Is the Agenticpaywall Composer MCP server down?

mcp-registry/com.agenticpaywall/composer · v3.4.2

healthy
Last checked 2026-10-27 02:33 UTC · handshake 206ms

As of 2026-10-27 02:33 UTC, the Agenticpaywall Composer MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 489 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
100%
checks observed
4,954
outages (90d)
489
tools
2

Composes + runs multi-step external-data workflows for one quoted USDC price (x402).

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

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 3 warning(s) across 2 tool(s); ~424 tokens of tool definitions.
Scores higher than 5% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~424 tokens per session — lighter than 95% of servers.
70 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints0
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (3)

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

Tools: plan_workflow, run_workflow

2 of 2 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: plan_workflow, run_workflow

1 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: run_workflow

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%2Fcom.agenticpaywall%2Fcomposer/fixes

run_workflow 1 change
{
  "name": "run_workflow",
  "description": "Run a workflow Composer planned for you and get the synthesized result. PAID\nvia x402 — one payment replaces the multi-step work you'd otherwise do yourself.\n\nPass the `plan_id` from plan_workflow. This call is payment-gated: it returns an\nx402 402 carrying the final live-checked price (normally ≈ plan_workflow's\nindicative quote); your x402 client pays it (settled on Base), and Composer then\nexecutes the multi-step workflow — paying each provider from its own wallet — and\nreturns the synthesize",
  "inputSchema": {
    "type": "object",
    "required": [
      "plan_id"
    ],
    "properties": {
      "plan_id": {
        "type": "string"
      },
      "agent_id": {
        "type": "string",
        "default": ""
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

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.agenticpaywall/composer"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.agenticpaywall/composer"}) 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.agenticpaywall%2Fcomposer.svg)](https://glimind.com/server/mcp-registry%2Fcom.agenticpaywall%2Fcomposer?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.agenticpaywall%2Fcomposer?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.agenticpaywall%2Fcomposer.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.agenticpaywall%2Fcomposer.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.agenticpaywall%2Fcomposer?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:e0643c8bef2fb5c3…, first seen 2026-10-17, included at leaf 10751 of 76,865. Version history · verify what your client received.

Tools (2)

Compare: most reliable productivity 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 Agenticpaywall Composer MCP server down right now?

As of 2026-10-27 02:33 UTC, the Agenticpaywall Composer MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 489 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Agenticpaywall Composer MCP server provide?

Agenticpaywall Composer MCP server advertises 2 tools, including plan_workflow, run_workflow.

How do I install Agenticpaywall Composer MCP server?

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

Is the Agenticpaywall Composer MCP server safe to connect to an AI agent?

Glimind scanned all 2 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 Agenticpaywall Composer 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