Alternatives
Products that do what MCP Secrets Vault – Local MCP proxy to keep API keys out of LLM context does
- 1
- 2
- 3OS
2024 · github.com
- 4AV
Hey HN! Today we're launching Agent Vault - an open source HTTP credential proxy and vault for AI agents. Repo is at https://github.com/Infisical/agent-vault, and there's an in-depth description at https://infisical.com/blog/agent-vault-the-open-source-crede.... We built Agent Vault in response to a question that been plaguing the industry: How do we give agents secure access to services without them reading any secrets? Most teams building agents have run into this exact problem: They build an agent or agentic system and come to realize at some point…
Apr 2026 · github.com
- 5
hey HN, Jonathan and Guy here, creators of OneCLI (https://onecli.sh/). OneCLI is an open source vault for AI Agents. Traditional vaults are used to store your secrets and, on demand, provide them to you all in a secure way, trusting the person to keep them safe. We figured that in the agent's world, this is not the case, as you don't know what happens with the secret after it's delivered to the agent, or where it was saved. Or maybe someone even manipulated them to hand them over... From that understanding, we decided to build a network gateway that sits between your AI…
Jul 2026 · github.com
- 6OV
We built OneCLI because AI agents are being given raw API keys. And it's going about as well as you'd expect. We figured the answer isn't "don't give agents access," it's "give them access without giving them secrets." OneCLI is an open-source gateway that sits between your AI agents and the services they call. You store your real credentials once in OneCLI's encrypted vault, and give your agents placeholder keys. When an agent makes an HTTP call through the proxy, OneCLI matches the request by host/path, verifies the agent should have access, swaps the placeholder for the real…
Mar 2026 · github.com
- 7
- 8
- 9AM
Hi there, me and some friends were inspired by Simon Willison's recent post on the "lethal trifecta" (https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/ ) and started building a gateway to defend against it. The idea: instead of connecting an LLM directly to multiple MCP servers, you point them all through a Gateway. The Gateway: - Connects to each MCP server and inspects their tools + requirements - Classifies tools along the "trifecta" axes (private data access, untrusted content, external comms) - When all three conditions are about to align in a…
Sep 2025 · github.com
- 10GS
Anthropic's Model Context Protocol (MCP) has made it easy to spin up servers that expose tools and data to LLMs. A lot of these MCP servers run locally because they need access to your files, shell, browser, etc. The problem: they typically run with the same privileges as your user. If a server is buggy, misconfigured, or prompt-injected, it can do anything you can do: read SSH keys, exfiltrate dotfiles, poke around in private repos, etc. Our research group is working on this by adding a security manifest (inspired by the Android app manifest) plus a local policy enforcement engine that…
Nov 2025 · guardiagent.com
- 11CR
2023 · github.com
- 12
Free MCP for security AI: live BGP, DNS, threat graph
May 2026 · whisper.security
- 13
Wireshark for MCP. A transparent proxy that shows every real tool call between your AI client and your MCP servers, live in your terminal. - kerlenton/mcpsnoop
Jul 2026 · github.com
- 14ST
Hi! After learning about MCP, I'm really excited about the future of provider-agnostic, re-usable tooling. Unfortunately I've found that while it's easy to implement an MCP server for use with tools that support it (such as Claude Desktop), it's not as easy to implement your own support (such as integrating an MCP server into your own LLM application). We implemented a thin MCP wrapper that easily integrates with Mirascope calls so that you can hook up an MCP server and client super easily to any supported LLM provider. Excited to see what people build with this!
2025 · mirascope.com
- 15MN
Give a local MCP server a public URL with one command. No accounts, no signup — anonymous, ephemeral, OAuth 2.1-protected tunnels for MCP servers.
5d ago · terragohan.github.io
- 16MS
Hi HN! We kept seeing devs get pwned through MCP tools in ways that security scanners completely miss. So we built an open-source analyzer to catch these attacks. Our first OSS by Mighty team. The problem: At Defcon, we saw MCP exploits with 100% success rate against Claude and Llama. Three attack patterns: Hidden Unicode in "error messages" - Paste a colleague's error into Claude, your SSH keys get exfiltrated Trusted tool updates - That database tool you've used for months? Last week's update added credential theft Tool redefinition - Malicious tool redefines "deploy to prod" to run…
2025 · github.com
- 17
- 18VO
2020 · github.com
- 19
- 20MG
Many teams connecting LLMs to external tools eventually encounter the same architectural issue: as more tools and agents are added, the integration pattern becomes an N×M mesh of direct connections. Each agent implements its own auth, retries, rate limiting, and logging; each tool needs credentials distributed to multiple places and observability becomes fragmented. We built LLM gateway with this goal to provide a single place to manage authentication, authorization, routing, and observability for MCP servers, with a path toward a more general agent-gateway architecture in the future. The…
Dec 2025 · truefoundry.com
- 21
- 22
- 23MC
2025 · github.com
- 24AA
At my last company, we connected Claude Code and Cursor to almost all our internal services via MCP. It made the team incredibly fast, but we hit a wall: permissions. If you give an agent "Read Only" access, it can’t actually fix anything. If you give it "Write" access, it’s only a matter of time before a hallucination or a bad prompt results in a deleted database or a nuked production bucket. We had a few "close calls" that convinced us that simply reducing IAM permissions makes agents useless. I built Armour (https://github.com/fuushyn/armour) to solve this. It’s a…
Jan 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →