Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/δΈ­ζ–‡
Sign inSign up
Home/Servers/Agentscore

Agentscore

I
by io.github.Thezenmonster

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

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command
npx -y @agentscore-xyz/[email protected]
Provider
Claude Code
claude mcp add io.github.thezenmonster-agentscore -- npx -y @agentscore-xyz/[email protected]

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "io.github.thezenmonster-agentscore": {
      "command": "npx",
      "args": [
        "-y",
        "@agentscore-xyz/[email protected]"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • FirecrawlπŸ”₯ Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

Questions

How do I install Agentscore?
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Agentscore need an API key?
No required environment variable is listed on this record.
What transport does Agentscore use?
Agentscore runs locally over stdio.
When was Agentscore last checked?
Last checked 2026-10-16. MCP security trust layer: scan packages, inspect repos, check exposure, monitor changes.

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

@agentscore-xyz/mcp-server

MCP security trust layer. Scan packages, get trust verdicts, inspect repo-wide MCP dependencies, generate Policy Gate setup, install the CI workflow directly, check incident exposure, and query the abuse database. Eight tools for MCP security decisions. No API key, zero config.

Scan any MCP package for security issues: agentscores.xyz

Quick Start

Claude Desktop

Add to your claude_desktop_config.json:

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

Cursor / Any MCP Client

npx @agentscore-xyz/mcp-server

What This Does

Your AI can now make security decisions about MCP packages:

You: "Is exa-mcp-server safe to install?"

Claude: calls get_verdict "Verdict: ALLOW. Score 90/100, LOW risk. No provenance attestations (published by personal account). 9 tools exposed including web_search_exa and crawling_exa."

You: "The axios package was compromised. Which MCP servers are affected?"

Claude: calls check_exposure "Multiple monitored MCP servers depend on axios, including exa-mcp-server, tavily-mcp, and figma-mcp."

You: "Scan @azure-devops/mcp for security issues"

Claude: calls scan_package "Score 75/100, MODERATE risk. Found: preinstall script modifying npm registry config. No provenance attestations."

You: "Check this repo for MCP dependencies"

Claude: calls check_my_repo "MCP dependencies found: 5. Two are warnings. Run generate_policy_gate_setup to turn these checks into a CI gate."

You: "Set up AgentScore Policy Gate for this repo"

Claude: calls install_policy_gate "The workflow file is written to .github/workflows/agentscore-policy-gate.yml. Commit and push. GitHub OIDC will auto-provision the repo on first run."

Available Tools

ToolWhat it does
scan_packageFull security scan: install scripts, prompt injection, source code patterns, provenance posture, MCP tool extraction
get_verdictTrust decision: allow, warn, or block based on scan findings. Also reports monitoring status and publisher posture.
check_my_repoInspect the current repo for MCP dependencies and summarise verdicts for every package detected locally.
generate_policy_gate_setupGenerate the exact OIDC-based GitHub Actions workflow needed to enforce Policy Gate in CI.
install_policy_gateWrite .github/workflows/agentscore-policy-gate.yml directly into the repo so the gate is ready to commit.
check_exposureIncident response: which monitored MCP servers depend on a given package?
check_abuseQuery the KYA abuse database for reported packages or agents
monitor_statusCheck if a package is under continuous monitoring and get scan history

From Ad-Hoc Scans To CI Enforcement

The MCP server now bridges one-off package checks into the sticky product:

  1. Run check_my_repo to see every MCP package used in a repo.
  2. Run generate_policy_gate_setup to preview the OIDC-based GitHub Actions workflow.
  3. Run install_policy_gate to write the workflow file directly into the repo.
  4. Commit and push. The first run auto-provisions through GitHub OIDC.

That turns "is this package safe?" into "this repo now enforces MCP dependency policy on every PR."

Risk Levels

ScoreRiskMeaning
85-100LOWClean or minor issues only
70-84MODERATESome findings, review recommended
50-69ELEVATEDSignificant findings, use with caution
30-49HIGHSerious issues, not recommended
0-29CRITICALDo not use

What the Scanner Checks

  • Install scripts (postinstall/preinstall hooks with network calls or code execution)
  • Prompt injection patterns in package metadata
  • Suspicious URLs (sketchy TLDs, ngrok, raw IPs)
  • Source code patterns (command injection, unsafe eval, hardcoded secrets)
  • Publisher provenance (trusted publishing, attestations)
  • Dependency count and metadata completeness
  • MCP tool definitions extracted from published source

Monitoring

AgentScore continuously monitors hundreds of MCP packages. The check_exposure and monitor_status tools use this live dataset. When a package like axios gets compromised, you can instantly find which MCP servers are affected.

Links

  • Website: agentscores.xyz
  • API Docs: agentscores.xyz/docs
  • Methodology: agentscores.xyz/methodology

Licence

MIT

How do I install Agentscore?
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Agentscore need an API key?
No required environment variable is listed on this record.
What transport does Agentscore use?
Agentscore runs locally over stdio.
When was Agentscore last checked?
Last checked 2026-10-16. MCP security trust layer: scan packages, inspect repos, check exposure, monitor changes.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Pricing
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • MCP Apps
  • Tools
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • Club
  • Work with us
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA