Sanctions Screening MCP Server vs Tx Medical Exclusions
A side-by-side look at the Sanctions Screening MCP Server and Tx Medical Exclusions MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Sanctions Screening MCP Server for legal work as a local process; choose Tx Medical Exclusions for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Sanctions Screening MCP Server when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You want tools like
sanctions_screen_name, sanctions_screen_identifier, sanctions_get_designation.
Choose Tx Medical Exclusions when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 57/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View Sanctions Screening MCP Server | View Tx Medical Exclusions |
Tools & capabilities
Sanctions Screening MCP Server tools 7
sanctions_screen_nameScreen a person, company, vessel, or aircraft name against every loaded watchlist at oncesanctions_screen_identifierLook up an IMO number, SWIFT/BIC code, wallet address, or passport or national ID number exactly across every loaded watchlistsanctions_get_designationFetch the full record for one designation by source list and entry ID or published reference numbersanctions_resolve_entityResolve a company name, optionally within a jurisdiction, to ranked GLEIF LEI candidatessanctions_get_entityFetch the GLEIF Level 1 record for an LEI, with a sanctions cross-reference of its names, LEI, and registration numbersanctions_trace_ownershipTrace an LEI's parents and children, optionally cross-referencing every entity in the graphsanctions_list_sourcesList the loaded sources with record counts, licenses, and mirror freshness
Tx Medical Exclusions tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Sanctions Screening MCP Server
{
"mcpServers": {
"sanctions-screening-mcp-server": {
"command": "bunx",
"args": [
"@cyanheads/sanctions-screening-mcp-server@latest"
]
}
}
}
Tx Medical Exclusions
{
"mcpServers": {
"tx-medical-exclusions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-tx-medical-exclusions"
]
}
}
}
Frequently asked questions
Sanctions Screening MCP Server is categorized under Legal and uses a local stdio subprocess. Tx Medical Exclusions belongs to Legal and uses a local stdio subprocess. Pick Sanctions Screening MCP Server for legal work and Tx Medical Exclusions for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Sanctions Screening MCP Server has no declared pricing — check the project's own site. Tx Medical Exclusions is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add sanctions-screening-mcp-server and tx-medical-exclusions as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sanctions Screening MCP Server has a quality signal of 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Tx Medical Exclusions has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.