mcp-registry/io.github.mifactory-bot/mifactory-payments · v1.0.0
As of 2026-10-26 17:14 UTC, the Mifactory Bot Mifactory Payments 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.
Stripe payments for AI agents. Create links, verify, manage customers.
Point your MCP client at this streamable-http endpoint: https://mifactory-payments.vercel.app/mcp
4 of 4 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 →
3 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 →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. 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. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mifactory-bot%2Fmifactory-payments/fixes
{
"name": "create_customer",
"description": "Crea un cliente en Stripe. Cuesta 5 créditos.",
"inputSchema": {
"type": "object",
"required": [
"stripe_key",
"email"
],
"properties": {
"name": {
"type": "string",
"description": "Nombre del cliente"
},
"email": {
"type": "string",
"description": "Email del cliente"
},
"metadata": {
"type": "object",
"description": "Metadata adicional"
},
"stripe_key": {
"type": "string",
"description": "Tu Stripe secret key"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_payment_link",
"description": "Crea un link de pago de Stripe. Cuesta 10 créditos.",
"inputSchema": {
"type": "object",
"required": [
"stripe_key",
"amount",
"description"
],
"properties": {
"amount": {
"type": "number",
"description": "Monto en USD (ej: 19.99)"
},
"currency": {
"type": "string",
"description": "Moneda (default: usd)"
},
"cancel_url": {
"type": "string",
"description": "URL de redirección al cancelar"
},
"stripe_key": {
"type": "string",
"description": "Tu Stripe secret key (sk_live_... o sk_test_...)"
},
"description": {
"type": "string",
"description": "Nombre del producto o servicio"
},
"success_url": {
"type": "string",
"description": "URL de redirección al pagar"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "list_payments",
"description": "Lista los pagos recientes de tu cuenta Stripe. Cuesta 3 créditos.",
"inputSchema": {
"type": "object",
"required": [
"stripe_key"
],
"properties": {
"limit": {
"type": "number",
"description": "Número de pagos a listar (default: 10)"
},
"stripe_key": {
"type": "string",
"description": "Tu Stripe secret key"
}
}
},
"annotations": {
"readOnlyHint": true
}
}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.mifactory-bot/mifactory-payments"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.mifactory-bot/mifactory-payments"}) over MCP.
create_payment_link ~183 tokenscreate_customer ~117 tokensverify_payment ~93 tokenslist_payments ~92 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%2Fio.github.mifactory-bot%2Fmifactory-payments?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mifactory-bot%2Fmifactory-payments?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mifactory-bot%2Fmifactory-payments.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mifactory-bot%2Fmifactory-payments.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.mifactory-bot%2Fmifactory-payments?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:e63dc37194ac84dc…, first seen 2026-10-17, included at leaf 12088 of 74,352. Version history · verify what your client received.
Compare: most reliable payments 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-26 17:14 UTC, the Mifactory Bot Mifactory Payments 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.
Mifactory Bot Mifactory Payments MCP server advertises 4 tools, including create_customer, create_payment_link, list_payments, verify_payment.
Point your MCP client at this streamable-http endpoint: https://mifactory-payments.vercel.app/mcp
Glimind scanned all 4 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.