Ext Ops Panel
Open dashboard
Comparison

com.oceanalt/aml vs Postman MCP Server

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)). Postman MCP Server is an MCP server published by postman.com. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, npm registry (MCP servers)). As of our marketplace pass on 2026-11-06. 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/amlPostman MCP Server
Official MCP Registry Listed
Version: 0.7.6
Downloads/month (npm): 920
Downloads/week (npm): 149
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.15.0
Downloads/month (npm): 33 131
Downloads/week (npm): 7 080
Forks (GitHub): 85
Stars (GitHub): 325
Not marked · First seen
npm registry (MCP servers) Listed
Version: 0.7.6
Downloads/month (npm): 920
Downloads/week (npm): 149
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.15.0
Downloads/month (npm): 33 131
Downloads/week (npm): 7 080
Forks (GitHub): 85
Stars (GitHub): 325
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:73f715030cbe
Forks (GitHub): 85
Pulls (Docker Hub): 47 118
Stars (Docker Hub): 6
Stars (GitHub): 325
Not marked · First seen

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 Postman MCP Server
Factcom.oceanalt/amlPostman MCP Server
Marketplaces that list it (differs)2 (worse)3 (better)
Stars (GitHub) (differs)0 (worse)325 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub47 118
Forks (GitHub) (differs)0 (worse)85 (better)
Last release (differs)2026-10-20 (worse)2026-10-30 (better)
Where it runsRemote server or your machineRemote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declares (differs)Not published42
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITApache-2.0
Repository (differs)github.com/oceanalt666/oceanalt-aml-mcpgithub.com/postmanlabs/postman-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 5 days ago returned HTTP 405Responded 9 h ago, requires authentication

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.

Postman MCP Server

In its own words, on Official MCP Registry:

Give your AI agents trusted access to the full Postman platform.

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

Postman MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http postman-mcp-server https://mcp.postman.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: POSTMAN_API_KEY (secret), Authorization header

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

Only com.oceanalt/aml has

  • attest_control_baseline
  • baseline_controls
  • check_calldata_intent
  • check_payment_request
  • counterparty_control_baseline
  • evidence_bundle
  • payee_decide
  • payment_decision
  • recent_flagged
  • resolve_agent_identity
  • screen_address
  • screen_endpoint
Show the remaining 1
  • verify_payment_requirements

Only Postman MCP Server has

  • createCollection
  • createCollectionRequest
  • createCollectionResponse
  • createEnvironment
  • createMock
  • createSpec
  • createSpecFile
  • createWorkspace
  • duplicateCollection
  • generateCollection
  • generateSpecFromCollection
  • getAllSpecs
Show the remaining 30
  • getAuthenticatedUser
  • getCollection
  • getCollections
  • getDuplicateCollectionTaskStatus
  • getEnabledTools
  • getEnvironment
  • getEnvironments
  • getGeneratedCollectionSpecs
  • getMock
  • getMocks
  • getSpec
  • getSpecCollections
  • getSpecDefinition
  • getSpecFile
  • getSpecFiles
  • getTaggedEntities
  • getWorkspace
  • getWorkspaces
  • publishMock
  • putCollection
  • putEnvironment
  • runCollection
  • searchPostmanElements
  • syncCollectionWithSpec
  • syncSpecWithCollection
  • updateCollectionRequest
  • updateMock
  • updateSpecFile
  • updateSpecProperties
  • updateWorkspace

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (com.oceanalt/aml as of 2026-10-29). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of com.oceanalt/aml publish no settings it asks for, so we do not compare settings.

What it can do: com.oceanalt/aml · What it can do: Postman MCP Server · 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). Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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