Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.smartpolicy-protocol/smartpolicy

NPM · @SMARTPOLICY/MCP · SCANNED AUG 3

Runtime authorization for AI agents and smart contracts via an immutable on-chain policy registry

Available components

+15 this week 60 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (110 of 114), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (110 of 114), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @smartpolicy/mcp

# add to Claude Code
claude mcp add smartpolicy-protocol-smartpolicy -- npx -y @smartpolicy/mcp
# add to Codex CLI
codex mcp add smartpolicy-protocol-smartpolicy -- npx -y @smartpolicy/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "smartpolicy-protocol-smartpolicy": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@smartpolicy/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add smartpolicy-protocol-smartpolicy --command npx --arg -y --arg @smartpolicy/mcp
# ~/.hermes/config.yaml
mcp_servers:
  smartpolicy-protocol-smartpolicy:
    command: "npx"
    args: ["-y", "@smartpolicy/mcp"]
// mcp.json
{
  "mcpServers": {
    "smartpolicy-protocol-smartpolicy": {
      "command": "npx",
      "args": [
        "-y",
        "@smartpolicy/mcp"
      ]
    }
  }
}
Changelog

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 Aug 26 +40
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Security disclosure: unverified → fail functional
    • License: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Schema quality: unverified → fair functional
    • Licence: Apache-2.0 functional
  • 2 Aug 26 −5
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Security disclosure: fail → unverified functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 1 Aug 26 +5
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 45

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@smartpolicy/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 110 packages

110 packages in the resolved dependency tree · 109 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 8 exposed · ~863 tokens

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.

Tool Tokens
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.

NameTypeReqDescription
actionstringyesAction name (e.g. "withdraw") or 0x-prefixed bytes32. Names are keccak256-hashed, matching keccak256("withdraw") in the protected contract.
contextstringOptional 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…
policyIdyesPolicy ID as decimal string or integer
subjectstringyes
targetyesthe contract that will consume the grant (the integrator/gate); only it may redeem
ttlSecondsintegerRequested 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.

NameTypeReqDescription
grantobjectyesthe grant object exactly as returned by grant_issue
signaturestringyes

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.

NameTypeReqDescription
actionstringyesAction name (e.g. "withdraw") or 0x-prefixed bytes32. Names are keccak256-hashed, matching keccak256("withdraw") in the protected contract.
policyIdyesPolicy ID as decimal string or integer
subjectstringyes

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.

NameTypeReqDescription
expiresAtintegerunix seconds; 0 = never expires
metadataHashstringoptional keccak256 of the metadata document — on-chain tamper-evidence for the URI's content
metadataURIstringoptional metadata pointer, informational only; prefer ipfs:// (content-immutable)
openMembershipbooleantrue: every address counts as a member
transferablebooleantrue: 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.

NameTypeReqDescription
policyIdyesPolicy 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.

NameTypeReqDescription
operationyes
policyIdyesPolicy ID as decimal string or integer

No output schema declared.

No examples provided.