Skip to content
ShadowPhone logo

ShadowPhone MCP server

Which servers in the official MCP registry are ShadowPhone's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-18

← Back to ShadowPhone

Whose server it is
  • Registry nameio.shadowphone/shadowphoneverified in the MCP registry

The registry name sits under shadowphone.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-18
  • Stateanswerschecked 2026-10-18
  • Tools2
  • Server calls itselfshadowphone-mcp-http
  • Server version0.4.0
  • Protocol version2024-11-05

On 2026-10-18 the server answered initialize and tools/list without a sign-in. First answer in 123 ms.

Measured dailydaily checks: 1, the first on 2026-10-19
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer215 ms
  • Space in an agent's context≈ 99 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsB · 75 of 100
  • Parameters without a description: in 1 of 2
  • Not saying whether it only reads or can destroy: 2 of 2

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work.

Tools it offers2 tools · read 2026-10-18
  • public_health_check

    Returns MCP bridge health/version and current UTC time.

  • public_get_latest_release

    Fetches latest desktop release metadata for a platform.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "shadowphone": {
      "type": "http",
      "url": "https://www.shadowphone.io/api/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.