Find MCP - Agentage MCP Directory
REMOTE · CATALOG.AGENTAGE.IO · 2 COMPONENTS
Search the official MCP registry: 17,000+ servers with trust grades, stars, tools, install config.
Available components
Last scanned (8 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 961 tokens (~320/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Sept 26 0
- Stability: 0.97 → pass security
- 2 Sept 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://catalog.agentage.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=catalog.agentage.io | CN=YE1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 655a23212e3df56c50a03053dc5692bbba6 |
| SANs: catalog.agentage.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of catalog.agentage.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| agentage.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://catalog.agentage.io/mcp | Verified | 200 | |
| http (plaintext) | http://catalog.agentage.io/mcp | HTTPS enforced | 301 | https://catalog.agentage.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mcp_categories List directory filter values ~71
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | Category labels and how many servers carry each |
| languages | array | yes | Repository languages and their server counts |
| licenses | array | yes | License names and their server counts |
No examples provided.
mcp_get Get one MCP server ~263
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The canonical slug of one server, taken verbatim from a mcp_search result. Catalog slugs are registry-derived and rarely match the plain product name (e.g. "io-github-github-github-mcp-server", not "… |
| Name | Type | Req | Description |
|---|---|---|---|
| category | array | yes | – |
| description | string | yes | – |
| details_url | string | yes | Human detail page for this server - open it for more information |
| install | object | – | The recommended way to run this server, derived from its first package/remote |
| is_official | boolean | yes | – |
| language | string | – | – |
| license | string | – | – |
| name | string | yes | – |
| packages | array | yes | – |
| readme_excerpt | string | – | First ~2000 chars of the README; open details_url for the full document |
| remotes | array | yes | – |
| resolved_from | string | – | Present only when the requested slug was not canonical and was resolved by name; this is what you asked for - use `slug` from now on |
| slug | string | yes | – |
| title | string | yes | – |
| tools | array | yes | The MCP tools this server exposes, from its live tools/list |
| transport_types | array | yes | – |
No examples provided.
mcp_search Search the MCP directory ~522
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional. Restrict to one category label. Valid values come from the mcp_categories tool - call it to get the exact labels (with counts) and pass one verbatim; anything else is rejected. Omit for no… |
| language | string | – | Optional. Restrict to a repository language (e.g. "TypeScript", "Python"). Exact, case-sensitive; call mcp_categories for valid values. Omit for no language filter. |
| license | string | – | Optional. Restrict to a license, given either as an SPDX id ("MIT", "Apache-2.0") or as the full name mcp_categories lists ("MIT License"). Omit for no license filter. |
| limit | integer | – | Optional. Results per page; defaults to 20, capped at 50. |
| page | integer | – | Optional. 1-based page number; defaults to 1. Use pagination.total_pages to page. |
| query | string | yes | What to search for - a keyword, product, capability, or server name (e.g. "github", "postgres", "web search"). Matched across names, titles, and descriptions. Prefer a single distinctive term over a… |
| type | string | – | Optional. Restrict to one distribution type: npm | pypi | oci | mcpb | nuget, or "remote" for hosted (HTTP) servers. Omit to search every type. |
| Name | Type | Req | Description |
|---|---|---|---|
| pagination | object | yes | – |
| query | string | yes | The query the backend actually ran |
| results | array | yes | – |
No examples provided.
How do I install the Find MCP - Agentage MCP Directory server?
Find MCP - Agentage MCP Directory is a hosted endpoint at https://catalog.agentage.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · catalog.agentage.io
claude mcp add --transport http io-agentage-find-mcp 'https://catalog.agentage.io/mcp'
What is the Find MCP - Agentage MCP Directory server?
Find MCP - Agentage MCP Directory is listed in the public MCP registry as io.agentage/find-mcp. Search the official MCP registry: 17,000+ servers with trust grades, stars, tools, install config. This page covers its hosted endpoint (https://catalog.agentage.io/mcp).
Is the Find MCP - Agentage MCP Directory server safe to use?
Find MCP - Agentage MCP Directory scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Find MCP - Agentage MCP Directory server expose?
Find MCP - Agentage MCP Directory exposes 3 tools: mcp_search, mcp_get, mcp_categories. Their descriptions and schemas cost roughly 856 tokens of context every time the server is loaded.
Does the Find MCP - Agentage MCP Directory server require authentication?
No. We connected to Find MCP - Agentage MCP Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Find MCP - Agentage MCP Directory server still maintained?
Find MCP - Agentage MCP Directory is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Find MCP - Agentage MCP Directory server?
VerifyMCP ran 13 checks on Find MCP - Agentage MCP Directory, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.