mcp.tc directory
REMOTE · MCP.TC
Search the mcp.tc directory of MCP servers: URLs, install commands, sign-in types, tools, setup.
Available components
Last scanned (21 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 4 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 561 tokens (~187/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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://mcp.tc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.tc | CN=YE1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 62ce2e5d06a7dee2086adea173cd88717fe |
| SANs: *.mcp.tc, mcp.tc | ||||||
| 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 mcp.tc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tc. | present | 13489 | 13 | Verified |
| mcp.tc. | absent | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tc/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tc/mcp | HTTPS enforced | 301 | https://mcp.tc/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 →
get_server Get MCP server details ~171
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 | Type | Req | Description |
|---|---|---|---|
| client | string | – | Optional: only the setup steps for this client, written out in full. |
| slug | string | yes | The listing's slug from search_servers, e.g. "notion", or its link https://mcp.tc/i/notion. |
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | yes | – |
| auth_note | string | yes | – |
| capabilities | array | – | – |
| category | string|null | – | – |
| category_name | string|null | – | – |
| description | string|null | – | – |
| docs | string|null | – | – |
| endpoint | string|null | yes | The server's own URL (remote servers): what clients connect to |
| env_vars | array | – | – |
| example_prompts | array | – | – |
| headers | array | – | – |
| health | string | – | – |
| history_feed | string | yes | Atom feed of the listing's History |
| history_url | string | yes | The listing's History tab: what mcp.tc's own checks saw change and the server owner's edits, newest first |
| homepage | string|null | – | – |
| install_command | string|null | yes | Command that starts it (local servers) |
| kind | string | yes | – |
| last_changed | string|null | yes | When the History last recorded a change (ISO 8601, UTC) |
| last_checked | string|null | – | – |
| link | string | yes | – |
| name | string | yes | – |
| package | object|null | – | – |
| recent_changes | array | yes | The newest History entries, newest first. Summaries name tools but never quote their descriptions. kind baseline marks where tracking started |
| repository | string|null | – | – |
| server_version | string|null | – | – |
| setup | array | yes | – |
| slug | string | yes | – |
| tagline | string|null | – | – |
| tools | array | yes | – |
| tools_checked | string|null | yes | When mcp.tc last read the tool list (ISO 8601, UTC); null unless tracking is tools |
| tools_count | integer | – | – |
| tracking | string | 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 rea… |
| transport | string|null | – | – |
| vendor | string|null | – | – |
| verified | boolean | yes | – |
| verified_by | string|null | – | – |
No examples provided.
list_categories List categories ~33
The directory's categories with their slugs and how many servers each holds. Pass a slug as the category of search_servers.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
| total_servers | integer | yes | – |
No examples provided.
search_servers Search MCP servers ~195
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 | Type | Req | Description |
|---|---|---|---|
| auth | string | – | 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). |
| category | string | – | Category slug (see list_categories). |
| limit | integer | – | How many results to return. |
| query | string | – | Words to find in the server's name, vendor, tagline or tags, e.g. "postgres" or "github issues". Every word must match. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| more_url | string|null | – | The same search on the website when there are more results |
| results | array | yes | – |
| total | integer | yes | Listings that match, including those not returned |
No examples provided.
How do I install the mcp.tc directory server?
mcp.tc directory is a hosted endpoint at https://mcp.tc/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 · mcp.tc
claude mcp add --transport http tc-mcp-mcp-tc 'https://mcp.tc/mcp'
What is the mcp.tc directory server?
mcp.tc directory is listed in the public MCP registry as tc.mcp/mcp-tc. Search the mcp.tc directory of MCP servers: URLs, install commands, sign-in types, tools, setup. This page covers its hosted endpoint (https://mcp.tc/mcp).
Is the mcp.tc directory server safe to use?
mcp.tc 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 mcp.tc directory server expose?
mcp.tc directory exposes 3 tools: search_servers, get_server, list_categories. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.
Does the mcp.tc directory server require authentication?
No. We connected to mcp.tc directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the mcp.tc directory server still maintained?
mcp.tc directory is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.