mcp-sanctions
PulseGate's liveness check found it on 3 Oct 2026; it has been in the index since 2 Sep 2026. How this is checked
mcp-sanctions is an open-source Model Context Protocol server for screening persons and entities against sanctions and watchlists. Developers can integrate its compliance screening capabilities into AI agents and automated risk workflows.
Inferred · not functionally tested
Overview
5 featuresPurpose: Automating sanctions and watchlist screening for people and organizations.
Inferred · not functionally tested
Audience: developers building compliance and risk-screening workflows
Inferred · not functionally tested
Functions: data_extraction, agents
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: Open Source · platforms: WEB · deployment: browser, self_hosted, cli, api_only
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: github.com. These links do not verify the individual claims.
In the Frameworks & SDKs space, mcp-sanctions takes a focused approach. Inferred · not functionally tested: It focuses on automating sanctions and watchlist screening for people and organizations. Inferred · not functionally tested: mcp-sanctions is an open-source project aimed at developers building compliance and risk-screening workflows. Basis unknown · not verified: mcp-sanctions is open source under the Open Source license. Basis unknown · not verified: mcp-sanctions is available on the web, the command line, and API, and it can be self-hosted.
It is developed by atomno-mcp. Inferred · not functionally tested: Key capabilities include person screening, entity screening, and sanctions checks. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Person screening
- Entity screening
- Sanctions checks
- Watchlist screening
- MCP server
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed2 Sep · 16:00 UTCmcp-sanctions seen via MCP Registry (official)Source: MCP Registry (official) · Open
Frequently asked questions about mcp-sanctions
- What is mcp-sanctions?
- Inferred · not functionally tested: Mcp-sanctions focuses on automating sanctions and watchlist screening for people and organizations. It is catalogued under Frameworks & SDKs on PulseGate.
- Who is mcp-sanctions for?
- Inferred · not functionally tested: mcp-sanctions is an open-source project built for developers building compliance and risk-screening workflows.
- Is mcp-sanctions free?
- Basis unknown · not verified: Yes — mcp-sanctions is open source under the Open Source license and free to use.
- What platforms does mcp-sanctions run on?
- Basis unknown · not verified: mcp-sanctions runs on the web, the command line, and API. It can also be self-hosted.
- Is mcp-sanctions still active?
- PulseGate's liveness check found it on 3 Oct 2026.
- What are alternatives to mcp-sanctions?
- Similar projects tracked by PulseGate include sanctions-screening, sanctions-io, and open-sanctions.sanctions-screeningsanctions-ioopen-sanctions
- Who makes mcp-sanctions?
- mcp-sanctions is developed by atomno-mcp.
- Is mcp-sanctions open source?
- Basis unknown · not verified: Yes — mcp-sanctions is open source under the Open Source license.
Similar projects
Closest matches by what these projects do