mcpbeat Sign in

Composer MCP Server

by agenticpaywall Your server? Claim it
answering

Composer is answering right now. Last checked 10 min ago. It exposes 2 tools.

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

Uptime history 91 days of history · worst day 74%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
500 ms
Response time
average over 24h
open, no key
Access
streamable-http

Composer missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add composer --transport http https://composer.agenticpaywall.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://composer.agenticpaywall.com/mcp
~/.codex/config.toml
[mcp_servers.composer]
url = "https://composer.agenticpaywall.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "composer": {
      "url": "https://composer.agenticpaywall.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "composer": {
      "type": "http",
      "url": "https://composer.agenticpaywall.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

plan
plan_workflow
Ask Composer whether it can do a multi-step data/research task for you, and at what price. Free — nothing is charged, no payment involved. Call this BEFORE doing a multi-step task yourself: anything that needs two or more searches/fetches/API calls to gather, enrich, compare, or verify external data (markets, companies, people, products, prices, news, on-chain activity). Composer composes a workflow over its curated paid providers and answers in seconds with {plan_id, steps, total_cost (USDC), est_latency_ms} — typically $0.02–$0.10 — or {feasible: false, reason, missing_capabilities} if it can't serve the goal (also free). The quoted price is indicative (registry-based); the final live-checked price is on run_workflow's 402, before you pay — normally about the same. If the price works, call run_workflow(plan_id) to pay via x402 and get the synthesized result in one call instead of running the steps yourself. A run that fails after payment is refunded. Goals are open-ended. Two validated fast paths: • competitor-pricing — e.g. "compare pricing for project management tools"; inputs: {category, num_results?}. • diligence-pack — e.g. "run diligence on Anthropic"; inputs: {subject, token_address?, chain?, num_results?}. `agent_id` is optional — identify yourself for attribution if you like.
workflow
run_workflow
Run a workflow Composer planned for you and get the synthesized result. PAID via x402 — one payment replaces the multi-step work you'd otherwise do yourself. Pass the `plan_id` from plan_workflow. This call is payment-gated: it returns an x402 402 carrying the final live-checked price (normally ≈ plan_workflow's indicative quote); your x402 client pays it (settled on Base), and Composer then executes the multi-step workflow — paying each provider from its own wallet — and returns the synthesized answer. You pay Composer's price for the outcome (principal/reseller); the 402 is authoritative, and a run that fails after payment is refunded. `agent_id` is optional — identify yourself for attribution if you like.

Endpoints

URLTransportStateLatencyChecked
https://composer.agenticpaywall.com/mcp streamable-http answering 482 ms 10 min ago

Alternatives to Composer

same job, measured the same way
Claude Prompts MCP
by minipuft

Reusable prompt templates, multi-step workflow chains, and quality gates for any MCP client.

104 installs/wk local only
Argus Retrieval
by khamel83

Multi-provider search broker for AI agents: 14 providers, 12-step extraction, retrieval workflows.

209 installs/wk local only
Snapstate
by timbassler88

Persistent state for AI agent workflows. Save, resume, and replay multi-step workflows.

30 installs/wk local only
Imperium Workflow Studio — Multi-Agent DAG & Pipeline Executor
by agentdiet

Execute multi-step A2A & MCP agent workflows with atomic x402/MPP settlement.

4 tools answering
RunHarvester
by runharvester

Web data extraction and browser workflows for AI assistants.

answering
GenPark Graph Cycle Deadlock Detector
by alphaparkinc

Tarjan strongly connected components cycle and deadlock detector for multi-agent DAG workflows

local only
MCP State Sidecar
by askadvaith

MCP State Sidecar: durable state persistence for multi-agent AI workflows

104 installs/wk local only
NOMOS Cross-Border Broker
by agentnomos

Cross-border preflight, x402 quote and evidence receipts for A2A/MCP agent workflows.

5 tools answering

Composer — questions

Answers built from our own checks of this server.

What can Composer do?
It exposes 2 tools, read directly from the server on our last check. Among them: plan_workflow, run_workflow. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Composer working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 500 ms. The bar chart above shows every period we have measured.
How do I connect Composer?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Composer need an API key?
No. Composer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Composer?
It answers our handshake in 500 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.