mcp-registry/com.entangleit/agentpay · v0.3.1
As of 2026-10-23 01:36 UTC, the Entangleit Agentpay MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Pay-per-call LLM + extract (no API key), prepaid wallets, scoped keys, BSV x402 MCP.
Claude Code
claude mcp add --transport http entangleit-agentpay-mcp-server https://entangleit.com/api/agentpay/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"entangleit-agentpay-mcp-server": {
"type": "http",
"url": "https://entangleit.com/api/agentpay/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
27 of 27 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 →
19 parameter(s) across 11 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 →
9 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 →
Handshake + tools/list takes ~1,664 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: 3 tool(s) removed and 2 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. How to fix →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 11 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.entangleit%2Fagentpay/fixes
{
"name": "chat",
"description": "Pay-per-call LLM, no API key. Sends messages to Fuse chat completions; agentpay settles the standard x402 v2 BSV 402 from this wallet and returns the completion plus receiptUrl and txid. Models: fuse-fast (500 sats) or fuse-smart (2500 sats). Wallet limits, scoped keys, and trial budgets apply. Pass dryRun to quote without spending.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"messages"
],
"properties": {
"key": {
"type": "string",
"description": "Agent key (agp_…). Optional when the MCP connection sends Authorization: Bearer."
},
"ref": {
"type": "string"
},
"model": {
"enum": [
"fuse-fast",
"fuse-smart"
],
"type": "string",
"description": "Fuse model (default fuse-fast). fuse-fast = 500 sats, fuse-smart = 2500 sats."
},
"dryRun": {
"type": "boolean",
"description": "Quote + policy check only, no debit or settlement"
},
"messages": {
"type": "array",
"items": {
"type": "object",
"required": [
"role",
"content"
],
"properties": {
"role": {
"enum": [
"system",
"user",
"assistant"
],
"type": "string"
},
"content": {
"type": "string",
"minLength": 1
}
}
},
"minItems": 1,
"description": "OpenAI-style chat messages"
},
"approvalId": {
"type": "string",
"description": "Approval id from a prior approval_required response"
},
"max_tokens": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1
},
"amountCents": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1,
"description": "Override the USD cents charged (min 1 cent default)"
},
"description": {
"type": "string",
"maxLength": 200
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Pay-per-call LLM"
}{
"name": "create_topup_link",
"description": "Create a Stripe Checkout URL that a human opens to fund the wallet. Amount between 100 and 100000 cents USD.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"amountCents"
],
"properties": {
"key": {
"type": "string",
"description": "Agent key (agp_…). Optional when the MCP connection sends Authorization: Bearer."
},
"amountCents": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991,
"description": "Top-up amount in USD cents, e.g. 2000 = $20"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create top-up link"
}{
"name": "create_upgrade_link",
"description": "Create a Stripe Checkout URL to upgrade the wallet to agentpay Pro (more agent keys, higher daily limits, CSV export). Hand the URL to the human who owns the wallet.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"key": {
"type": "string",
"description": "Agent key (agp_…). Optional when the MCP connection sends Authorization: Bearer."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create upgrade link"
}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.entangleit/agentpay"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.entangleit/agentpay"}) over MCP.
extract ~847 tokenspay_service ~456 tokenschat ~418 tokensmint_subagent ~396 tokenssend ~342 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fcom.entangleit%2Fagentpay?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.entangleit%2Fagentpay?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.entangleit%2Fagentpay.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.entangleit%2Fagentpay.svg :target: https://glimind.com/server/mcp-registry%2Fcom.entangleit%2Fagentpay?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1a64dea5ae716fc4…, first seen 2026-10-20, included at leaf 35024 of 49,278. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable finance servers · most reliable payments servers · most reliable security servers · most reliable devops servers
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.
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"
}
}
}
As of 2026-10-23 01:36 UTC, the Entangleit Agentpay MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Entangleit Agentpay MCP server advertises 27 tools, including chat, claim_bounty, claim_trial, create_topup_link, create_upgrade_link.
Point your MCP client at this streamable-http endpoint: https://entangleit.com/api/agentpay/mcp
Glimind scanned all 27 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.
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.