Is the Oceanalt Aml MCP server down?

mcp-registry/com.oceanalt/aml · v0.7.4

Also listed as glama/oceanalt666/oceanalt-aml, mcp-registry/io.github.chrisssun18-bot/oceanalt-aml

As of 2026-10-19 19:23 UTC, the Oceanalt Aml MCP server is up with a Glimind reliability score of 70/100 (grade C). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 8 minutes.

Screen a payee address before an AI agent pays: sanctions, mixers, scam lists, on-chain risk.

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

{
  "mcpServers": {
    "oceanalt-aml-mcp-server": {
      "type": "http",
      "url": "https://oceanalt.com/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (83/100)

What to fix (5)

Auto-fix: 1 corrected tool definition

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.oceanalt%2Faml/fixes

{
  "name": "verify_payment_requirements",
  "description": "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. verif",
  "inputSchema": {
    "type": "object",
    "required": [
      "body"
    ],
    "properties": {
      "body": {
        "description": "The decoded PAYMENT-REQUIRED header JSON (object), or the raw base64 header value (string).",
        "type": "string"
      },
      "expect": {
        "type": "object",
        "properties": {
          "payTo": {
            "type": "string"
          },
          "amount": {
            "type": "string"
          }
        },
        "description": "What you are about to pay; checked against the signed fields."
      },
      "keys_url": {
        "type": "string",
        "description": "Override the seller's public-key URL (defaults to extensions.signedRequirements.keys_url)."
      }
    }
  },
  "annotations": {
    "title": "Verify signed payment requirements (free)",
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true
  },
  "title": "Verify a signed x402 402 response (free)"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.oceanalt/aml"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.oceanalt/aml"}) over MCP.

Passed

• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~3,765 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.20% uptime over 30 days.

Largest tool definitions

• payment_decision ~607 tokens
• check_payment_request ~467 tokens
• check_calldata_intent ~441 tokens
• attest_control_baseline ~377 tokens
• screen_address ~336 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.oceanalt%2Faml.svg)](https://glimind.com/server/mcp-registry%2Fcom.oceanalt%2Faml?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.oceanalt%2Faml?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.oceanalt%2Faml.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.oceanalt%2Faml.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.oceanalt%2Faml?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:5e729b243ba27181…, first seen 2026-10-19, included at leaf 27830 of 28,354. Version history · verify what your client received.

Tools (16)

• attest_control_baseline
• baseline_controls
• batch_screen
• check_calldata_intent
• check_payment_request
• compliance_decision
• counterparty_control_baseline
• deep_trace
• evidence_bundle
• payee_decide
• payment_decision
• recent_flagged
• resolve_agent_identity
• screen_address
• screen_endpoint
• verify_payment_requirements

Compare: most reliable security servers · most reliable other servers · most reliable finance servers · most reliable knowledge servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Oceanalt Aml MCP server down right now?

As of 2026-10-19 19:23 UTC, the Oceanalt Aml MCP server is up with a Glimind reliability score of 70/100 (grade C). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Oceanalt Aml MCP server provide?

Oceanalt Aml MCP server advertises 16 tools, including attest_control_baseline, baseline_controls, batch_screen, check_calldata_intent, check_payment_request.

How do I install Oceanalt Aml MCP server?

Point your MCP client at this streamable-http endpoint: https://oceanalt.com/api/mcp

Is the Oceanalt Aml MCP server safe to connect to an AI agent?

Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Oceanalt Aml MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.