io.github.Thezenmonster/agentscore

NPM · @AGENTSCORE-XYZ/MCP-SERVER · SCANNED AUG 3

MCP security trust layer: scan packages, inspect repos, check exposure, monitor changes.

Available components

+24 this week 70 70 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 16 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Tool/resource definitions use about 563 tokens (~70/item across 8 items; 8 tools + 0 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @agentscore-xyz/mcp-server

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add thezenmonster-agentscore -- npx -y @agentscore-xyz/mcp-server

# add to Codex CLI

codex mcp add thezenmonster-agentscore -- npx -y @agentscore-xyz/mcp-server

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thezenmonster-agentscore": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@agentscore-xyz/mcp-server"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add thezenmonster-agentscore --command npx --arg -y --arg @agentscore-xyz/mcp-server

# ~/.hermes/config.yaml

mcp_servers:
  thezenmonster-agentscore:
    command: "npx"
    args: ["-y", "@agentscore-xyz/mcp-server"]

// mcp.json

{
  "mcpServers": {
    "thezenmonster-agentscore": {
      "command": "npx",
      "args": [
        "-y",
        "@agentscore-xyz/mcp-server"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +50
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Security disclosure: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.27 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
2 Aug 26 −16
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
1 Aug 26 +8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
27 Jul 26 46

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@agentscore-xyz/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 8 exposed · ~563 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

check_abuse ~49

Check if a package or agent has been reported to the KYA abuse database. Returns whether abuse has been reported and any details.

Input Output Examples

Name	Type	Req	Description
agent	string	yes	Package name or agent identifier to check

No output schema declared.

No examples provided.

check_exposure ~60

Check which monitored MCP servers depend on a given package. Use this during incident response to find blast radius. Example: 'which MCP servers use axios?'

Input Output Examples

Name	Type	Req	Description
npm	string	yes	npm package name to check exposure for (e.g. 'axios')

No output schema declared.

No examples provided.

check_my_repo ~80

Inspect the current repo for MCP dependencies, look up AgentScore verdicts for each package, and summarise what should be gated in CI. Use this when a developer wants to understand all MCP packages in a repo instead of scanning one package at a time.

Input Output Examples

Name	Type	Req	Description
path	string	—	Optional path to the repo root. Defaults to the current working directory.

No output schema declared.

No examples provided.

generate_policy_gate_setup ~86

Generate the exact GitHub Actions workflow needed to enforce AgentScore Policy Gate for a repo. Detects MCP dependencies locally and returns the YAML, secret name, and pilot link needed for setup.

Input Output Examples

Name	Type	Req	Description
path	string	—	Optional path to the repo root. Defaults to the current working directory.
repo_url	string	—	Optional repository URL override for the pilot handoff link.

No output schema declared.

No examples provided.

get_verdict ~63

Get a trust verdict for an MCP package: allow, warn, or block. Based on scan findings (score and severity). Also reports monitoring status and publisher posture. Use this before installing or connecting to an MCP server.

Input Output Examples

Name	Type	Req	Description
npm	string	yes	npm package name

No output schema declared.

No examples provided.

install_policy_gate ~98

Write the AgentScore Policy Gate workflow file to this repo. Creates .github/workflows/agentscore-policy-gate.yml with OIDC authentication (no API key needed). Detects MCP dependencies and includes them in the workflow. The gate will auto-provision the repo on first push.

Input Output Examples

Name	Type	Req	Description
path	string	—	Optional path to the repo root. Defaults to the current working directory.
repo_url	string	—	Optional repository URL override.

No output schema declared.

No examples provided.

monitor_status ~44

Check if an MCP package is under continuous monitoring and get its scan history. Shows current score, risk level, and recent changes.

Input Output Examples

Name	Type	Req	Description
npm	string	yes	npm package name

No output schema declared.

No examples provided.

scan_package ~83

Scan an npm package for MCP security issues. Checks install scripts, prompt injection patterns, suspicious URLs, source code patterns, dependency count, metadata completeness, and publisher provenance. Returns score (0-100), risk level, and detailed findings.

Input Output Examples

Name	Type	Req	Description
npm	string	yes	npm package name (e.g. 'exa-mcp-server', '@modelcontextprotocol/server-github')

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug