67 npm MCP servers, started in a sandbox and logged
Emerged finds new products worth a look, daily — what’s new today
A signed, append-only daily log of what public MCP servers say their tools do
If your agents call third-party MCP servers, this shows how often their tool descriptions quietly change under you, with proof.
A nightly crawler visits every endpoint in the official MCP registry without credentials and stores the exact tool names, descriptions and schemas it gets back in an RFC 6962 Merkle tree with signed tree heads, so nothing can be rewritten later. After 38 unbroken days: 13,997 endpoints, 56.4% open without auth, 755,221 observations. 19.2% changed their tools within a day, almost always keeping the name while editing the description, and two operators run about 30% of servers. By Yassine Houta; licence not yet set.
67 npm MCP servers, started in a sandbox and logged
A local ledger of every tool call your coding agents make
A local gate on where your agent is allowed to send things
A daily census of which MCP servers and skills agents actually run
Reads a codebase's commits for the risks an acquirer would find, with citations
Native x64dbg plugin that lets AI assistants drive the debugger over MCP