MCP Station

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.

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.

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.

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.

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.

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.

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.

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