io.github.smartpolicy-protocol/smartpolicy
NPM · @SMARTPOLICY/MCP
Runtime authorization for AI agents and smart contracts via an immutable on-chain policy registry
Available components
Last scanned (8 hours ago)
Scores higher than 53% 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 109 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 (Apache-2.0).Pass
- Actively maintained (last published 116 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1000 tokens (~125/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% 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 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
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.
- 4 Nov 26 −2
- Stability: pass → 0.83 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
No change was recorded against any check on this day. Supply Chain Security went from 98 to 99.
- 22 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
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/@smartpolicy/mcp@0.2.0
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 109 packages
| Packages resolved | 109 |
|---|---|
| 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 →
grant_issue ~276
Issue a short-lived single-use EIP-712 grant authorizing `subject` to perform `action` under `policyId`, redeemable ONLY at the `target` contract. The subject must pass policy_check first; the policy must list this server's issuer address (grant_issuer_info) via addIssuer. Pass the result to target's PolicyGate.withGrant function. Verify with grant_verify before broadcasting.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action name (e.g. "withdraw") or 0x-prefixed bytes32. Names are keccak256-hashed, matching keccak256("withdraw") in the protected contract. |
| context | string | – | Optional bytes32 binding the gated call's parameters. Set to keccak256(abi.encode(...)) of the exact parameters the caller must use (e.g. the recipient and amount for a transfer); the on-chain gate r… |
| policyId | – | yes | Policy ID as decimal string or integer |
| subject | string | yes | – |
| target | – | yes | the contract that will consume the grant (the integrator/gate); only it may redeem |
| ttlSeconds | integer | – | Requested grant lifetime in seconds; clamped to the server's maxGrantTtlSeconds (see grant_issuer_info) |
No output schema declared.
No examples provided.
grant_issuer_info ~30
This server's grant-issuer address (authorize it on a policy via addIssuer) and limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
grant_verify ~92
Pre-flight a grant before broadcasting: checks the on-chain GrantVerifier for validity (signature, validity window, issuer authorization, policy active) and whether the nonce is already used. Returns {valid, nonceUsed}. Note: does NOT check subject==caller or target — the gate enforces those on redemption.
| Name | Type | Req | Description |
|---|---|---|---|
| grant | object | yes | the grant object exactly as returned by grant_issue |
| signature | string | yes | – |
No output schema declared.
No examples provided.
policy_check ~125
THE canonical SmartPolicy question: may `subject` perform `action` under policy `policyId`? Returns allowed (boolean) plus the reasons. Maps 1:1 to PolicyRegistry.isAllowed — a protected contract gives the identical answer on-chain. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action name (e.g. "withdraw") or 0x-prefixed bytes32. Names are keccak256-hashed, matching keccak256("withdraw") in the protected contract. |
| policyId | – | yes | Policy ID as decimal string or integer |
| subject | string | yes | – |
No output schema declared.
No examples provided.
policy_create ~150
Build the unsigned transaction that creates a new policy. Returns {to, value, data} for YOUR wallet to sign and submit — the submitting address becomes the policy owner. `value` is the protocol creation fee in wei.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | integer | – | unix seconds; 0 = never expires |
| metadataHash | string | – | optional keccak256 of the metadata document — on-chain tamper-evidence for the URI's content |
| metadataURI | string | – | optional metadata pointer, informational only; prefer ipfs:// (content-immutable) |
| openMembership | boolean | – | true: every address counts as a member |
| transferable | boolean | – | true: ownership can be transferred later |
No output schema declared.
No examples provided.
policy_fees ~49
Current protocol fees in wei (read live). createPolicy needs exactly creationFee as msg.value; every other write needs exactly updateFee. Read this before building any write tx — wrong value reverts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
policy_get ~45
Read a policy: owner, expiry, active/locked state, membership mode, member count, metadata URI. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| policyId | – | yes | Policy ID as decimal string or integer |
No output schema declared.
No examples provided.
policy_update ~96
Build the unsigned transaction for a policy rule change (submit from the owner or an admin wallet; `value` is the protocol update fee in wei). Operations: addMembers, removeMembers, setActionRule (UNSET|MEMBERS|ANYONE|NOBODY), addIssuer, removeIssuer, addAdmin, removeAdmin, setExpiry.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | – | yes | – |
| policyId | – | yes | Policy ID as decimal string or integer |
No output schema declared.
No examples provided.
How do I install the io.github.smartpolicy-protocol/smartpolicy MCP server?
io.github.smartpolicy-protocol/smartpolicy runs locally as an npm package, launched with npx -y @smartpolicy/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 · @smartpolicy/mcp
claude mcp add smartpolicy-protocol-smartpolicy -- npx -y @smartpolicy/mcp
What is the io.github.smartpolicy-protocol/smartpolicy MCP server?
io.github.smartpolicy-protocol/smartpolicy is an MCP server listed in the public MCP registry as io.github.smartpolicy-protocol/smartpolicy. Runtime authorization for AI agents and smart contracts via an immutable on-chain policy registry. This page covers its npm package (@smartpolicy/mcp).
Is the io.github.smartpolicy-protocol/smartpolicy MCP server safe to use?
io.github.smartpolicy-protocol/smartpolicy scores 76 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.smartpolicy-protocol/smartpolicy MCP server expose?
io.github.smartpolicy-protocol/smartpolicy exposes 8 tools: policy_check, policy_get, grant_issue, grant_issuer_info, policy_fees, and 3 more. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.
Is the io.github.smartpolicy-protocol/smartpolicy MCP server still maintained?
io.github.smartpolicy-protocol/smartpolicy 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.smartpolicy-protocol/smartpolicy MCP server under?
io.github.smartpolicy-protocol/smartpolicy declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.