Server data from the Official MCP Registry
Spend, scope, data, and approval policy gate for autonomous AI actions.
Spend, scope, data, and approval policy gate for autonomous AI actions.
Remote endpoints: streamable-http: https://agentpass-protocol.rmalka06.chatgpt.site/mcp
Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.
1 tool verified · Open access · No issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"io-github-razel369-intentfence": {
"url": "https://agentpass-protocol.rmalka06.chatgpt.site/mcp"
}
}
}From the project's GitHub README.
IntentFence is an open spend and action policy gate for autonomous AI. Put it immediately before a tool call, evaluate declared scope, cost, data-retention, and approval constraints, and run the downstream action only when the decision allows it:
safe_to_proceedneeds_reviewdeniedProduction: https://agentpass-protocol.rmalka06.chatgpt.site
| Surface | Endpoint |
|---|---|
| Free REST preview | POST /api/preflight |
| Paid x402 decision | POST /api/preflight/verified |
| Receipt verification | POST /api/receipts/verify |
| Public ES256 keys | GET /.well-known/jwks.json |
| MCP Streamable HTTP | /mcp |
| A2A Agent Card | GET /.well-known/agent-card.json |
| OpenAPI | GET /openapi.json |
The paid endpoint costs 0.05 USDC on Base through x402. A successful call
returns both the facilitator's PAYMENT-RESPONSE settlement header and an
IntentFence ES256 compact-JWS receipt.
For teams that need a guarded production workflow, the launch pilot is $750 plus $149/month and includes hands-on integration of one agent action. The Production plan starts at $499/month.
IntentFence 0.5 attests that it evaluated the inputs supplied by the caller. It does not independently prove real-world identity, authorization, or downstream enforcement. The receipt-signing key is separate from the USDC recipient wallet. IntentFence never needs a payer's seed phrase or wallet private key.
npm install
npm run dev
The production signing key is stored in Sites as the secret
INTENTFENCE_SIGNING_PRIVATE_JWK. Generate a separate development key with:
node scripts/generate-signing-key.mjs /secure/path/intentfence-private-jwk.json
Never commit the generated private JWK. Publish only its public coordinates in
/.well-known/jwks.json.
npm run test
npm run lint
npx tsc --noEmit
npm run sdk:check
npm run smoke:protocol -- http://localhost:3000
Set INTENTFENCE_TEST_PRIVATE_JWK_PATH only for a local smoke test that should
exercise the signed-receipt verifier.
TypeScript and Python SDKs live in sdk/. The root server.json is ready for
the official MCP Registry under io.github.razel369/intentfence; the public MCP
endpoint uses Streamable HTTP and requires no API key.
The fastest path to production is one guarded action: purchase, transfer, booking, deployment, deletion, or another consequential tool call. Submit the pilot form on the production site with the real action and its policy boundary.
See docs/PROTOCOL.md and docs/SECURITY.md for the protocol and security model.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.