Alternatives
Products that do what Vouqis does
Know if your MCP server actually works
- 1
Test MCP servers like a real AI client, not just a ping
May 2026 · openstatus.dev
- 2MS
Hi HN, I've been building MCPSpec, an open-source CLI for MCP server reliability. Record sessions, generate mock servers, catch Tool Poisoning, and fail your CI build when something's wrong — without writing test code. There are ways to validate MCP servers today — the MCP Inspector, ad-hoc SDK scripts, unit tests for server internals — but nothing that handles regression detection, security auditing, mock generation, and CI pass/fail checks in one tool. MCPSpec does that: 1. Record a session against your real server, replay it after changes to catch regressions 2. Generate a standalone…
Feb 2026 · light-handle.github.io
- 3
Give AI agents access to real-time data across 200+ apps
May 2026 · apideck.com
- 4
- 5
- 6
- 7MS
I noticed the growing security concerns around MCP (https://news.ycombinator.com/item?id=43600192) and built an open source tool that can detect several patterns of tool poisoning attacks, exfiltration channels and cross-origin manipulations. MCP-Shield scans your installed servers (Cursor, Claude Desktop, etc.) and shows what each tool is trying to do at the instruction level, beyond just the API surface. It catches hidden instructions that try to read sensitive files, shadow other tools' behavior, or exfiltrate data. Example of what it detects: - Hidden instructions…
2025 · github.com
- 8AF
I built an unofficial CLI and MCP server for Lambda cloud GPU instances. The main idea: your AI agents can now spin up and manage Lambda GPUs for you. The MCP server exposes tools to find, launch, and terminate instances. Add it to Claude Code, Cursor, or any agent with one command and you can say things like "launch an H100, ssh in, and run big_job.py" Other features: - Notifications via Slack, Discord, or Telegram when instances are SSH-ready - 1Password support for API keys - Also includes a standalone CLI with the same functionality Written in Rust. MIT licensed. Note: This is an…
Jan 2026 · github.com
- 9
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
- 10
- 11RA
Hi HN, We’re building security tooling around agentic AI systems. Today, we're releasing our public MCP catalog with detailed risk analysis for every MCP server we've found on the internet: https://mcp.armor1.ai/mcp-directory We all love agents and the power that MCPs unlock: suddenly your AI assistant can query databases, manage files, call APIs, and interact with the real world. But when we started adopting MCPs ourselves, we kept running into the same nagging questions: Is this MCP safe? Where is my data actually going? Could it execute destructive actions? Is it…
Feb 2026 · mcp.armor1.ai
- 12MF
Hey everyone, I've wanted an easy way to control which mcp server tools are available to clients. So for example, I might want a gmail server to only expose the read tool (but not send, delete etc). I figured if I create a cli for spawning mcp servers, I could intercept the stdin, stdout, stderr etc and modify what the clients see when they are making calls to list tools, resources, and prompts. Well it worked! In the initial version you can easily add a server to claude with a safe list of tools: npx -y mcpgod add @modelcontextprotocol/server-everything --client claude --tools=echo,add…
2025 · github.com
- 13MR
Hi HN, I'm Vlad. I've been building MCP servers and related tooling for a while now, and I kept hitting a class of bug that no unit test caught: someone on the team renames a tool parameter or tweaks a tool description, all the tests pass, but the AI agent that was calling that tool silently breaks. This happens because the model reads tool descriptions and parameter schemas to decide which tool to call and how, so a renamed parameter or a reworded description isn't just a cosmetic change — it directly affects the model's behavior. The MCP spec doesn't have tool versioning available yet, and…
Mar 2026 · github.com
- 14
- 15MT
Recently I was trying to use an MCP server to pull data from a service, but hit a limitation: the MCP didn't expose the data I needed, even though the service's REST API supported it. So I wrote a quick CLI wrapper around the API. Worked great, except Claude Code had no structured way to know what my CLI does or how to call it. For `gh` or `curl` the model can learn from the extensive training data, but for a tool I just wrote, it was stabbing in the dark. MCP solves this discovery problem, but it does it by rebuilding tool interaction from scratch: server processes, JSON-RPC transport,…
Feb 2026 · github.com
- 16
- 17
Score any MCP server's agent-readiness in 30 seconds
Jun 2026 · isyourmcpready.com
- 18HM
We built a Rust MCP server, which wraps the excellent headless terminal (HT)[1] to makes it available for agentic coding tools. Most agentic coding tools struggle with blocking, interactive terminal tools (all the boilerplate generator, infra CLI tools etc). This is because many existing CLI dev tools are built for humans and require interactive input. We built this so agentic coding tools (Claude Code, Cursor, Memex, etc) can “see” and “interact” with terminals exactly like humans do. In our demo video [2], you'll see it operating vim/emacs just as a human would - selecting options,…
2025 · github.com
- 19SU
2025 · github.com
- 20MS
Hey HN, Gal, Nir and Doron here. Over the past 2 years, we've helped teams debug everything from prompt issues to production outages. We kept running into the same problem: Jumping between our IDEs and our observability dashboards. So, we built an open-source MCP server that connects any OpenTelemetry backend (Grafana, Jaeger, Datadog, Dynatrace, Traceloop) to our dev environment using an MCP. While there are many MCP servers built for specific providers (like Datadog’s - https://docs.datadoghq.com/bits_ai/mcp_server), they’re closed source (so we can’t easily extend…
Nov 2025 · github.com
- 21
- 22MT
At our company we needed some sort of unified logging for our AI agents (devs using cursor, internal agents for checking documents, handling client requests etc) and we came up with a tool that we've decided to make available as a SaaS. With it your agents will report their progress automatically, and you'll get a unified log across projects that you can monitor on your dashboard, query through our api, set up slack and zapier hooks or even push notifications to your mobile. You can try it out for free, any feedback would be most appreciated, thanks.
2025 · taskerio.com
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →