@agentage/find-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: catalog.agentage.io
What it contacted
catalog.agentage.io
Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.
Starting it
npx -y @agentage/find-mcp@1.13.5
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
mcp_categories | Returned a result 0.1 s · 2,305 characters |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
mcp_search query, type, category, language, license, limit, page
Search the agentage MCP directory - a public catalog of Model Context Protocol servers crawled from the official registry - for servers matching a keyword, optionally narrowed by type, category, language, or license. Use this FIRST whenever the user wants to discover, find, compare, or pick an MCP server ("is there an MCP for X", "which MCP servers do Y"). Results are ranked by text relevance to the query first, then by popularity, so the best match is on top. Returns a page of lean cards (slug, title, description, category, transport, match_score - text relevance the ranking is based on, details_url). To read one server's full packages, tools, and install command, call mcp_get with the slug from a result; open a card's details_url for the human detail page. Valid category, language, and license values come from the mcp_categories tool, not from guesswork - call it before filtering and pass its labels verbatim, or the call is rejected. Read-only - never installs or runs anything.mcp_get slug
Fetch the complete record for ONE MCP server in the agentage directory by its canonical slug: full description, categories, the packages and remote endpoints it ships, the tools it exposes, a ready-to-run install command, and a README excerpt. Use this after mcp_search to get the depth a result card omits - pass a slug exactly as returned by mcp_search. Slugs are canonical and registry-derived ("io-github-github-github-mcp-server"), NOT the plain product name ("github"); if you pass a plain name anyway it is resolved by search as a fallback - a single confident match returns that server (with `resolved_from` set), anything else returns an error naming the candidate slugs to retry with. No slug yet? call mcp_search first. Read-only.mcp_categories
List the directory's available filter values - every category, language, and license, each with how many servers carry it. Call this BEFORE mcp_search when you intend to filter, so you pass exact, existing values for the type/category/language/license arguments instead of guessing. Takes no input. Read-only.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=22.0.0 |
| Source | github.com/agentage/find-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-kBEMG0J3I23DXwttD/0nWd8WaJtDydt8VRNWoavjyYP6Bm5p34DgKiSKoT4w0xdItStPvXenjKHZ/zJH9DbnJg== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 1.13.5 | 2026-11-16 | Starts with no setup | 3 |
| 1.13.4 | 2026-11-12 | Starts with no setup | 3 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40agentage/find-mcp)
New version out? Ask for a fresh report.