Hey HN, Adam here.
We built a small MCP example around a single problem:
How do you let an agent use a tool that needs credentials without giving the credentials to the agent?
The demo has two tools. One is open. One is protected.
When the agent calls the protected tool, Keydris checks the policy first:
ALLOW → run the tool
REJECT → stop
The credential stays on the server. The agent never sees it.
We do the check through a small middleware on the MCP server called the KIT Reader.
Repo: https://github.com/keydrisLabs/mcp-auth-keydris-template
We're early. If you're building with MCP, Claude Code or Codex, I'd love to know how you're handling this today and where you think this approach breaks.
We support other elements like integrations etc but would love your feedback
We built a small MCP example around a single problem:
How do you let an agent use a tool that needs credentials without giving the credentials to the agent?
The demo has two tools. One is open. One is protected.
When the agent calls the protected tool, Keydris checks the policy first:
ALLOW → run the tool REJECT → stop
The credential stays on the server. The agent never sees it.
We do the check through a small middleware on the MCP server called the KIT Reader.
Repo: https://github.com/keydrisLabs/mcp-auth-keydris-template
We're early. If you're building with MCP, Claude Code or Codex, I'd love to know how you're handling this today and where you think this approach breaks.
We support other elements like integrations etc but would love your feedback