Dropwatch Entity Screen MCP

An MCP server that allows AI agents to screen business entities or persons against federal exclusions, debarment, and sanctions lists such as SAM.gov and OFAC. It provides a pay-per-call model using x402 cryptocurrency payments on the Base network, enabling autonomous risk assessment without traditional API keys.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-06Operated by dropwatchhq

MCP endpoint (Streamable HTTP)

https://screen.dropwatchhq.com/mcp

Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 0 of 2 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 6, 2026, 2:00 PM UTC
Passed Official MCP Registry namespace is tied to dropwatchhq.com · Nov 6, 2026, 1:58 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 6, 2026, 1:58 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Screen a business entity for federal exclusions and sanctions
Resolve entity data across SEC and LEI records
Perform deduped exclusion/sanctions cross-walk checks

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: com.dropwatchhq/entity-screen@1.0.0 Project website

Protocol and capabilities

Server: entity-screen 1.0.0
MCP protocol negotiated in check: 2024-11-05
Tools: 2 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {}
}

Tools

2 advertised

screen_entity

Advertised by the server during the last successful anonymous check.

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.

screen_entity input schema

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Legal/business name or ticker of the entity to screen"
    }
  }
}

resolve_entity

Advertised by the server during the last successful anonymous check.

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.

resolve_entity input schema

{
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Entity name or ticker"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

2026-11-06: 1 of 1 checks answered
2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 352 ms
95th percentile latency: 352 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 6, 2026, 2:00 PM UTC · probe · passed · 352 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http dropwatch-entity-screen-mcp https://screen.dropwatchhq.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add dropwatch-entity-screen-mcp --url https://screen.dropwatchhq.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable dropwatch-entity-screen-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "dropwatch-entity-screen-mcp": {
      "url": "https://screen.dropwatchhq.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "dropwatch-entity-screen-mcp": {
      "type": "streamableHttp",
      "url": "https://screen.dropwatchhq.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start dropwatch-entity-screen-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "dropwatch-entity-screen-mcp": {
      "type": "http",
      "url": "https://screen.dropwatchhq.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http dropwatch-entity-screen-mcp https://screen.dropwatchhq.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://screen.dropwatchhq.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "dropwatch-entity-screen-mcp": {
      "serverUrl": "https://screen.dropwatchhq.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Dropwatch Entity Screen MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 6,262

Do you run Dropwatch Entity Screen MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing