Ext Ops Panel
Open dashboard
Comparison

com.oceanalt/aml vs Payment Intelligence

com.oceanalt/aml is an MCP server published by oceanalt.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Payment Intelligence is an MCP server published by Raafet57. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecom.oceanalt/amlPayment Intelligence
Official MCP Registry Listed
Version: 0.7.6
Downloads/month (npm): 1 082
Downloads/week (npm): 314
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.3.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.7.6
Downloads/month (npm): 1 082
Downloads/week (npm): 314
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

com.oceanalt/aml vs Payment Intelligence
Factcom.oceanalt/amlPayment Intelligence
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-20 (worse)2026-10-22 (better)
Where it runs (differs)Remote server or your machineOn your machine (payment-intelligence-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/oceanalt666/oceanalt-aml-mcpgithub.com/raafet57/payment-intelligence-plugin
Changes in the last 7 days (differs)95
First seen (differs)2026-10-112026-10-21
Endpoint at the last check (differs)Responded 4 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

com.oceanalt/aml

In its own words, on Official MCP Registry:

Pre-payment checks for AI agents: sanctions and AML screening of payees, payment pages and requests.

Payment Intelligence

In its own words, on Official MCP Registry:

Offline ISO 20022 payment tools: explain and scrub pacs/camt, CBPR+, SSI checks, IBAN and BIC.

How to run each

com.oceanalt/aml As a remote MCP server

Claude Code
claude mcp add --transport http aml https://oceanalt.com/api/mcp

Payment Intelligence As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio payment-intelligence -- npx -y payment-intelligence-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only com.oceanalt/aml has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of Payment Intelligence nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: com.oceanalt/aml · What it can do: Payment Intelligence · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built