Local MCP capabilities provider for Expo
SENTINEL Compliance Intelligence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
AML/CFT compliance oracle: wallet screening, sanctions, PEPs, jurisdiction risk.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http sentinel-compliance-intelligence-mcp https://mru-oracle.com/mcp
# 2 — ask your agent for something these tools do
# screen_entity, screen_wallet, get_jurisdiction_risk and 9 more
SENTINEL Compliance Intelligence costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http sentinel-compliance-intelligence-mcp https://mru-oracle.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Screen one person or organisation name, including aliases, against sanctions lists (US, EU, UK, UN, Canada, Australia and national lists aggregated by OpenSanctions), politically exposed persons, wanted persons (incl. Interpol Red Notices), development-bank and US debarments, crypto-linked entities, ransomware groups and OFAC-listed vessels. Use it for a quick list check of a name; use run_due_dil
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Full name to screen, 2-200 characters: letters, digits, spaces and - ' . , ( ) & (e.g. "Lazarus Group"). Longer, more specific names give fewer partial matches. |
| list | string | no | Search one list group only (default all); mauritius searches the Mauritius registry name index |
| limit | integer | no | Maximum hits to return, 1-25 (default 10). When the limit is reached the result has truncated=true. |
Check a blockchain address (any chain) against active sanctioned and frozen addresses: OFAC SDN, OpenSanctions, UK, Circle USDC and Tether USDT freeze lists, and Ransomwhere ransomware wallets. Use it before sending or accepting funds; owner_name also screens the owner's name and returns a composite risk (critical when the address is listed, elevated when only the name matched). For names alone us
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | Full wallet address, 10-128 characters of letters, digits, ':', '_' or '-' (e.g. 0x08723392Ed15743cc38513C4925f5e6be5c17243) |
| owner_name | string | no | Optional name of the wallet's owner to screen in the same call (switches to the combined wallet + name check) |
Look up one country's anti-money-laundering risk: FATF status (black/grey list), Basel AML Index, Corruption Perceptions Index, EU and US high-risk designations, tax-haven flag, and a derived risk level (critical, high, medium, low or standard). Use it to assess a counterparty's country or a payment corridor; it takes one country code per call, so check each end of a corridor separately. For a nam
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country_code | string | yes | ISO 3166-1 alpha-2 country code, e.g. MU (Mauritius), KP (North Korea), AE (United Arab Emirates) |
Search Mauritius-specific records by name: Financial Services Commission licensees (category fsc_licensee), licensed banks, insurers, payment and other financial institutions (licensed_entity), offshore entities from the ICIJ leak databases (offshore_entity), local politically exposed persons (pep) and adverse-media mentions (adverse_media); omit category to search all. Use it for Mauritius counte
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Company or person name, 2-200 characters (e.g. "Absa Bank") |
| category | string | no | Optional record type filter |
| limit | integer | no | Maximum records, 1-25 (default 10) |
Profile one person or company in a single call: global watchlist screening, AML risk of every country found in the hits, Mauritius registry records (with their FSC-licensing and PEP-role links), and a composite 0-100 risk score with its factors. Use it for onboarding (KYC/KYB) or enhanced due diligence; use screen_entity when a list check is enough and screen_cross_border_payment for both parties
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Person or company name, 2-200 characters |
| include_forex | boolean | no | Include Bank of Mauritius exchange rates for context when countries are detected (default true) |
Screen both parties of a payment before it is sent: sender and receiver names against global watchlists, their countries' AML risk, and an optional Bank of Mauritius exchange rate for the corridor (set currency_from; currency_to defaults to MUR). Returns PROCEED (risk score below 15), REVIEW (15-39, minor indicators such as partial name matches), FLAG (40-74, enhanced due diligence) or BLOCK (75+,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sender_name | string | yes | Sender (originator) name, 2-200 characters |
| sender_country | string | no | Optional sender ISO 3166-1 alpha-2 country code, e.g. GB |
| receiver_name | string | yes | Receiver (beneficiary) name, 2-200 characters |
| receiver_country | string | no | Optional receiver ISO 3166-1 alpha-2 country code, e.g. MU |
| currency_from | string | no | Optional source currency, ISO 4217 (e.g. USD); adds the MUR corridor rate |
| currency_to | string | no | Optional target currency, ISO 4217 (default MUR) |
Screen the originator and beneficiary of a crypto transfer (wallets, plus names and countries when given) and store the result as a Travel Rule packet. The strictest threshold among the parties' countries applies (EU/EEA 0, Japan about 700, otherwise the FATF Recommendation 16 de-minimis of 1,000 USD); pass amount_usd to learn whether it applies. Returns a packetId, a free verification URL and an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| originator_address | string | yes | Originator wallet address, 10-256 letters, digits or ':' |
| beneficiary_address | string | yes | Beneficiary wallet address, 10-256 letters, digits or ':' |
| originator_name | string | no | Optional originator name; screened against watchlists and stored only as a keyed hash |
| beneficiary_name | string | no | Optional beneficiary name; screened and stored only as a keyed hash |
| originator_country | string | no | Optional originator ISO 3166-1 alpha-2 country; sets the applicable threshold (e.g. US, SG, JP) |
| beneficiary_country | string | no | Optional beneficiary ISO 3166-1 alpha-2 country |
| amount_usd | number | no | Optional transfer value in USD; without it travelRule.applies is null |
| purpose | string | no | Optional purpose of the transfer, up to 200 characters |
Verify a Travel Rule packet you received from a counterparty: returns its stored risk level, recommendation, flags, threshold result and masked wallet addresses. Pass the packet_id you received and, optionally, the originator and beneficiary names and wallet addresses you hold; each is compared with what was screened and reported only as match true/false, so names are never revealed. Use it on the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| packet_id | string | yes | Packet id from the originator, TR- followed by 22 URL-safe characters |
| originator_name | string | no | Optional originator name you hold; checked against the stored keyed hash |
| beneficiary_name | string | no | Optional beneficiary name you hold |
| originator_address | string | no | Optional originator wallet address you hold |
| beneficiary_address | string | no | Optional beneficiary wallet address you hold |
Start 30 days of watchlist monitoring for one wallet address (type wallet) or one person/company name (type entity): it is screened now, re-screened every 6 hours against the latest lists, and an optional HMAC-signed webhook (a public HTTPS URL) is called whenever its status changes between clear, review and alerted. Use it for ongoing monitoring after onboarding; use screen_entity or screen_walle
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | What to monitor |
| value | string | yes | The wallet address (type wallet) or person/company name (type entity), 2-256 characters |
| webhook_url | string | no | Optional public https:// URL that receives a signed POST when the status changes |
| label | string | no | Optional reference of yours, up to 100 characters, echoed in results and webhooks |
| chain | string | no | Optional chain hint for wallets, e.g. ethereum, base, tron (informational) |
Read the status of watchlist monitors created with create_watchlist_monitor. With exactly one id, the target is re-screened against the latest lists right now (and its webhook fires if the status changed); with 2-20 ids, the stored statuses from the last 6-hourly re-screen are returned without re-screening. Use one id when you need a fresh answer before acting and several ids for a periodic sweep;
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monitor_ids | array | yes | 1-20 monitor ids (MON- followed by 22 URL-safe characters). One id = live re-screen; 2-20 ids = stored statuses. |
Permanently stop a watchlist monitor: re-screening ends, its webhook URL is deleted and later checks report status cancelled. It cannot be resumed; create a new monitor with create_watchlist_monitor instead. Use it when monitoring is no longer needed or the webhook endpoint is retired; to read a monitor's status use check_watchlist_monitors. Pass the MON- id returned when the monitor was created:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| monitor_id | string | yes | Monitor id to cancel, MON- followed by 22 URL-safe characters |
Run a Know-Your-Agent check on an AI agent's EVM wallet: ERC-8004 agent-registry lookup and operator, sanctions screening (result clear or sanctioned), on-chain behaviour (wallet age, activity, fund-flow taint, mixer and scam contacts, threat-intel alerts), a 0-100 risk score with its band (minimal, low, moderate, elevated, high or critical), and a signed W3C Verifiable Credential plus a sanctions
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM wallet address: 0x followed by 40 hex characters |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SENTINEL Compliance Intelligence or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish SENTINEL Compliance Intelligence can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.