MCP Station
net.mcpstation/stationmcpstation.netstreamable-httpv0.1.0Scanned
Directory of remote MCP servers with daily measured reachability, tools and changes.
8 tools: 2 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MCP Station can do
The MCP Station is published by mcpstation.net, a domain the MCP Registry verified. It has 8 tools. It can create or change data (2 tools: check_overlap and preflight), but cannot delete data. 6 tools only read.
2 tools bring in text other people can write (get_changes and list_categories).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 2Claude Code: ask
check_overlapUse when the user has several MCP servers connected or planned and wants to know if any duplicate each other.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check your MCP servers for matching tool definitions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
preflightUse right before connecting or reconnecting one or more MCP servers, or when a connected server starts failing: one call returns, for each exact registry name, the latest daily che…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Use right before connecting or reconnecting one or more MCP servers, or when a connected server starts failing: one call returns, for each exact registry name, the latest daily check (reachable, authentication, check success 7/30 days, response time), declared risk, tool definition size, changes in the last 7 days (tools, schemas, descriptions, authentication, versions, before and after) and whether the servers you list share tool definitions. Facts measured by MCP Station, not a verdict; it does not run any new check or execute tools. To find servers first use search_servers.
Annotations the server declares
- title: Check MCP servers before connecting
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 6Show 6 read-only tools
get_changesUse when the user asks what changed in the servers they use, or wants to review tool changes before using a server again.Reads text others writeNo findings
Why it is in this group
- The name "get_changes" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it 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 and description changes, new destructive tools, servers that stopped or started answering, new listings, and changes in authentication, MCP version, server version or HTTPS (before and after), per day for the last 30 days. Facts, not verdicts. Give names to watch specific servers.
Annotations the server declares
- title: Changes since a date
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_serverUse 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.No findings
Why it is in this group
- The name "get_server" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get one MCP server
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_server_historyUse 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.No findings
Why it is in this group
- The name "get_server_history" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Daily check history
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_categoriesUse to browse what kinds of MCP servers exist or to get category IDs for search filters: category IDs (stable), names, parents and server counts.Reads text others writeNo findings
Why it is in this group
- The name "list_categories" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- title: List categories
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_serversUse when the user needs an MCP server for a task, or asks whether one exists, works today, or needs a key or sign-in.No findings
Why it is in this group
- The name "search_servers" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search remote MCP servers
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_toolsUse when the user needs a specific capability (a tool) rather than a whole server; to find servers by topic use search_servers.No findings
Why it is in this group
- The name "search_tools" says "search": a word for reading.
Description, as the server wrote it 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'.
Annotations the server declares
- title: Search tools across MCP servers
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:24 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcpstation.net/mcp: tools/list returned 8 tools to an anonymous client, including check_overlap (write), preflight (write)
Posture changes
- Nov 10, 2026
- Tools that change things, listed without credentials: 1 to 2
- Nov 3, 2026
- Tools that change things, listed without credentials: 0 to 1
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
- Tools that change things, listed without credentials: 1 to 2
Tools2 added, 6 changed.+2 added~6 changedView diff
- Added:check_overlapChanges things
- Added:preflightChanges things
- Changed:get_changesOnly readsdescriptioninputSchemaannotations
- Changed:get_serverOnly readsdescriptionannotations
- Changed:get_server_historyOnly readsdescriptionannotations
- Changed:list_categoriesOnly readsdescriptionannotations
- Changed:search_serversOnly readsdescriptioninputSchemaannotations
- Changed:search_toolsOnly readsdescriptioninputSchemaannotations
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 1.View diff
- Tools that change things, listed without credentials: 0 to 1
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http station https://mcpstation.net/mcpclaude mcp add --transport http station https://mcpstation.net/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__station__search_servers",
"mcp__station__search_tools",
"mcp__station__get_server",
"mcp__station__get_server_history",
"mcp__station__get_changes",
"mcp__station__list_categories"
],
"ask": [
"mcp__station__check_overlap",
"mcp__station__preflight"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as station. Review it before you use it.
Capability tags behind 2 rules
- mcp__station__get_changes untrusted-input
- mcp__station__list_categories untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/net.mcpstation/station/verify?hash=1505cd7558bb8892dedcf05d4160ee43065fb02bb7da9abe0070c7cbc682741f" | jq -e '.changed == false'Pinned hash 1505cd7558bb, from Nov 9, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/net.mcpstation/station/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/net.mcpstation/station)Source: MCP Registry. Synced Oct 26, 2026, 06:17 UTC.
MCP Station: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MCP Station safe?
- No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MCP Station delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MCP Station do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the MCP Station have?
- 8 tools: 2 write, 6 read. check_overlap, preflight, search_servers, search_tools, get_server, get_server_history, get_changes and list_categories.
Does the MCP Station need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MCP Station send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MCP Station changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.