app.payperwork/payperwork

PayperWork

Is the PayperWork MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-02.

Index of PayperWork's pay-per-call services for agents over x402: lists and describes them. Free.

alive probed 2026-11-02 · HTTP 200

2tools

261tokens in Claude Opus 5.5

0.1 %of Claude's 200k window

0.1×the median server

522 msto initialize

35 msto list tools

Endpoint: https://payperwork.app/mcp (streamable-http)
Host: payperwork.app
Protocol: 2025-11-25
Reports itself as: payperwork 0.4.1
Capabilities: tools
Instructions: 1 628 characters
Of a 1M window: <0.1 % of a 1M context window
Count: 261 tokens in Claude Opus 5.5, exact, measured 2026-11-02. With the Claude Code prefix mcp__…__ on each tool name: 279. The o200k_base estimate is 146. Counted again when the tool definitions change. Method.
Website: https://payperwork.app
Registry: active, updated 2026-11-01 · registry entry
Changes: 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.79×.

Tool	≈ Claude tokens	o200k estimate	Share of this server
describe_service	163	91	62 %
list_services	98	55	38 %

These registry entries have the same tool names and the same schema sizes.

We add a row when the result changes. A server with no change keeps its last row.

Probed	Result	Init	Tools	Claude	o200k
2026-11-02 11:15	alive	91 ms	2	261	146
2026-11-01 10:34	alive	522 ms	2	249	137

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.