Health · Remote MCP server
Clearscreen
Screen people & companies against 12 US sanctions & exclusion lists (OFAC, LEIE, SAM, Medicaid).
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.lvsmanhole/clearscreen- Version
- 1.0.0
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-06-04
- Updated
- 2026-06-04
- Publisher
- lvsmanhole (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/lvsmanhole) · how
- Website
- lvsmanhole.github.io/clearscreen-data/
- Repository
- github.com/lvsmanhole/clearscreen-data
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://clearscreen-mcp.mcpize.run/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Clearscreen
Clearscreen is a remote MCP server: there is nothing to install. Its endpoint is https://clearscreen-mcp.mcpize.run/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More health servers
| Server | Runs |
|---|---|
| China NMPA Medical Device DataStructured China NMPA UDI data for AI agents: devices, registrants, models and registration numbers. | Remote · HTTPLive check: ✓ handshake |
| China PharmaChina Pharma MCP - China-to-Western biotech licensing deals, from SEC filings. | Remote · HTTPLive check: ✓ handshake |
| Chiwawa - AI Agent RegistrySearch and discover AI agents across A2A and MCP protocols. 2,000+ agents with health tracking. | Remote · SSELive check: ✓ SSE reachable |
| Claidex MCPBiomedical failure intelligence platform for terminated trials and translational analysis. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Clinical Fda MCPOpenFDA ilaç geri çağırma kayıtları + ClinicalTrials.gov klinik deney arama, ABD federal açık… | Remote · HTTPLive check: ✗ no handshake |
| Clinical Trial & Medical Research Tracker - buy per-query in-session (trialwatch)Medical research: new trial results tracker. $0.01/query. Register in-session - free testnet funds. | Remote · HTTPLive check: ✓ handshake |
| Clinical Trial DesignPhase 2/3 clinical trial design via gsDesign / gsDesign2: sample size, GS boundaries, multiplicity. | Local · stdio |
| ClinicaltrialsSearch and analyze ClinicalTrials.gov: trials by keyword/condition/drug/status/phase, one study's… | Remote · HTTPLive check: ✓ handshake |