mcpbeat

Phoenix Screen MCP Server

com.dropwatchhq/phoenix-screen
answering

Phoenix Screen is answering right now. Last checked 2 min ago. It exposes 1 tools.

Phoenix/rebrand relink detection: links a debarred principal to a newly-formed business entity.

Uptime history 44 hours of history
44 hours agonow
100.0%
Uptime 24h
92 of 92 checks
1
Tools
read from the server
72 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add phoenix-screen --transport http https://phoenix.dropwatchhq.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "phoenix-screen": {
      "url": "https://phoenix.dropwatchhq.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.phoenix-screen]
url = "https://phoenix.dropwatchhq.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "phoenix-screen": {
      "url": "https://phoenix.dropwatchhq.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "phoenix-screen": {
      "url": "https://phoenix.dropwatchhq.com/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

phoenix
phoenix_relink_check
Detect a phoenix / rebrand relink that exact-match screeners miss. Given a principal or entity name (e.g. a debarred contractor, an excluded provider, or an OFAC-listed party), this fuzzy-relinks it to NEWLY-FORMED Secretary-of-State business entities that share the name AND a second independent signal (principal address or named registered agent), while filtering out shared commercial registered-agent addresses. Returns NON-CONCLUSORY review flags with the full evidence chain and primary-source links — a research lead for human diligence, never a determination of wrongdoing. Use during M&A diligence, vendor/counterparty onboarding, or compliance screening.

Endpoints

URLTransportStateLatencyChecked
https://phoenix.dropwatchhq.com/mcp streamable-http answering 65 ms 2 min ago

Phoenix Screen — questions

Answers built from our own checks of this server.

What can Phoenix Screen do?
It exposes 1 tools, read directly from the server on our last check. Among them: phoenix_relink_check. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Phoenix Screen working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 72 ms. The bar chart above shows every period we have measured.
How do I connect Phoenix Screen?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Phoenix Screen need an API key?
No. Phoenix Screen completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Phoenix Screen?
It answers our handshake in 72 ms on average, which is faster than 93% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.