Launching today
anlyon.dev
The MCP registry, sorted by what each tool can do
0 followers
The MCP registry, sorted by what each tool can do
0 followers
A free index of the official MCP registry. Each tool is sorted by what it does: reads, changes things, can't be undone, or deletes or cancels. Paste your MCP config to audit it, pin a lockfile that fails CI when tools change, and follow change feeds.
Free
Launch Team
Framer AI AgentsDesign and publish professional sites with AI
Promoted
Hi Product Hunt, I'm Sohaib, founder of Anlyon.
I kept adding MCP servers to agents without knowing what their tools could do. A server is called "GitHub" or "Compute Engine". It doesn't tell you which of its 30 tools can delete a VM or merge a pull request.
anlyon.dev reads the tool definitions of servers in the official MCP registry and puts each tool in one of four groups: reads, changes things, can't be undone, or deletes or cancels. Every tool shows why it landed there: the verb in its name, its description, its inputs and the server's own annotations.
You can:
paste your MCP config and see everything your agent can do across servers, including paths private data could take out, and get a Claude Code permissions block
pin a lockfile that fails CI when a server changes its tools
follow change feeds for the whole index or for one server
What it doesn't do: it never signs in and never calls a tool. Servers that ask for sign-in before they list tools show no tools yet, and local (stdio) servers are listed without tools for now. The checks are fixed rules with no model in the loop. A scan is a point in time, not a safety guarantee.
It's free, built by the team behind Anlyon (https://anlyon.com).
Which server should we look at next, and did you spot a tool in the wrong group?