Authorization proxy for another MCP server: a rule check and AI judges approve each tool call
MCPpedia last refreshed this data
io.github.Insomniac-VibeLabs/two-key is an MCP server that authorization proxy for another MCP server: a rule check and AI judges approve each tool call. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 87/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-insomniac-vibelabs-two-key": {
"args": [
"two-key"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Authorization proxy for another MCP server: a rule check and AI judges approve each tool call
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked two-key against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in security
Search-first MCP server for JavaScript reverse engineering: 735 tools across 36 domains.
MCP security scanner. CI-native testing, attack simulation, health scoring, and SARIF.
MCP server for 1Password service accounts — tools and resources for vaults and credentials
Deterministic security scanning, no model or API key, plus offline-verifiable proof a fix worked.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Insomniac-VibeLabs/two-key and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Two independent keys must turn before an AI agent can act. No human needed.
AI agent authorization and MCP gateway with dual-path authorization. Deterministic bytecode policy combined with AI judge approval, single-use capability tokens, and an encrypted ledger.
🎯 The Problem
AI agents can be given permission to use a tool without being given authority to perform every consequential action that tool can perform.
Traditional tool permissions answer:
"Can this agent call this tool?"
Two-Key asks a different question:
"Is this specific action authorized to execute?"
Two-Key is an authorization layer for AI agents that use tools. Before a consequential tool call executes, Two-Key requires independent authorization through a deterministic policy path and an independent judge path:
Only when both keys turn does Two-Key issue a single-use token, bound to the exact arguments, the signed constitution, and the ledger state. The gateway runs the tool only with that token, and every decision, allowed or denied, is written to an encrypted, hash-chained ledger with a signed head.
What you get:
high_assurance profile asks for judges
from two makers and a yes from a local one.two-key mcp-proxy shows the
agent only the tools you signe