io.github.sznt2010/agentresources-mcp
NPM · @AGENTRESOURCES/MCP
MCP server for Agent Resources: Trust Cards, signed telemetry, ERC-8004 identity, x402.
Available components
Last scanned (32 minutes ago)
Scores higher than 40% of npm servers
Category Memory and Knowledge
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
- 32 of 113 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 184 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 273 tokens (~68/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −5
- Stability: pass → 0.63 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → 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/@agentresources/mcp@0.1.2
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 113 packages
| Packages resolved | 113 |
|---|---|
| Stale | 30 |
| No linked repository | 2 |
| 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 →
memory ~74
Memory verbs (remember, recall, forget, improve). Reads and writes go through the unified telemetry-as-memory store; recall is a multi-stage retrieval (cosine + cross-encoder + MMR + tail prune) handled server-side.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | object | yes | Verb-specific payload; see schemas. |
| verb | string | yes | – |
No output schema declared.
No examples provided.
signing_keys ~54
Manage an agent's signed-telemetry keys (list / register / revoke). Wraps /api/v1/agents/{id}/signing-keys.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| payload | object | yes | – |
No output schema declared.
No examples provided.
telemetry_ingest ~56
Submit a batch of telemetry spans (optionally signed envelope) to the AR gateway. Requires an authenticated session token.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | The AR agent UUID this span batch belongs to. |
| spans | array | yes | – |
No output schema declared.
No examples provided.
trust_card_lookup ~89
Fetch the public Trust Card (signed JSON-LD VC) for a wallet from /.well-known/trust-card/{wallet}. Optionally include the latest Merkle anchor proof.
| Name | Type | Req | Description |
|---|---|---|---|
| includeAnchor | boolean | – | When true, also include the latest Merkle anchor entry. Default false. |
| wallet | string | yes | 0x-prefixed 20-byte EVM wallet address (case-insensitive). |
No output schema declared.
No examples provided.
How do I install the io.github.sznt2010/agentresources-mcp server?
io.github.sznt2010/agentresources-mcp runs locally as an npm package, launched with npx -y @agentresources/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 · @agentresources/mcp
claude mcp add sznt2010-agentresources-mcp -- npx -y @agentresources/mcp
What is the io.github.sznt2010/agentresources-mcp server?
io.github.sznt2010/agentresources-mcp is listed in the public MCP registry as io.github.sznt2010/agentresources-mcp. MCP server for Agent Resources: Trust Cards, signed telemetry, ERC-8004 identity, x402. This page covers its npm package (@agentresources/mcp).
Is the io.github.sznt2010/agentresources-mcp server safe to use?
io.github.sznt2010/agentresources-mcp scores 71 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.sznt2010/agentresources-mcp server expose?
io.github.sznt2010/agentresources-mcp exposes 4 tools: trust_card_lookup, telemetry_ingest, memory, signing_keys. Their descriptions and schemas cost roughly 273 tokens of context every time the server is loaded.
Is the io.github.sznt2010/agentresources-mcp server still maintained?
io.github.sznt2010/agentresources-mcp 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.
What licence is the io.github.sznt2010/agentresources-mcp server under?
io.github.sznt2010/agentresources-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.