A side-by-side look at the Pkgxray and Agentscore MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Pkgxray for security work as a local process; choose Agentscore MCP Server for security as a local process. You can also run both side by side in one mcpServers block.
scan_package, get_verdict, check_exposure.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 47/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 1 |
| Directory activity | 5 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Pkgxray | View Agentscore MCP Server |
No tool names declared yet. Check the project README from the listing page.
scan_packageScan 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_verdictGet 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_exposureCheck 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_abuseCheck if a package or agent has been reported to the KYA abuse database. Returns whether abuse has been reported and any details.monitor_statusCheck if an MCP package is under continuous monitoring and get its scan history. Shows current score, risk level, and recent changes.check_my_repoInspect 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_setupGenerate 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_gateWrite 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.Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"pkgxray": {
"command": "npx",
"args": [
"--yes",
"pkgxray@1.0.5"
]
}
}
}
{
"mcpServers": {
"thezenmonster-agentscore-mcp-server": {
"command": "npx",
"args": [
"-y",
"@agentscore-xyz/mcp-server"
]
}
}
}