Agentage MCP server
Featured official server
3 tools · Last check that passed 4 Nov 2026, 12:15 UTC
Agentage's own remote MCP server, Find MCP, gives an agent search across Agentage's public catalog of MCP servers, crawled from the official MCP Registry, with each server's details, tools and install configuration, with no sign-in. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 3 tools
| Tool | Counted as |
|---|---|
mcp_categories | Said to only read |
mcp_get | Said to only read |
mcp_search | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
21 of the last 21 checks passed
A check passes when the server lists its tools. Checked at https://catalog.agentage.io/mcp.
Recent changes
No change seen across the last 21 checks that passed.
From the scan of 4 Nov 2026, 12:43 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Agentage's tools change.
One email when Agentage's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Results describe servers made by other people, with the install configuration for each, so a server an agent finds here and installs runs someone else's code. Agentage's entry in the official MCP Registry
- Server descriptions, READMEs and tool lists written by other servers' authors come back to the agent as text, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Agentage's own settings, as its documentation describes them. Stackduke has not tested them.
- Agentage describes its catalog API as public and read-only, with no key and no signup, so we recommend connecting the MCP server with no Agentage credentials. Agentage's MCP Catalog API reference
- Mark server descriptions and READMEs from this server as untrusted external content, as OWASP advises, so it has less influence on what the agent does. OWASP, prompt injection
- Keep a person approving the install of any server the agent finds, as OWASP advises for high-risk actions. OWASP, prompt injection
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.