intentplane
Related Servers
Alternatives to intentplane
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSecurity gateway for MCP servers. Wraps any MCP server with per-tool policies (Cedar + JSON), Ed25519-signed decision receipts, human approval gates, and trust tiers. Shadow mode by default — logs everything, blocks nothing.2,140 npm9MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP gateway that applies deterministic, compiled policy to tool discovery, invocation, and outbound data flow, with no model in the enforcement path. Every decision emits a hash-chained receipt sealed with Ed25519 and verifiable using public keys only.Apache 2.0
- AlicenseBqualityCmaintenanceSecurity gateway that wraps any MCP server with per-tool policies, approval gates, and optional Ed25519-signed decision receipts. Shadow mode logs every tool call without blocking; enforce mode applies block, rate-limit, and minimum-tier rules. Receipts are independently verifiable offline with no accounts needed.52,140 npm11MIT
- AlicenseNot gradedqualityBmaintenanceA proxy that sits in front of any MCP server. Hides tools with hidden instructions, freezes actions if tool descriptions change mid-session, caps actions like delete, send or pay with a budget, and keeps a signed audit log.1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProxy for any MCP server that lets read tools pass straight through while turning every write tool into a pending card the agent cannot release on its own. Only signed evidence from the user's paired device — a tap on the approval page or their own transcribed voice — actually executes the action, with one-time nonces, expiry, replay checks and receipts.MIT
- AlicenseCqualityAmaintenanceExposes an MCP server that routes every agent tool call through deterministic policy gates, budget escrow with clawback, authenticated approvals, and a hash-chained audit trail, enabling agents to safely perform money-related operations while receiving actionable denial reasons.132Apache 2.0
TDQS
Scored across 4 tools
Each tool targets a clearly distinct resource and action: account balance, inbox reading, money transfer, and email sending. There is no meaningful overlap between any pair.
All names follow a clean verb_noun pattern (get_balance, read_inbox, send_money, send_email). The minor get/read variation is natural and does not break predictability.
Four tools is a reasonable minimum for a small assistant-style server covering finance and email. It is slightly thin for the apparent breadth of those domains, but each tool earns its place.
Core read and send operations exist for both money and email, but there are notable gaps: no transaction history, no individual email retrieval/search, and no reply/delete operations. Agents can complete basic workflows but will hit dead ends for common follow-ups.