mcpserver.lol
registry/agentscore
Connection check local install

agentscore

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

Tools 8
GitHub stars
Installs / wk 121
Licence
Transport stdio
Last checked never

Tools & capabilities

8 tools

Read from the published package source — this server runs locally, so there is no endpoint to query. Names are taken from the code, not observed at runtime, and descriptions are often absent.

check_abuse from source
Check if a package or agent has been reported to the KYA abuse database. Returns whether abuse has been reported and any details.
check_exposure from source
Check which monitored MCP servers depend on a given package. Use this during incident response to find blast radius. Example:
check_my_repo from source
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…
generate_policy_gate_setup from source
Generate the exact GitHub Actions workflow needed to enforce AgentScore Policy Gate for a repo. Detects MCP dependencies locally and returns the OIDC-based YAML needed for setup. N…
get_verdict from source
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 in…
install_policy_gate from source
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 dependen…
monitor_status from source
Check if an MCP package is under continuous monitoring and get its scan history. Shows current score, risk level, and recent changes.
scan_package from source
Scan an npm package for MCP security issues. Checks install scripts, prompt injection patterns, suspicious URLs, source code patterns, dependency count, metadata completeness, and…