Sanction
Approval and budget checks before agent spending or tool use. Cooperative MCP; host must ask.
Open the source (opens github.com) https://github.com/ericlovold/sanction
Before you use it
- Runs on someone else's server: what you send it leaves your machine.
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: SANCTION_API_KEY. Use a key with the least access you can.
What it is
MCP servers from io.github.ericlovold.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
sanction-mcp@0.10.0
From the server's entry in the official MCP Registry
Remote endpoint (streamable-http)
https://getsanction.com/mcp
From the server's entry in the official MCP Registry
Settings it asks for
SANCTION_API_KEYsecret required · Agent API key (pxy_...). Create one at https://getsanction.com or via POST /api/v1/wallets then POST /api/v1/agents.SANCTION_WALLET_ID· Optional override for sanction_wallet_status; by default the wallet derives from the agent key.SANCTION_API_URL· Sanction API base URL.
Related
-
Screen people, companies and vessels against US OFAC, UK and Canadian sanctions lists.
sanctionscreen-mcp@0.1.0 -
Screen people, companies and vessels against US OFAC, UK and Canadian sanctions lists.
sanctionsnorth-mcp@0.1.0 -
Sanctions Io
MCP serverssanctions.io MCP — wraps the sanctions.io Screening API (api.sanctions.io)
@pipeworx/mcp-sanctions-io@0.2.1 -
sanctionwise
MCP serversVerified UK sanctions screening for AI agents — official FCDO UK Sanctions List, not guesses.
sanctionwise@0.1.1 -
SanctionScreen
MCP serversScreen counterparties and enrich companies for AI agents — sanctions checks, cited sources.
-
sanctions.io MCP by usefulapi
MCP serversScreen names against sanctions, PEP and watchlists; list screening sources in sanctions.io.