Alternatives
Products that do what shutup-mcp does
Zero-config MCP proxy that hides 99% of tools
- 1
- 2ZA
2019 · zeroserver.io
- 3
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
- 4
- 5
- 6
Zero-dep CLI: one MCP config synced to every agent. A 255-tool listing costs 581 tokens, not 71,929 - schemas never enter context. - activeing123/mcptoon
27d ago · github.com
- 7AH
While building my startup i kept running into the issue where ai agents in cursor create endpoints or code that shouldn't exist, hallucinates strings, or just don't understand the code. ask-human-mcp pauses your agent whenever it’s stuck, logs a question into ask_human.md in your root directory with answer: PENDING, and then resumes as soon as you fill in the correct answer. the pain: your agent screams out an endpoint that never existed it makes confident assumptions and you spend hours debugging false leads the fix: ask-human-mcp gives your agent an escape hatch. when it’s unsure, it calls…
2025 · masonyarbrough.com
- 8HM
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
- 9MS
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
- 10
- 11
- 12
- 13
- 14
- 15JZ
I built a cli tool that gets you started with TypeScript development with zero config. Initially created to solve my own problem but thought it might be useful for others as well. - SWC compiler - TypeScript type check support - Live reload support - .env file support - Path alias support - Typescript script runner - REPL support Please tell me I am not going down a rabbit hole.
2022 · github.com
- 16
- 17
- 18MS
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
- 19MS
2025 · github.com
- 20HA
Hi HN, my name is Philip, I’m the co-founder of Glasskube and one of the creators of HyprMCP. This project started when we did what everyone was doing — building a remote MCP server and launching it. Building the first local MCP server for testing was quite simple, and we had our first tools ready within a day. The next step was turning that into a production-ready remote MCP server. As we exposed the MCP server to our users, we wanted to authenticate them with our existing authentication methods. We dove deep into authentication. Our approach was to build an auth proxy and plug it in front…
Oct 2025 · github.com
- 21MF
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
- 22
- 23MS
2025 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →