mcpbeat

Entity Screen MCP Server

com.dropwatchhq/entity-screen
answering

Entity Screen is answering right now. Last checked moments ago. It exposes 2 tools.

Screen a business or person for exclusions, debarment, and sanctions (SAM.gov, OFAC).

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
68 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 0 min ago.

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

Available tools 2

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

resolve
resolve_entity
Resolve a real-world entity across regulated datasets and return its canonical identity plus all linked identifiers (ticker, CIK, UEI, DUNS, NPI). Use to cross-walk a name to its federal/SEC/health identifiers.
screen
screen_entity
Screen a company/provider/vendor/counterparty for risk before onboarding. Resolves the entity across SEC, USAspending, NPI, NIH and FDA, then checks federal exclusion lists (OIG LEIE, SAM.gov), FDA enforcement/recalls, and absence signals (stopped filing, lapsed activity). Returns a risk score plus sourced, neutral evidence with links.

Endpoints

URLTransportStateLatencyChecked
https://screen.dropwatchhq.com/mcp streamable-http answering 68 ms 0 min ago

Entity Screen — questions

Answers built from our own checks of this server.

What can Entity Screen do?
It exposes 2 tools, read directly from the server on our last check. Among them: resolve_entity, screen_entity. 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 Entity 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 68 ms. The bar chart above shows every period we have measured.
How do I connect Entity 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 Entity Screen need an API key?
No. Entity Screen completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Entity Screen?
It answers our handshake in 68 ms on average, which is faster than 94% 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.