Is the Magmite Pay MCP server down?

mcp-registry/dev.magmite/pay · v1.32.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 17:58 UTC · handshake 525ms

As of 2026-11-22 17:58 UTC, the Magmite Pay MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
941
outages (90d)
0
tools
43

Micropayment tools payable per call in USDC over x402. Discovery free, no accounts, no api keys.

Point your MCP client at this streamable-http endpoint: https://pay.magmite.dev/mcp

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 3 warning(s) across 43 tool(s); ~7,561 tokens of tool definitions.
Scores higher than 20% of 27,661 MCP servers Glimind has audited.
Its tool list costs an agent ~7,561 tokens per session — more than 75% of servers.
85 → 78 since 2026-11-16
no tool-poisoning patterns
Descriptions100
Safety hints11
Schemas100
Protocol100
Stability100
Token cost75
Reliability100
Client compatibility70

What to fix (4)

43 of 43 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: aeo-playbook, aeo-scan, agent-full-backup, agent-time, arbitrum-fee-snapshot and 38 more

43 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

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. How to fix →

Tools: mcp-registry-update-kit, mcp-update-kit, pay-test-0-001, pay-test-0-01, pay-test-0-10

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 8 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.magmite%2Fpay/fixes

csv-convert 1 change
{
  "name": "csv-convert",
  "description": "CSV convert. A CSV document in, URL-encoded as the csv query parameter (up to 12,000 bytes), a conversion out: RFC 4180 parsing (quoted fields, escaped quotes, newlines in quotes), delimiter sniffing among comma, semicolon, pipe, and tab, a JSON records array keyed by header, and a rendered Markdown table of the same rows, with every statistic included. Price: $0.10 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.",
  "inputSchema": {
    "type": "object",
    "required": [
      "csv"
    ],
    "properties": {
      "csv": {
        "type": "string",
        "description": "The CSV document to convert (up to 12,000 bytes)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
mcp-registry-update-kit 1 change
{
  "name": "mcp-registry-update-kit",
  "description": "Mcp registry update kit. The complete registry re-publish methodology: the rule that the server moves first, the server.json discipline with the version line the one changed byte, the publisher login, validate, and publish sequence with its proof gates, the honest versions read path, and a field-verification close-out proving the listing in step with the live handshake. One call returns the full kit; the buyer's agent re-publishes its registry listing without breaking discovery. Price: $10.00 pe",
  "inputSchema": {
    "type": "object",
    "properties": {
      "server": {
        "type": "string",
        "description": "Optional description of the MCP server whose registry listing is being re-published, e.g. its name and version; seeds the intake step."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": true
  }
}
mcp-update-kit 1 change
{
  "name": "mcp-update-kit",
  "description": "Mcp update kit. The complete server-update methodology: protocol version negotiation rules, a versioning discipline that never reuses a number, the add-evolve-deprecate-remove ladder with lead times, client caching and refresh behavior for tools and descriptions, the registry and server-card re-publish path, and a zero-regression verification pass with rollback. One call returns the full kit; the buyer's agent updates its own MCP server without breaking clients. Price: $10.00 per call, paid in U",
  "inputSchema": {
    "type": "object",
    "properties": {
      "server": {
        "type": "string",
        "description": "Optional description of the MCP server being updated, e.g. its name and version; seeds the intake step."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": true
  }
}

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/dev.magmite/pay"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.magmite/pay"}) 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fdev.magmite%2Fpay.svg)](https://glimind.com/server/mcp-registry%2Fdev.magmite%2Fpay?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.magmite%2Fpay?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fdev.magmite%2Fpay.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:97e59d7a459fa26d…, first seen 2026-11-19, included at leaf 347422 of 384,795. Version history · verify what your client received.

Tools (43)

Compare: most reliable knowledge servers · most reliable web servers · most reliable files servers · most reliable other servers · most reliable data 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Magmite Pay MCP server down right now?

As of 2026-11-22 17:58 UTC, the Magmite Pay MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Magmite Pay MCP server provide?

Magmite Pay MCP server advertises 43 tools, including aeo-playbook, aeo-scan, agent-full-backup, agent-time, arbitrum-fee-snapshot.

How do I install Magmite Pay MCP server?

Point your MCP client at this streamable-http endpoint: https://pay.magmite.dev/mcp

Is the Magmite Pay MCP server safe to connect to an AI agent?

Glimind scanned all 43 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 Magmite Pay 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.

Feedback
Help us improve