MCP Station
REMOTE · MCPSTATION.NET
Directory of remote MCP servers with daily measured reachability, tools and changes.
Available components
Last scanned (14 hours ago)
Scores higher than 64% 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. 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 Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 980 tokens (~140/item across 7 items; 7 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Tool “check_overlap” rewrote its description, which is the text the model reads security
- Tool “get_changes” rewrote its description, which is the text the model reads security
- Tool “get_server” rewrote its description, which is the text the model reads security
- Tool “get_server_history” rewrote its description, which is the text the model reads security
- Tool “list_categories” rewrote its description, which is the text the model reads security
- Tool “search_servers” rewrote its description, which is the text the model reads security
- Tool “search_tools” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 67% → 74% ▲ functional
- Schema quality: fair → good functional
- “get_changes” reworded the description of “since” cosmetic
- “search_servers” reworded the description of “limit” cosmetic
- “search_tools” reworded the description of “limit” cosmetic
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Schema quality: 690 → 780 ▼ functional
- New tool “check_overlap” functional
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 71
First indexed and scored.
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://mcpstation.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcpstation.net | CN=WR3,O=Google Trust Services,C=US | 27 Oct 2026 | 25 Jan 2027 | RSA 2048 | SHA256-RSA | 913452c6fb03bd1912dc66e2debf545c |
| SANs: mcpstation.net | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcpstation.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| mcpstation.net. | 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 |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self'; base-uri 'none'; form-action 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcpstation.net/mcp | Verified | 200 | |
| http (plaintext) | http://mcpstation.net/mcp | HTTPS enforced | 301 | https://mcpstation.net/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 →
check_overlap Check your MCP servers for matching tool definitions ~111
Use when the user has several MCP servers connected or planned and wants to know if any duplicate each other. Give the exact registry names of the MCP servers you connect (or plan to). Returns which of them share tool definitions, a remote endpoint or a registry description, compared on the same measurement day, and how many other listings share each one's tool definitions. Facts only, not a judgement. If two share tool definitions, clients that load tool definitions into context may load them twice.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | – |
No output schema declared.
No examples provided.
get_changes Changes since a date ~104
Use when the user asks what changed in the servers they use, or wants to review tool changes before using a server again. Tools added or removed, input schema changes, new destructive tools, servers that stopped or started answering, and new listings, per day for the last 30 days. Give names to watch specific servers.
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | – | – |
| since | string | – | YYYY-MM-DD, e.g. 2026-10-01; default yesterday |
No output schema declared.
No examples provided.
get_server Get one MCP server ~57
Use before connecting a server, or when the user names one: registry data, latest measurements, declared risk, rank parts, connection URLs and tools of one server.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Registry name, e.g. com.example/server |
No output schema declared.
No examples provided.
get_server_history Daily check history ~57
Use when the user asks whether a server has been answering lately: daily check results (reachable, response time) of one server for up to 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| name | string | yes | Registry name |
No output schema declared.
No examples provided.
list_categories List categories ~38
Use to browse what kinds of MCP servers exist or to get category IDs for search filters: category IDs (stable), names, parents and server counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_servers Search remote MCP servers ~305
Use when the user needs an MCP server for a task, or asks whether one exists, works today, or needs a key or sign-in. Do not use for general web search; for one server already known by name use get_server. Find remote MCP servers listed in the Official MCP Registry, with MCP Station's daily measurements. Turn the user's need into words (q) plus filters. Example: 'crypto market data, no API key, working' -> q='crypto market data', auth='none', reachable=true. Results are ordered by relevance first, then by published rank rules (measurements only, no paid placement). similar_to='<registry name>' returns other working servers in the same categories with the same authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | – | Authentication at the last check |
| capability | string | – | Declared at initialize |
| category | string | – | Category ID, e.g. finance.crypto (see list_categories) |
| limit | integer | – | Ask only for as many results as needed (default 10) |
| min_success_7d | number | – | Daily check success over 7 days |
| offset | integer | – | – |
| q | string | – | Words, max 200 characters |
| reachable | boolean | – | true = answered at the last check |
| risk | string | – | Declared by the server's tool hints |
| similar_to | string | – | Registry name of a server to find alternatives for |
| transport | string | – | – |
No output schema declared.
No examples provided.
search_tools Search tools across MCP servers ~205
Use when the user needs a specific capability (a tool) rather than a whole server; to find servers by topic use search_servers. Find individual tools by name and description (as the servers report them in tools/list), with the server each belongs to and its measurements. Example: q='pdf table extraction'.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | string | – | Authentication at the last check |
| capability | string | – | Declared at initialize |
| category | string | – | Category ID, e.g. finance.crypto (see list_categories) |
| limit | integer | – | Ask only for as many results as needed (default 10) |
| min_success_7d | number | – | Daily check success over 7 days |
| offset | integer | – | – |
| q | string | yes | Words, max 200 characters |
| reachable | boolean | – | true = answered at the last check |
| risk | string | – | Declared by the server's tool hints |
| transport | string | – | – |
No output schema declared.
No examples provided.
How do I install the MCP Station server?
MCP Station is a hosted endpoint at https://mcpstation.net/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 · mcpstation.net
claude mcp add --transport http net-mcpstation-station 'https://mcpstation.net/mcp'
What is the MCP Station server?
MCP Station is listed in the public MCP registry as net.mcpstation/station. Directory of remote MCP servers with daily measured reachability, tools and changes. This page covers its hosted endpoint (https://mcpstation.net/mcp).
Is the MCP Station server safe to use?
MCP Station scores 75 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 Station server expose?
MCP Station exposes 7 tools: search_servers, search_tools, get_server, get_server_history, get_changes, and 2 more. Their descriptions and schemas cost roughly 877 tokens of context every time the server is loaded.
Does the MCP Station server require authentication?
No. We connected to MCP Station without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP Station server still maintained?
MCP Station 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.