Is the Ai Agents Make Money Here MCP server down?

mcp-registry/com.ai-agents-make-money-here/mcp · v1.0.0

healthy
Last checked 2026-10-26 17:16 UTC · handshake 352ms

As of 2026-10-26 17:16 UTC, the Ai Agents Make Money Here MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
4,926
outages (90d)
0
tools
6

Earn 1 USDC on the internet: pay 10 USDC on Base, get 1 USDC back plus a signed receipt of earnings.

Point your MCP client at this streamable-http endpoint: https://ai-agents-make-money-here.com/mcp

Agent-readiness: C (72/100)

C (72/100): 0 error(s), 3 warning(s) across 6 tool(s); ~729 tokens of tool definitions.
Scores higher than 7% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~729 tokens per session — lighter than 85% of servers.
70 → 72 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions55
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

6 of 6 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: attach_payment_tx, create_claim, get_claim, get_ledger, get_offer and 1 more

3 parameter(s) across 3 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. How to fix →

Tools: attach_payment_tx, get_claim, get_receipt

2 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: attach_payment_tx, create_claim

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: 6 corrected tool definitions

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.ai-agents-make-money-here%2Fmcp/fixes

attach_payment_tx 1 change
{
  "name": "attach_payment_tx",
  "description": "Use when the automatic match did not happen. The transfer must have come from the claim's payout address or carry the claim's exact amount; otherwise it is rejected to prevent anyone claiming someone else's payment.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "claim_id",
      "tx_hash"
    ],
    "properties": {
      "tx_hash": {
        "type": "string",
        "description": "32-byte 0x transaction hash on Base"
      },
      "claim_id": {
        "type": "string",
        "pattern": "^clm_[0-9a-f]{16}$"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Attach the hash of a payment you already sent"
}
create_claim 1 change
{
  "name": "create_claim",
  "description": "Creates a claim for the 0x address on Base where you want the 1 USDC sent. Returns the claim_id, the pay-to address, and the exact USDC amount (about 10) that identifies your claim so it can be paid from any wallet.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "payout_address"
    ],
    "properties": {
      "email": {
        "type": "string",
        "format": "email",
        "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
        "description": "Receipt is also emailed here"
      },
      "tx_hash": {
        "type": "string",
        "description": "If you already paid: the transaction hash of your USDC transfer"
      },
      "agent_name": {
        "type": "string",
        "maxLength": 80,
        "description": "Shown on the public ledger"
      },
      "payout_address": {
        "type": "string",
        "description": "Your 0x address on Base"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Register a payout address and get an exact amount to send"
}
get_claim 1 change
{
  "name": "get_claim",
  "description": "Returns status (awaiting_payment, paid, paying, completed, failed, expired), payment and payout transactions, and the next step.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "claim_id"
    ],
    "properties": {
      "claim_id": {
        "type": "string",
        "pattern": "^clm_[0-9a-f]{16}$"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Check a claim's status"
}

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.ai-agents-make-money-here/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.ai-agents-make-money-here/mcp"}) 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%2Fcom.ai-agents-make-money-here%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.ai-agents-make-money-here%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.ai-agents-make-money-here%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ai-agents-make-money-here%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ai-agents-make-money-here%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.ai-agents-make-money-here%2Fmcp?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:0b777dbf7f03d32d…, first seen 2026-10-17, included at leaf 9661 of 74,362. Version history · verify what your client received.

Tools (6)

Compare: most reliable finance servers · most reliable security 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 Ai Agents Make Money Here MCP server down right now?

As of 2026-10-26 17:16 UTC, the Ai Agents Make Money Here MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Ai Agents Make Money Here MCP server provide?

Ai Agents Make Money Here MCP server advertises 6 tools, including attach_payment_tx, create_claim, get_claim, get_ledger, get_offer.

How do I install Ai Agents Make Money Here MCP server?

Point your MCP client at this streamable-http endpoint: https://ai-agents-make-money-here.com/mcp

Is the Ai Agents Make Money Here MCP server safe to connect to an AI agent?

Glimind scanned all 6 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 Ai Agents Make Money Here 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