updated 2026-10-18 00:07 UTC

Sub Agents MCP

Repository by shinpr

Define task-specific AI sub-agents in Markdown for any MCP-compatible tool.

MCP Servers TypeScript Listed MIT

Is Sub Agents MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.7 / 10
Provenance None
Signed commits 63%
Last push 3d ago
Advisories None known
Compare Sub Agents MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Sub Agents MCP scores 63.8/100 (Grade C), ranked #554 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.7/10; 63% of recent commits are signed; no published advisory affects its latest release (sub-agents-mcp); last pushed 2026-10-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How Sub Agents MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Sub Agents MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/shinpr/sub-agents-mcp, MIT, last pushed 2026-10-15. 63% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.7/10 (scanned Oct 17, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection4
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 10
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked, not attested

    • npm sub-agents-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: sub-agents-mcp 0.14.4. No published advisory affects it (OSV, checked 2026-10-18).

Changes to this chain

  • 2026-08-26 OSSF Scorecard: 5.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Sub Agents MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Sub Agents MCP compares in MCP Servers

  1. #310 Maya MCP 63.9 +0.1
  2. #311 Parallel Browser MCP 63.9 +0.1
  3. #312 Sub Agents MCP 63.8 this agent
  4. #313 Persistent Project Context for xAI Grok 63.7 −0.1
  5. #314 PageIndex MCP 63.7 −0.1

Bars show each HVTrust score; the tick marks Sub Agents MCP’s 63.8.

Where the 63.8 comes from

HVTrust dimensions vs the MCP Servers average

63.8 / 100 · 100.0% confidence

Sub Agents MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.3 / 25
in line with avg 10.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.8 below avg 13.6
Transparency50% declared license · 50% OSSF Scorecard
13.3 / 17
1.0 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
16.2 / 20
4.0 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.2 / 20
0.8 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-16
Rank Moved
Rank rose 119 spots (#667 → #548)
2026-10-16
HVTrust Changed
HVTrust up 3.5pts (60.5 → 64.0)
2026-10-15
Rank Moved
Rank dropped 37 spots (#630 → #667)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.7/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for Sub Agents MCP View MCP Servers Report missing data
56.4
Activity sub-score · out of 100
#312
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-18 00:07 UTC · Repo last pushed 3 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
98
Forks
17
Last Push
2026-10-15
3 days ago
Commits (4 wk)
12
Downloads (7d)
338
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼5
was #549

Analysis

Activity Inputs

56.4 / 100
StarsRepository reach
12.0 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
13.9 / 25
CommunityFork signal
5.8 / 20

Common questions about Sub Agents MCP

Sub Agents MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Sub Agents MCP publish package provenance?
No published build provenance is currently detected for Sub Agents MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Sub Agents MCP have an OpenSSF Scorecard?
Sub Agents MCP has an OpenSSF Scorecard score of 5.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Sub Agents MCP actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does Sub Agents MCP use?
Sub Agents MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Sub Agents MCP's commits signed?
63% of the last 100 commits to Sub Agents MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Sub Agents MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Sub Agents MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, Google Gemini

Maintain Sub Agents MCP?

For maintainers

HVTrust scores Sub Agents MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 35HVTrust 4Listed 2Grade 2Scorecard 1Surface 1Delisted 1MCP 1Score 1
2026-10-16
Rank Moved
Rank rose 119 spots (#667 → #548)
2026-10-16
HVTrust Changed
HVTrust up 3.5pts (60.5 → 64.0)
2026-10-15
Rank Moved
Rank dropped 37 spots (#630 → #667)
2026-10-14
Rank Moved
Rank rose 63 spots (#693 → #630)
2026-10-14
Activity Score Changed
Activity score up 7pts (47 → 54)
2026-10-10
Rank Moved
Rank dropped 21 spots (#659 → #680)
2026-10-09
Rank Moved
Rank dropped 51 spots (#608 → #659)
2026-10-08
Rank Moved
Rank rose 33 spots (#641 → #608)
2026-10-06
Rank Moved
Rank dropped 11 spots (#632 → #643)
2026-10-02
Rank Moved
Rank dropped 66 spots (#545 → #611)
2026-10-01
Rank Moved
Rank dropped 12 spots (#533 → #545)
2026-09-26
Rank Moved
Rank rose 12 spots (#557 → #545)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 239 spots (#782 → #543)
2026-09-23
HVTrust Changed
HVTrust up 33.6pts (29.2 → 62.8)
2026-09-22
Newly Listed
First tracked at rank #782
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 28 spots (#480 → #508)
2026-09-11
Rank Moved
Rank dropped 10 spots (#460 → #470)
2026-09-09
Grade Changed
Trust grade D → C
2026-09-09
Rank Moved
Rank rose 629 spots (#1087 → #458)
2026-09-09
HVTrust Changed
HVTrust up 22.0pts (42.4 → 64.4)
2026-09-07
Rank Moved
Rank dropped 32 spots (#1048 → #1080)
2026-09-06
Rank Moved
Rank dropped 12 spots (#1036 → #1048)
2026-09-05
Rank Moved
Rank dropped 39 spots (#997 → #1036)
2026-09-04
Rank Moved
Rank dropped 24 spots (#973 → #997)
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Anthropic, Google Gemini
2026-09-03
Rank Moved
Rank dropped 56 spots (#917 → #973)
2026-09-02
Rank Moved
Rank dropped 55 spots (#862 → #917)
2026-09-01
Rank Moved
Rank dropped 23 spots (#839 → #862)
2026-08-31
Rank Moved
Rank dropped 31 spots (#808 → #839)
2026-08-30
Rank Moved
Rank dropped 19 spots (#789 → #808)
2026-08-29
Rank Moved
Rank dropped 47 spots (#742 → #789)
2026-08-28
Rank Moved
Rank dropped 32 spots (#710 → #742)
2026-08-27
Rank Moved
Rank dropped 22 spots (#688 → #710)
2026-08-26
Scorecard Added
OSSF Scorecard: 5.7/10
2026-08-26
Rank Moved
Rank rose 265 spots (#953 → #688)
2026-08-26
HVTrust Changed
HVTrust up 19.9pts (22.5 → 42.4)
2026-08-23
Rank Moved
Rank rose 22 spots (#968 → #946)
2026-08-22
Rank Moved
Rank rose 12 spots (#980 → #968)
2026-08-20
Rank Moved
Rank dropped 10 spots (#976 → #986)
2026-08-17
Rank Moved
Rank rose 13 spots (#980 → #967)
2026-08-16
Rank Moved
Rank dropped 34 spots (#946 → #980)
2026-08-13
Rank Moved
Rank dropped 12 spots (#935 → #947)
2026-08-12
Rank Moved
Rank rose 11 spots (#946 → #935)
2026-08-10
Rank Moved
Rank dropped 52 spots (#884 → #936)
2026-08-08
Newly Listed
First tracked at rank #875
GitHub → npm: sub-agents-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.8 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/sub-agents-mcp.svg)](https://hvtracker.net/agents/sub-agents-mcp)
HTML:
<a href="https://hvtracker.net/agents/sub-agents-mcp"><img src="https://hvtracker.net/badge/sub-agents-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON