Is the Chrisssun18 Bot Oceanalt Aml MCP server down?

mcp-registry/io.github.chrisssun18-bot/oceanalt-aml · v0.7.2

Also listed as glama/oceanalt666/oceanalt-aml, mcp-registry/com.oceanalt/aml · primary listing: mcp-registry/com.oceanalt/aml

healthy
Last checked 2026-10-18 02:00 UTC · handshake 847ms

As of 2026-10-18 02:00 UTC, the Chrisssun18 Bot Oceanalt Aml MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 62 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.1%
checks observed
3,675
outages (90d)
62
tools
12

AML/compliance address screening for AI agent payments — free tools, no API key.

Install Chrisssun18 Bot Oceanalt Aml MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "chrisssun18-bot-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 (84/100)

B (84/100): 0 error(s), 4 warning(s) across 12 tool(s); ~3,271 tokens of tool definitions.
Scores higher than 46% of 15,345 MCP servers Glimind has audited.
Its tool list costs an agent ~3,271 tokens per session — more than 55% of servers.
84 → 84 since 2026-10-17
no tool-poisoning patterns
Schemas86
Descriptions78
Safety hints57
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability72

What to fix (5)

5 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.

Tools: payee_decide, payment_decision, screen_address, screen_endpoint, verify_payment_requirements

2 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.

Tools: check_calldata_intent, evidence_bundle

1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).

Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays.

Tools: verify_payment_requirements

Handshake + tools/list takes ~3,063 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 0 tool(s) removed and 7 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts.

Auto-fix: 1 corrected tool definition

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

verify_payment_requirements 1 change
{
  "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/io.github.chrisssun18-bot/oceanalt-aml"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.chrisssun18-bot/oceanalt-aml"}) over MCP.

Passed

Largest tool definitions

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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.chrisssun18-bot%2Foceanalt-aml.svg)](https://glimind.com/server/mcp-registry%2Fio.github.chrisssun18-bot%2Foceanalt-aml?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.chrisssun18-bot%2Foceanalt-aml?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.chrisssun18-bot%2Foceanalt-aml.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.chrisssun18-bot%2Foceanalt-aml.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.chrisssun18-bot%2Foceanalt-aml?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:b905394875fd3f03…, first seen 2026-10-17, included at leaf 17419 of 19,652. Version history · verify what your client received.

Tools (12)

Compare: most reliable security servers · most reliable knowledge servers · most reliable finance servers · most reliable payments servers · most reliable identity servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Chrisssun18 Bot Oceanalt Aml MCP server down right now?

As of 2026-10-18 02:00 UTC, the Chrisssun18 Bot Oceanalt Aml MCP server is up with a Glimind reliability score of 69/100 (grade C). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 62 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Chrisssun18 Bot Oceanalt Aml MCP server provide?

Chrisssun18 Bot Oceanalt Aml MCP server advertises 12 tools, including attest_control_baseline, baseline_controls, check_calldata_intent, counterparty_control_baseline, evidence_bundle.

How do I install Chrisssun18 Bot Oceanalt Aml MCP server?

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

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

Glimind scanned all 12 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 Chrisssun18 Bot 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.