MCP.Market

Smartpolicy MCP server

by smartpolicy-protocol·io.github.smartpolicy-protocol/smartpolicy·v0.2.0
No reviews yet

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

B77/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
New

0 stars38 downloads/wk

Reviews

Write one

Nobody has reviewed Smartpolicy yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Smartpolicy tools (8, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • grant_issue

    Issue a short-lived single-use EIP-712 grant authorizing `subject` to perform `action` under

  • grant_issuer_info

    This server's grant-issuer address (authorize it on a policy via addIssuer) and limits.

  • grant_verify

    Pre-flight a grant before broadcasting: checks the on-chain GrantVerifier for validity (signature,

  • policy_check

    THE canonical SmartPolicy question: may `subject` perform `action` under policy `policyId`?

  • policy_createwrite action

    Build the unsigned transaction that creates a new policy. Returns {to, value, data} for YOUR

  • policy_fees

    Current protocol fees in wei (read live). createPolicy needs exactly creationFee as msg.value;

  • policy_get

    Read a policy: owner, expiry, active/locked state, membership mode, member count, metadata URI. Free.

  • policy_updatewrite action

    Build the unsigned transaction for a policy rule change (submit from the owner or an admin

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan21 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 77 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Smartpolicy compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
38
more than 29% of 12,191 servers with a package

What its tools let an agent do: 6 read · 2 change

Install Smartpolicy in Claude Code, Cursor or VS Code

Runs npx -y @smartpolicy/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add smartpolicy -- npx -y @smartpolicy/mcp
Add to Cursor

What the publisher says

From the Smartpolicy repository's README, as published. We do not edit it. Read it on GitHub

SmartPolicy

Runtime authorization for AI agents and smart contracts.

Define what an agent, a user, or a contract is allowed to do — once, as a policy. Enforce it everywhere: on-chain via a minimal verifier, off-chain via an MCP server and REST API that AI systems consume directly. Update the rules without redeploying anything.

Status (2026-06-12): core contracts live on Ethereum Sepolia

(Etherscan-verified, addresses in contracts/deployments/sepolia.json); 54

Foundry tests green; MCP server v0 packaged — npx smartpolicy-mcp runs

zero-config against Sepolia, npx smartpolicy-mcp deploy bootstraps any

chain from embedded bytecode; AI-consumability proven by unaided

fresh-agent execution tests (incl. cold start on an empty chain). NOT

audited; internal until mature — no public repo or registry listings yet.

Current state, decisions, and how to resume work: PLAN.md.

Why

Every team shipping AI agents hits the same wall: the agent can technically do anything its keys allow, and the only ways to constrain it are hardcoded prompts or redeployed code. Every smart contract team hits the mirror image: access rules baked into the contract at deploy time.

SmartPolicy separates the rule from the enforcement point:

and mutability flags. It is data, not code. Changing a rule is a transaction, not a redeploy.

  • A policy lives in the on-chain Registry: members, admins, conditions, expiry,

"may 0xAgent perform action under policy N?" and receives a short-lived signed grant (EIP-712) that any contract or backend can verify.

  • Enforcement happens wherever the action happens:
  • A smart contract inherits one modifier and checks the Registry (free view call).
  • An AI agent (or the service in front of it) asks the MCP server / REST API:

What this is NOT

Revenue is fees: a small fee on on-chain policy writes, and metered (x402) pay-per-call on the hosted API. Reads and verification are free.

  • Not a token. There is no protocol token, no ICO, no governance theater.

code you can read, not admin keys you have to trust. New protocol versions are new deployments.

  • Not upgradeable. The core Registry is immutable once deployed. Trust comes from

world?". Condition values that depend on external facts are attested via signed grants from sources the policy owner chooses.

  • Not an oracle. SmartPolicy answers "is this allowed?", not "what happened in the

Architecture (short version)

┌─────────────┐   MCP / REST (x402 metered)   ┌──────────────────┐
│  AI agents   │ ────────────────────────────▶ │ SmartPolicy MCP  │
│  & services  │ ◀──── signed grants ────────  │ server (TS)      │
└─────────────┘                                └────────┬─────────┘
                                                        │ reads + grant issuance
┌─────────────┐   inherit Gate modifier        ┌────────▼─────────┐
│  Protected   │ ────── view calls ──────────▶ │ PolicyRegistry   │
│  contracts   │                               │ (Base, immutable)│
└─────────────┘                                └──────────────────┘

See ARCHITECTURE.md for the full design and the rationale for every decision (chain, fees, trust model, what was deliberately dropped from v1).

Repository layout

contracts/   Solidity core: PolicyRegistry, PolicyGate, interfaces (Foundry)
mcp/         MCP server + REST API (TypeScript, x402 metering)
sdk/         TypeScript client SDK (@smartpolicy/sdk) — reads, grants, tx-building
docs/        Integration guides (planned)

Lineage

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Smartpolicy: common questions

Is Smartpolicy MCP server safe?
Mostly: it is graded B (77/100). Read the Smartpolicy safety report
How do I install Smartpolicy?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Smartpolicy need an API key?
Yes. The registry entry asks for SMARTPOLICY_ISSUER_KEY.
Is Smartpolicy maintained?
The last commit was 115 days ago (2026-07-11). The latest release is v0.2.0.
How does Smartpolicy compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.