agentscore-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_packageA | 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. |
| get_verdictA | 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. |
| check_exposureA | 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?' |
| check_abuseA | Check if a package or agent has been reported to the KYA abuse database. Returns whether abuse has been reported and any details. |
| monitor_statusA | Check if an MCP package is under continuous monitoring and get its scan history. Shows current score, risk level, and recent changes. |
| check_my_repoA | 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. |
| generate_policy_gate_setupA | 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. No API key or secret is required. |
| install_policy_gateA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes: scanning, checking verdicts, monitoring, policy enforcement, etc. However, 'install_policy_gate' and 'generate_policy_gate_setup' are closely related (generate vs write workflow), which could cause misselection. Also, 'check_abuse' and 'get_verdict' both return trust-related info but from different sources, which is fine.
Tools use a consistent verb_noun pattern: check_abuse, check_exposure, generate_policy_gate_setup, etc. The only minor inconsistency is 'install_policy_gate' where 'install' could be seen as more specific than 'generate', but still follows the pattern. No mixing of camelCase or other styles.
8 tools is appropriate for an MCP package security server. Each tool covers a core function: scanning, verdict, monitoring, abuse check, exposure analysis, repo check, and policy gate generation/installation. Neither too few nor too many.
The tool set covers key lifecycle operations: scan, get verdict, monitor, check abuse, check exposure, and policy enforcement (generate+install). Missing tools could include updating a verdict or removing a policy gate, but the core workflow is well-covered.