com.oceanalt/aml
REMOTE · OCEANALT.COM · 2 COMPONENTS
Pre-payment checks for AI agents: sanctions and AML screening of payees, payment pages and requests.
Available components
Last scanned (18 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3267 tokens (~251/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
- Structured output schemas are declared (31% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.97 functional
- 3 Nov 26 0
- Tool “payment_decision” rewrote its description, which is the text the model reads security
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 26 Oct 26 0
- Tool “screen_address” rewrote its description, which is the text the model reads security
- “screen_address” reworded the description of “address” cosmetic
- “payment_decision” reworded the description of “to” cosmetic
- 22 Oct 26 0
- Server version: 0.7.5 → 0.7.6 functional
- 20 Oct 26 +10
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- First check of Schema quality: 100 functional
- New prompt “check_before_paying” functional
- Server version: 0.7.2 → 0.7.5 functional
- “payment_decision” reworded the description of “network” cosmetic
- “payment_decision” reworded the description of “to” cosmetic
- “screen_address” reworded the description of “address” cosmetic
- “screen_address” reworded the description of “network” cosmetic
- 19 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 18 Oct 26 −1
- Schema quality: 2611 → 3019 ▼ functional
- Tool coverage: 25% → 31% ▲ functional
- New tool “check_payment_request” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://oceanalt.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oceanalt.com | CN=YE2,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 599122729147741ab6bd6af890eef4f267b |
| SANs: oceanalt.com, www.oceanalt.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of oceanalt.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| oceanalt.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://static.sumsub.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://api.sumsub.com https://in.sumsub.com https://static.sumsub.com wss://api.sumsub.com wss://in.sumsub.com; media-src 'self' blob: https://api.sumsub.com https://in.sumsub.com; worker-src 'self' blob:; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com https://player.bilibili.com https://player.vimeo.com https://api.sumsub.com https://in.sumsub.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(self "https://api.sumsub.com" "https://in.sumsub.com"), camera=(self "https://api.sumsub.com" "https://in.sumsub.com") |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oceanalt.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://oceanalt.com/api/mcp | HTTPS enforced | 301 | https://oceanalt.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attest_control_baseline File your own control-baseline attestation (free) ~300
File your operator's control-baseline attestation — the counterpart to counterparty_control_baseline. That tool asks what controls the OTHER side runs; this one publishes what YOUR side runs, so payers can see it before settling with you. No account, no key, one call. Gaps are allowed and expected: answer false where a control is not in place and describe how you plan to close it in gapPlan. A filing with declared gaps is worth far more than no filing — it lets a payer decide against a known shape instead of a blank. Get the control ids from the baseline list first. Only file for a party you are actually authorised to speak for.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Optional. If this party already has an agent registered with OceanAlt, link the attestation to it. |
| answers | object | yes | Map of control id to boolean, e.g. {"ACB-1.1": true, "ACB-2.1": false}. Control ids come from the baseline list (see baseline_controls). |
| contact | string | – | Optional contact for follow-up. Not published. |
| entity | string | yes | The accountable party's legal or commonly-used name, e.g. "Acme Robotics Ltd". This is who the attestation is about — not your agent's name. |
| gapPlan | string | – | For controls answered false: how and when you plan to close them. Plain text. |
No output schema declared.
No examples provided.
baseline_controls List the control-baseline questions (free) ~71
Fetch the OceanAlt Agent Control Baseline: the list of controls an agent operator is expected to run before it is allowed to move money, each answerable yes or no. Call this before attest_control_baseline so you file against real control ids. Each control carries which gate enforces it and why it exists.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_calldata_intent Decode calldata and compare with declared intent (free) ~328
Anti blind-signing. EVM: decodes what a transaction's calldata will actually do (ERC-20 transfer/approve/permit, setApprovalForAll, ownership transfer, native transfer). Solana: decodes a whole base64 transaction (SPL Token / Token-2022 Transfer, TransferChecked, Approve, SetAuthority, CloseAccount, Burn; System Transfer / Assign; ATA creation). Compares it with what you believe you are doing. EVM: pass intent:{action:'pay', to, amount} plus contract (the transaction's to) and data (hex calldata). Solana: pass network:'solana' and transaction (base64) instead of data. decision match = does what you declared; mismatch = different recipient/amount/asset, or an approval / authority change instead of a payment — do not sign; unknown = could not decode (including address-lookup-table accounts), which is not the same as safe.
| Name | Type | Req | Description |
|---|---|---|---|
| contract | string | – | EVM only: the transaction's `to` field (token contract for ERC-20 payments, or the recipient for native transfers). |
| data | string | – | EVM only: 0x-prefixed hex calldata. |
| intent | object | – | – |
| network | string | – | 'solana' to decode a Solana transaction; EVM chain name or CAIP-2 id otherwise (optional). |
| transaction | string | – | Solana only: base64-serialized transaction or message. |
| value | string | – | EVM only: native value in wei (optional). |
No output schema declared.
No examples provided.
check_payment_request Check an email, invoice or message that asks you to pay (free) ~408
Call this before paying because an email, invoice or chat message asked you to. Pass what you received: raw headers if you have them, the From line, subject and body (or body_html), and the payee address if you already extracted one. OceanAlt checks whether the sender is who it claims to be (SPF/DKIM/DMARC results, a display name that names another domain, Reply-To sent elsewhere), whether the sender domain or any link imitates a brand or is a known phishing host, whether the payee address is listed or differs from previous_pay_to, and whether the text pressures the reader, announces changed payment details, or carries instructions aimed at an AI. Returns allow | review | decline with findings. On decline, do not pay from this message; confirm through a channel you already trust. The text is processed in memory and not stored. Free, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Plain-text body, invoice text or chat message |
| body_html | string | – | HTML body, if available (lets OceanAlt compare link text with where links really go) |
| expected_sender_domain | string | – | The domain this requester normally sends from, if you know it |
| from | string | – | The From line, e.g. "Acme Billing" <billing@acme.com> |
| headers | string | – | Raw email headers, if available (needed to check SPF/DKIM/DMARC) |
| lang | string | – | Language for human-readable fields. Defaults to English. |
| network | string | – | Network of pay_to, e.g. base, ethereum, tron, solana |
| pay_to | string | – | The payee address the message asks you to pay, if you already extracted it |
| previous_pay_to | string | – | The address you paid this requester last time, if any |
| reply_to | string | – | The Reply-To line, if any |
| subject | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | – | – |
| findings | array | – | – |
| reason_code | string | – | – |
| signal_keys | array | – | – |
No examples provided.
counterparty_control_baseline Check a counterparty's control baseline before paying (free) ~159
Answers a different question from address screening. Screening asks whether an address is risky; this asks how much damage the agent on the other side could do if it were talked into something. Returns that party's self-attestation against the OceanAlt Agent Control Baseline, split into two sets that must NOT be conflated: verified_by_oceanalt (enforced by the gateway on every payment — provable) and self_claimed (what they state about their own side — NOT verified by OceanAlt). Most parties have not attested: found:false means no information, not a bad signal.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Their agent id, if you have that instead. |
| entity | string | – | The counterparty's entity name. |
No output schema declared.
No examples provided.
evidence_bundle Signed evidence bundle for an address (free) ~105
Everything OceanAlt holds about an address as public facts, in one Ed25519-signed bundle you can verify offline: screening verdict with evidence and freshness, profile signals, one-hop relations to listed addresses, fulfillment receipt stats and coverage. A witness, not a prosecutor: no conclusions about people. Same as GET https://oceanalt.com/api/evidence/bundle.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| network | string | – | EVM chain name (optional, default ethereum). |
No output schema declared.
No examples provided.
payee_decide Payee-side decision: accept this payment? (free) ~160
The receiving side's check before settlement. Given the payee's registry id (sid) and, optionally, the payer, amount and purpose, returns accept / decline / hold_request_info / not_ready with reason codes, the fields to request, evidence and a signature. Rule-based, not a model's opinion. Same logic as POST https://oceanalt.com/api/payee/decide.
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsdc | number | – | Amount in USDC (optional). |
| network | string | – | Chain of the payment (optional). |
| payee | string | yes | The payee's registry id (sid). |
| payer | object | – | Who is paying (optional). |
| purpose | string | – | What the payment is for (optional). |
No output schema declared.
No examples provided.
payment_decision Call before every payment: allow, review or decline (free, no API key) ~547
Call before sending funds, buying a service, settling an invoice or answering an x402 payment quote. Pass the payee address (to) and network to get allow | review | decline, evidence and retry semantics. Only an explicit allow passes this risk check; review, decline, missing or unknown decisions and errors are not permission to pay. This tool does not transfer funds or grant payment authorization. A signed receipt or attestation records the decision, including review; a valid signature does not turn review into approval or prove settlement. If a receipt is returned, its Ed25519 signature can be verified with the public key at https://oceanalt.com/.well-known/oceanalt-keys.json. Pass resource_url to check the origin's payment quote against the payee; a different payee or an unavailable check raises the decision to review. A match is not an endorsement of the seller. Free within the monthly allowance; no signup or key is required to start. Anonymous allowance exhaustion is an error, not a risk decision.
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsdc | number | – | Amount in USDC (optional; recorded, not required for the decision). |
| lang | string | – | Language for human-readable fields (signals, note, advice). Defaults to English. |
| maxAmountUsdc | number | – | Optional declared per-payment cap in USDC. amountUsdc above it → decline. |
| network | string | – | EVM chain, only for a 0x address. Leave it out for Tron, Solana, Bitcoin and XRP Ledger addresses: the chain is detected from the address. |
| purpose | string | – | Short purpose/memo (optional). |
| reasoning | string | – | Optional payment intent: why this payee. Instruction-override phrases here route the payment to review. |
| resource_url | string | – | Optional: the http(s) URL of the paid resource, i.e. the URL that returned the 402 payment quote. OceanAlt asks that origin for its own quote and checks whether it names this payee (origin binding). |
| task | string | – | Optional payment intent: what this payment is for. Sending task, reasoning or maxAmountUsdc opts into a deterministic intent check; an empty intent is itself a finding (requires_information). |
| to | string | yes | Payee address the agent is about to pay: 0x (EVM), T… (TRON), Solana, Bitcoin or r… (XRP Ledger); list matching only: Monero (4…/8…), Bitcoin Cash (q…/p…, optional bitcoincash: prefix), Litecoin (ltc… |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_networks | array | – | – |
| address | string | – | – |
| allow | boolean | – | if (!allow) do not pay. |
| blocked | boolean | – | – |
| cached | boolean | – | – |
| code | string | – | Input error code, e.g. unknown_network, network_address_mismatch, unparsable_url. |
| decision | string | – | – |
| detail_level | string | – | – |
| detail_note | string | – | – |
| error | string | – | Present only on an input error (isError: true). |
| evaluated_at | string | – | – |
| evidence | array | – | – |
| evidence_as_of | object | – | – |
| evidence_oldest | string|null | – | – |
| evidence_qualification | object | – | – |
| intelligence | object | – | – |
| intent_check | object | – | – |
| lang | string | – | – |
| note | string | – | – |
| origin_binding | object | – | – |
| payee_fulfillment | object | – | – |
| reason_code | string | – | Stable reason code; table at https://oceanalt.com/api/contract. |
| receipt | object | – | Ed25519-signed decision receipt: { signed, signature_ed25519, note }. Verify with https://oceanalt.com/.well-known/oceanalt-keys.json. |
| requires_information | object | – | – |
| retry | string | – | – |
| retry_hint | string | – | – |
| risk | number|null | – | Rounded to 10 when detail_level is coarse. |
| risk_band | string|null | – | – |
| screened_network | string | – | – |
| screening_scope | object | – | Present only for list-only chains: coverage is list_only, no on-chain analysis is performed. |
| settlement | object | – | – |
| signal_class | string | – | – |
| signal_keys | array | – | Language-independent keys. Branch on these. Full list at https://oceanalt.com/api/contract. |
| signals | array | – | Human-readable. Do not branch on these. |
| standard | string | – | – |
| verdict | string | – | clear means no match in the data held, not that it is safe. uncertain must never be treated as clear. |
No examples provided.
recent_flagged List recently flagged addresses (free) ~55
Return a representative sample of addresses on OceanAlt's reviewed risk list — OFAC-sanctioned, known mixers, and scam/phishing — each with its source category and reason. Takes no arguments. Free, no API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_agent_identity Resolve an agent's chain of accountability (free) ~109
Resolves who stands behind a paying agent: agent -> principal -> mandate -> credential -> wallet. Each link reports whether it holds; completeness counts how many do (a factual count, not a score). Wherever the chain breaks is where accountability stops. Publication is opt-in and only posture is exposed (that a ceiling exists, never its value), so found:false means the agent has not published — absence of information, not a bad signal.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | The agent id to resolve. |
No output schema declared.
No examples provided.
screen_address Screen a payee address for AML risk (free) ~344
Run an AML compliance screen on a single blockchain address BEFORE paying or receiving from it — the pre-payment check on a counterparty. Checks OFAC sanctions, known mixers, scam and phishing lists, stablecoin issuer freezes, and on-chain heuristics. Returns a verdict (clear | caution | risky), a 0–100 risk score, a blocked flag, and the matching signals — receipts, not a black-box score. A clear verdict means nothing was found in the data OceanAlt holds; it is not a statement that the address is safe. Depth varies by chain (see coverage.chains at /.well-known/agent-capabilities). Supports EVM (0x…), Tron (T…), Solana, Bitcoin and XRP Ledger (r…); Monero, Bitcoin Cash, Litecoin (ltc1) and BNB Beacon (bnb1) by list matching only. Free, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address to screen. EVM: 0x + 40 hex. Tron: T + 33 base58. Solana: base58 public key. Bitcoin: bc1… / 1… / 3…. XRP Ledger: r…. List matching only: Monero (4…/8…, 95 chars), Bitcoin Cash (q…/p…, option… |
| lang | string | – | Language for human-readable fields (signals, note, advice). Defaults to English. |
| network | string | – | EVM chain (optional; auto-defaults to ethereum; ignored for Tron, Solana, Bitcoin and XRP Ledger). |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_networks | array | – | – |
| blocked | boolean | – | – |
| cached | boolean | – | – |
| code | string | – | Input error code, e.g. unknown_network, network_address_mismatch, unparsable_url. |
| detail_level | string | – | – |
| detail_note | string | – | – |
| error | string | – | Present only on an input error (isError: true). |
| evaluated_at | string | – | – |
| evidence | array | – | – |
| evidence_as_of | object | – | – |
| evidence_oldest | string|null | – | – |
| evidence_qualification | object | – | – |
| note | string | – | – |
| provider | string | – | – |
| reason_code | string | – | Stable reason code; table at https://oceanalt.com/api/contract. |
| requires_information | object | – | – |
| retry | string | – | – |
| retry_hint | string | – | – |
| risk | number|null | – | Rounded to 10 when detail_level is coarse. |
| risk_band | string|null | – | – |
| screened_network | string | – | The chain actually screened: tron, solana, bitcoin and xrpl follow the address format; an 0x address uses network, or ethereum when none was given. List-only chains (monero, bitcoin-cash, litecoin, b… |
| screening_scope | object | – | Present only for list-only chains: coverage is list_only, no on-chain analysis is performed. |
| signal_class | string | – | – |
| signal_keys | array | – | Language-independent keys. Branch on these. Full list at https://oceanalt.com/api/contract. |
| signals | array | – | Human-readable. Do not branch on these. |
| verdict | string | – | clear means no match in the data held, not that it is safe. uncertain must never be treated as clear. |
No examples provided.
screen_endpoint Screen a payment endpoint for phishing (free) ~209
Screen a payment ENDPOINT (URL or domain) before calling it — the half that address screening cannot answer. In x402 the agent discovers a URL first, receives a 402, and only then learns where to pay: if that endpoint is spoofed, the payee address it hands back is freshly generated and appears on no sanctions list. Checks the hostname and its parent domains against phishing-domain intelligence plus hostname shape signals (bare IP, punycode homograph, deep subdomain nesting, free hosting). Returns clear | caution | risky | unknown with language-independent signal_keys. A clear verdict means no match was found, NOT that the endpoint is safe — freshly registered phishing hosts always precede any list. Use together with screen_address. Free, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language for human-readable fields. Defaults to English. |
| url | string | yes | Full URL or bare domain of the payment endpoint, e.g. https://pay.example.com/x402 or pay.example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted_networks | array | – | – |
| code | string | – | Input error code, e.g. unknown_network, network_address_mismatch, unparsable_url. |
| detail_level | string | – | – |
| detail_note | string | – | – |
| error | string | – | Present only on an input error (isError: true). |
| evidence | array | – | – |
| host | string | – | – |
| imitates | object | – | Present when the host imitates a known brand. |
| input | string | – | – |
| listed_as | object | – | Present when the host or a parent domain is on a phishing list: source, label, firstSeen, lastSeen, delistedAt. |
| note | string | – | – |
| reason_code | string | – | Stable reason code; table at https://oceanalt.com/api/contract. |
| retry | string | – | – |
| retry_hint | string | – | – |
| risk | number|null | – | Rounded to 10 when detail_level is coarse. |
| risk_band | string|null | – | – |
| signal_class | string | – | – |
| signal_keys | array | – | Language-independent keys. Branch on these. Full list at https://oceanalt.com/api/contract. |
| signals | array | – | Human-readable. Do not branch on these. |
| verdict | string | – | clear means no match in the data held, not that it is safe. uncertain must never be treated as clear. |
No examples provided.
verify_payment_requirements Verify a signed x402 402 response (free) ~230
Before paying an x402 402 response, check that its payment requirements (payTo, amount, asset, network, resource) were signed by the seller and not altered in transit by a proxy, CDN, SDK or another tool. x402 v2 carries the requirements in the PAYMENT-REQUIRED response header (base64 JSON): pass either the decoded JSON or the raw base64 value as body. Optionally pass expect:{payTo, amount} — the address and amount you are about to pay — and the tool also checks they match what was signed. verified:false with reason_code no_signature means the seller does not sign (unprotected, not necessarily malicious); digest_mismatch or signature_invalid means the response was tampered with — do not pay.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | yes | The decoded PAYMENT-REQUIRED header JSON (object), or the raw base64 header value (string). |
| expect | object | – | What you are about to pay; checked against the signed fields. |
| keys_url | string | – | Override the seller's public-key URL (defaults to extensions.signedRequirements.keys_url). |
No output schema declared.
No examples provided.
How do I install the com.oceanalt/aml MCP server?
com.oceanalt/aml is a hosted endpoint at https://oceanalt.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · oceanalt.com
claude mcp add --transport http com-oceanalt-aml 'https://oceanalt.com/api/mcp'
What is the com.oceanalt/aml MCP server?
com.oceanalt/aml is an MCP server listed in the public MCP registry as com.oceanalt/aml. Pre-payment checks for AI agents: sanctions and AML screening of payees, payment pages and requests. This page covers its hosted endpoint (https://oceanalt.com/api/mcp).
Is the com.oceanalt/aml MCP server safe to use?
com.oceanalt/aml scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.oceanalt/aml MCP server expose?
com.oceanalt/aml exposes 13 tools: payment_decision, screen_address, screen_endpoint, check_payment_request, counterparty_control_baseline, and 8 more. Their descriptions and schemas cost roughly 3,025 tokens of context every time the server is loaded.
Does the com.oceanalt/aml MCP server require authentication?
No. We connected to com.oceanalt/aml without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.oceanalt/aml MCP server still maintained?
com.oceanalt/aml is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.