This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
anlyon.dev
The MCP registry, sorted by what each tool can do
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.
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.
Which server should we look at next, and did you spot a tool in the wrong group?
About anlyon.dev on Product Hunt
“The MCP registry, sorted by what each tool can do”
anlyon.dev was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #292 on the daily leaderboard. 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.
On the analytics side, anlyon.dev competes within Developer Tools, Artificial Intelligence and Security — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how anlyon.dev performed against the three products that launched closest to it on the same day.
Who hunted anlyon.dev?
anlyon.dev was hunted by Muhammad Sohaib. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of anlyon.dev including community comment highlights and product details, visit the product overview.
Muhammad Sohaib
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?