io.github.andyscott88/agentsafe
NPM · AGENTSAFE-MCP-SERVER
Real-time URL trust scoring for AI agents. Blocks phishing and malicious sites.
Available components
Last scanned (1 hour ago)
Scores higher than 38% 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
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 163 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 176 tokens (~58/item across 3 items; 3 tools + 0 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → 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 5 Nov 2026 · Analysed npm/agentsafe-mcp-server@1.0.1
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
evaluate_login ~44
Check if a URL is safe for an AI agent to submit login credentials to. Prevents credential theft on phishing sites.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The login URL to evaluate |
No output schema declared.
No examples provided.
evaluate_payment ~53
Check if a URL is safe for an AI agent to make a payment on. Uses strict payment-context scoring.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Transaction amount in dollars |
| url | string | yes | The payment URL to evaluate |
No output schema declared.
No examples provided.
evaluate_url ~79
Check if a URL is safe for an AI agent to interact with. Returns ALLOW, BLOCK, or REQUIRE_HUMAN_APPROVAL with Claude AI reasoning.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | The action the agent wants to take |
| data_sensitivity | string | – | Sensitivity of data involved |
| url | string | yes | The URL to evaluate |
No output schema declared.
No examples provided.
How do I install the io.github.andyscott88/agentsafe MCP server?
io.github.andyscott88/agentsafe runs locally as an npm package, launched with npx -y agentsafe-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agentsafe-mcp-server
claude mcp add andyscott88-agentsafe -- npx -y agentsafe-mcp-server
What is the io.github.andyscott88/agentsafe MCP server?
io.github.andyscott88/agentsafe is an MCP server listed in the public MCP registry as io.github.andyscott88/agentsafe. Real-time URL trust scoring for AI agents. Blocks phishing and malicious sites. This page covers its npm package (agentsafe-mcp-server).
Is the io.github.andyscott88/agentsafe MCP server safe to use?
io.github.andyscott88/agentsafe scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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.andyscott88/agentsafe MCP server expose?
io.github.andyscott88/agentsafe exposes 3 tools: evaluate_url, evaluate_payment, evaluate_login. Their descriptions and schemas cost roughly 176 tokens of context every time the server is loaded.
Is the io.github.andyscott88/agentsafe MCP server still maintained?
io.github.andyscott88/agentsafe is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.