io.github.mdfifty50-boop/agent-security
NPM · AGENT-SECURITY-MCP
Security scanning and threat detection for AI agents
Available components
Last scanned (16 hours ago)
Scores higher than 46% of npm servers
Category Security
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 → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. 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 211 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability41
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 622 tokens (~62/item across 10 items; 8 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 16 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 15 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 −2
- Stability: pass → 0.90 functional
- 3 Nov 26 +1
- Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/agent-security-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_agent_permissions ~89
Audit an agent configuration for over-privileged access. Compares granted permissions against role-based expectations (researcher, analyst, developer, reviewer, orchestrator, monitor). Flags principle of least privilege violations.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_config | object | yes | Agent configuration to audit |
| role | string | yes | The declared role of the agent (researcher, analyst, developer, reviewer, orchestrator, monitor) |
No output schema declared.
No examples provided.
detect_prompt_injection ~85
Analyze text for prompt injection attempts. Detects instruction overrides, identity manipulation, system prompt extraction, data exfiltration, delimiter attacks, encoded injections, and privilege escalation. Context-aware risk scoring.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Where this text originates — affects risk scoring (user_input is highest risk) |
| text | string | yes | The text to analyze for prompt injection patterns |
No output schema declared.
No examples provided.
detect_tool_poisoning ~57
Analyze an MCP tool definition for poisoning indicators — hidden instructions in descriptions that could manipulate agent behavior. Covers OWASP Agentic Top 10 tool poisoning attack vectors.
| Name | Type | Req | Description |
|---|---|---|---|
| tool_definition | object | yes | The MCP tool definition to analyze |
No output schema declared.
No examples provided.
generate_security_report ~99
Generate a comprehensive security assessment report for an agent deployment. Aggregates results from config scans and permission audits into a prioritized remediation plan with OWASP LLM Top 10 compliance notes.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Name of the agent or deployment being assessed |
| audit_results | array | – | Array of audit_agent_permissions results to include in the report |
| configs | array | – | Array of scan_mcp_config results to include in the report |
No output schema declared.
No examples provided.
health_check ~20
Returns server health, uptime, version, and usage stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_mcp_config ~76
Scan an MCP server configuration for security issues including dangerous commands, exposed secrets, network exposure, and container misconfigurations. Returns a risk score (0-100), issues found, and actionable recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | yes | MCP server configuration object |
| server_name | string | yes | Name of the MCP server being scanned |
No output schema declared.
No examples provided.
scan_secrets ~96
Detect leaked secrets and credentials in text or code. Identifies API keys (OpenAI, AWS, GitHub, GCP, Stripe, Slack, Telegram), JWT tokens, database connection strings, private keys, and .env patterns. All values are masked in output.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text or code content to scan for secrets |
| content_type | string | yes | Type of content being scanned — affects detection sensitivity |
No output schema declared.
No examples provided.
validate_scope_contract ~81
Check if an agent action complies with its scope contract. Validates tool usage against allowlists, file access against permitted paths, and boundary constraints (no_network, read_only, no_exec, no_secrets).
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | yes | The action to validate against the scope contract |
| scope_contract | object | yes | The agent scope contract defining permitted actions |
No output schema declared.
No examples provided.
How do I install the io.github.mdfifty50-boop/agent-security MCP server?
io.github.mdfifty50-boop/agent-security runs locally as an npm package, launched with npx -y agent-security-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agent-security-mcp
claude mcp add mdfifty50-boop-agent-security -- npx -y agent-security-mcp
What is the io.github.mdfifty50-boop/agent-security MCP server?
io.github.mdfifty50-boop/agent-security is an MCP server listed in the public MCP registry as io.github.mdfifty50-boop/agent-security. Security scanning and threat detection for AI agents. This page covers its npm package (agent-security-mcp).
Is the io.github.mdfifty50-boop/agent-security MCP server safe to use?
io.github.mdfifty50-boop/agent-security scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mdfifty50-boop/agent-security MCP server expose?
io.github.mdfifty50-boop/agent-security exposes 8 tools: health_check, scan_mcp_config, detect_prompt_injection, validate_scope_contract, scan_secrets, and 3 more. Their descriptions and schemas cost roughly 603 tokens of context every time the server is loaded.
Is the io.github.mdfifty50-boop/agent-security MCP server still maintained?
io.github.mdfifty50-boop/agent-security is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mdfifty50-boop/agent-security MCP server under?
io.github.mdfifty50-boop/agent-security declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.mdfifty50-boop/agent-security MCP server?
VerifyMCP ran 16 checks on io.github.mdfifty50-boop/agent-security, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.