# MCP Station (remote · mcpstation.net)

Directory of remote MCP servers with daily measured reachability, tools and changes.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcpstation.net`: 75/100 (this document), [markdown](https://verifymcp.io/servers/net-mcpstation-station/mcpstation.md), [page](https://verifymcp.io/servers/net-mcpstation-station/mcpstation)

## Channel facts

- Endpoint: `https://mcpstation.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 74% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http net-mcpstation-station 'https://mcpstation.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "net-mcpstation-station": {
      "url": "https://mcpstation.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-mcpstation-station": {
      "type": "http",
      "url": "https://mcpstation.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.net-mcpstation-station]
url = "https://mcpstation.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-mcpstation-station": {
      "type": "remote",
      "url": "https://mcpstation.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-mcpstation-station --url 'https://mcpstation.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-mcpstation-station:
    url: "https://mcpstation.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-mcpstation-station": {
      "Transport": "http",
      "Url": "https://mcpstation.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-mcpstation-station -t streamable-http -u 'https://mcpstation.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-mcpstation-station": {
      "type": "http",
      "url": "https://mcpstation.net/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 75, +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.

### 2026-11-01 (score 74, +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.

### 2026-10-31 (score 73, +1)

- [security] 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
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 67% → 74%
- [functional] Schema quality: fair → good
- [cosmetic] “get_changes” reworded the description of “since”
- [cosmetic] “search_servers” reworded the description of “limit”
- [cosmetic] “search_tools” reworded the description of “limit”

### 2026-10-29 (score 72, +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.

### 2026-10-28 (score 71, 0)

- [functional regression] Schema quality: 690 → 780
- [functional] New tool “check_overlap”

### 2026-10-27 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 71)

First indexed and scored.

## MCP tools (7)

### `search_servers` (~305 tokens)

Search remote MCP servers

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.

Input parameters:

- `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)

### `search_tools` (~205 tokens)

Search tools across MCP servers

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'.

Input parameters:

- `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, required): Words, max 200 characters
- `reachable` (boolean): true = answered at the last check
- `risk` (string): Declared by the server's tool hints
- `transport` (string)

### `get_server` (~57 tokens)

Get one MCP server

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.

Input parameters:

- `name` (string, required): Registry name, e.g. com.example/server

### `get_server_history` (~57 tokens)

Daily check history

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.

Input parameters:

- `days` (integer)
- `name` (string, required): Registry name

### `get_changes` (~104 tokens)

Changes since a date

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.

Input parameters:

- `names` (array)
- `since` (string): YYYY-MM-DD, e.g. 2026-10-01; default yesterday

### `check_overlap` (~111 tokens)

Check your MCP servers for matching tool definitions

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.

Input parameters:

- `names` (array, required)

### `list_categories` (~38 tokens)

List categories

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-mcpstation-station/mcpstation#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 71

## Common questions

### 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.

### What did VerifyMCP test on the MCP Station server?

VerifyMCP ran 13 checks on MCP Station, 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.

## Links

- Remote endpoint: https://mcpstation.net/mcp
- Website: https://mcpstation.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-mcpstation-station/mcpstation.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-mcpstation-station/mcpstation/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/net-mcpstation-station/mcpstation.json
- HTML version of this page: https://verifymcp.io/servers/net-mcpstation-station/mcpstation