com.agenticpaywall/composer
REMOTE · COMPOSER.AGENTICPAYWALL.COM · SCANNED SEP 28
Composes + runs multi-step external-data workflows for one quoted USDC price (x402).
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 530 tokens (~265/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.agenticpaywall/composer MCP server?
com.agenticpaywall/composer is a hosted endpoint at https://composer.agenticpaywall.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · composer.agenticpaywall.com
claude mcp add --transport http com-agenticpaywall-composer 'https://composer.agenticpaywall.com/mcp'
{
"mcpServers": {
"com-agenticpaywall-composer": {
"url": "https://composer.agenticpaywall.com/mcp"
}
}
} {
"servers": {
"com-agenticpaywall-composer": {
"type": "http",
"url": "https://composer.agenticpaywall.com/mcp"
}
}
} [mcp_servers.com-agenticpaywall-composer] url = "https://composer.agenticpaywall.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-agenticpaywall-composer": {
"type": "remote",
"url": "https://composer.agenticpaywall.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-agenticpaywall-composer --url 'https://composer.agenticpaywall.com/mcp' --transport streamable-http
mcp_servers:
com-agenticpaywall-composer:
url: "https://composer.agenticpaywall.com/mcp" {
"McpServers": {
"com-agenticpaywall-composer": {
"Transport": "http",
"Url": "https://composer.agenticpaywall.com/mcp"
}
}
} assistant mcp add com-agenticpaywall-composer -t streamable-http -u 'https://composer.agenticpaywall.com/mcp'
{
"mcpServers": {
"com-agenticpaywall-composer": {
"type": "http",
"url": "https://composer.agenticpaywall.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 0
- Stability: pass → 0.97 functional
- 12 Sept 26 0
- Stability: 0.97 → pass security
- 11 Sept 26 0
- Stability: pass → 0.97 functional
- 6 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://composer.agenticpaywall.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agenticpaywall.com | CN=YE2,O=Let's Encrypt,C=US | 7 Aug 2026 | 5 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6ff707df08a72f9c8955b075ed23c04b324 |
| SANs: *.agenticpaywall.com, agenticpaywall.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of composer.agenticpaywall.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agenticpaywall.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://composer.agenticpaywall.com/mcp | Verified | 200 | |
| http (plaintext) | http://composer.agenticpaywall.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
plan_workflow ~343
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| goal | string | yes | – |
| inputs | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
run_workflow ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| plan_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the com.agenticpaywall/composer MCP server?
com.agenticpaywall/composer is an MCP server listed in the public MCP registry as com.agenticpaywall/composer. Composes + runs multi-step external-data workflows for one quoted USDC price (x402). This page covers its hosted endpoint (https://composer.agenticpaywall.com/mcp).
Is the com.agenticpaywall/composer MCP server safe to use?
com.agenticpaywall/composer scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.agenticpaywall/composer MCP server expose?
com.agenticpaywall/composer exposes 2 tools: plan_workflow, run_workflow. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.
Does the com.agenticpaywall/composer MCP server require authentication?
No. We connected to com.agenticpaywall/composer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.agenticpaywall/composer MCP server still maintained?
com.agenticpaywall/composer is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.