Search the mcp.tc directory of MCP servers from your assistant. Find servers by name, task or category, then get each one's own URL or install command, sign-in type, tools, recent tool changes and setup steps for your client. Read-only, no sign-in.
Scored across 3 tools
Each tool has a clearly distinct role: search_servers discovers listings, get_server fetches full detail for one listing, and list_categories enumerates taxonomy. There is no overlap, and the descriptions explicitly cross-reference each other (pass a slug to search_servers; call get_server with a slug), which removes ambiguity.
All three names follow a strict verb_noun snake_case pattern: get_server, list_categories, search_servers. Noun targets (server/categories/servers) map cleanly to the action verbs, with no stylistic deviations.
Three tools is on the lean side but each earns its place in a read-only directory browsing domain: discovery, taxonomy, and detail retrieval. It is slightly thin (no dedicated pagination or client-specific browse tool), but nothing feels redundant or missing at a structural level.
The core read-only lifecycle is fully covered: browse categories, search the directory, then fetch a listing's endpoint, install command, auth model, and per-client setup steps. Minor gaps exist around advanced filtering or listing enumeration limits, but agents can work around them via the reciprocal slug references between search and get.
Everything about one listing: what it does, its tools, how it signs in, the server's own endpoint URL or install command, and setup steps for Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI and a generic JSON config. Setup always uses the vendor's own URL or package. It also returns the listing's recent changes: tools added, removed or changed and new versions that mcp.tc's periodic checks found, and edits by the server's owner.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The listing's slug from search_servers, e.g. "notion", or its link https://mcp.tc/i/notion. | |
| client | No | Optional: only the setup steps for this client, written out in full. |
| Name | Required | Description |
|---|---|---|
| auth | Yes | |
| docs | No | |
| kind | Yes | |
| link | Yes | |
| name | Yes | |
| slug | Yes | |
| setup | Yes | |
| tools | Yes | |
| health | No | |
| vendor | No | |
| headers | No | |
| package | No | |
| tagline | No | |
| category | No | |
| endpoint | Yes | The server's own URL (remote servers): what clients connect to |
| env_vars | No | |
| homepage | No | |
| tracking | Yes | What the History can see. tools: mcp.tc reads the tool list every 3 hours. version: no tool list, only new versions (a local npm or PyPI package, or the version a server reports). listing: mcp.tc reads neither its tools nor its version, so only edits by the server's owner are recorded |
| verified | Yes | |
| auth_note | Yes | |
| transport | No | |
| repository | No | |
| description | No | |
| history_url | Yes | The listing's History tab: what mcp.tc's own checks saw change and the server owner's edits, newest first |
| tools_count | No | |
| verified_by | No | |
| capabilities | No | |
| history_feed | Yes | Atom feed of the listing's History |
| last_changed | Yes | When the History last recorded a change (ISO 8601, UTC) |
| last_checked | No | |
| category_name | No | |
| tools_checked | Yes | When mcp.tc last read the tool list (ISO 8601, UTC); null unless tracking is tools |
| recent_changes | Yes | The newest History entries, newest first. Summaries name tools but never quote their descriptions. kind baseline marks where tracking started |
| server_version | No | |
| example_prompts | No | |
| install_command | Yes | Command that starts it (local servers) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine behavioral context: setup output 'always uses the vendor's own URL or package' (a trust/sourcing guarantee) and that it surfaces changes detected by mcp.tc's periodic checks plus owner edits. It stops short of noting rate limits or freshness/pagination of those change checks.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The key scope statement is front-loaded in the first clause, and the two flowing sentences are dense rather than padded. The exhaustive enumeration of ten client names is the one stretch that costs length without adding decision-relevant information, since the schema already lists them.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter read tool with annotations and an output schema, the description is complete enough to call correctly. Most of its length re-describes return values that the output schema already covers, which is slightly redundant, but nothing an agent needs is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both parameters are already fully documented, including the client enum. The description adds marginal value by naming all ten client targets, reinforcing what the 'client' parameter selects, but it introduces no syntax or format detail beyond the schema. Baseline 3 for a schema-documented tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Opens with a specific verb+resource ('Everything about one listing'), then enumerates exactly what that means: description, tools, sign-in, endpoint/install command, setup steps, recent changes. The scoping phrase 'one listing' inherently distinguishes it from the sibling search_servers and list_categories without needing to name them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description is entirely about what the tool returns; it never states when to call it versus search_servers, nor prerequisites such as needing a slug obtained from a prior search. The only usage hint (slug comes 'from search_servers') lives in the schema, not the description. An agent must infer the workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The directory's categories with their slugs and how many servers each holds. Pass a slug as the category of search_servers.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| categories | Yes | |
| total_servers | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is fully covered without the description. The description adds the return shape (slugs + counts) and a cross-tool linkage, but offers nothing else the annotations don't already establish.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with zero filler; the content description is front-loaded and the usage hint follows tightly. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values needn't be explained, and annotations carry the safety profile. The description is nearly complete for a simple no-arg list tool, missing only explicit guidance on when this lookup precedes search_servers.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters and the schema coverage is trivially complete, so the baseline of 4 applies. The description's instruction about the slug is about another tool's argument, not this one's, so it adds no parameter meaning here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies a specific resource (the directory's categories) and what each entry carries (slugs and server counts), which clearly separates it from get_server and search_servers. The verb is only implied ("List" comes from the name/title), but the scope is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
"Pass a slug as the category of search_servers" implies the downstream workflow this tool feeds, which is useful. However, it never states when to call this tool versus search_servers directly, nor any prerequisite for the flow, leaving usage to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search the mcp.tc directory of MCP servers by keyword, category or how they connect. Returns compact results, featured servers first, then the most viewed on mcp.tc, each with its slug and mcp.tc link. Call get_server with a slug for the endpoint URL, install command and setup steps. With no arguments it lists the directory in that order.
| Name | Required | Description | Default |
|---|---|---|---|
| auth | No | none: remote server that needs no sign-in. sign-in: remote server that needs OAuth sign-in or an API key (or offers optional sign-in). local: runs on your computer (npx, uvx, docker). | |
| limit | No | How many results to return. | |
| query | No | Words to find in the server's name, vendor, tagline or tags, e.g. "postgres" or "github issues". Every word must match. | |
| category | No | Category slug (see list_categories). |
| Name | Required | Description |
|---|---|---|
| count | Yes | |
| total | Yes | Listings that match, including those not returned |
| results | Yes | |
| more_url | No | The same search on the website when there are more results |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavioral value beyond them: compact results, featured-first then most-viewed ordering, and the returned fields (slug and mcp.tc link).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, zero waste, and the core purpose is front-loaded ahead of the sibling handoff and the no-args case. Each sentence carries distinct information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite an output schema existing, the description still summarizes result shape and ordering, and it covers the empty-argument case and the follow-up tool. Nothing needed to invoke or chain this tool is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all four parameters including the enums and limit bounds are fully documented in the schema. The description only gestures at the same axes ('keyword, category or how they connect') without adding format or syntax beyond what the schema already provides, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Search the mcp.tc directory of MCP servers') and qualifies the search axes (keyword, category, connection type). It is immediately distinguishable from get_server (detail lookup) and list_categories.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent onward: 'Call get_server with a slug for the endpoint URL, install command and setup steps,' and explains the no-argument behavior. It gives clear usage context but does not say when to prefer list_categories instead.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_serverlist_categoriessearch_servers
Add one secure layer between your agents and this server.