PayCheck MCP server

• check_merchantFree

  Decide whether an autonomous agent should pay a merchant, host, or wallet. PayCheck returns a deterministic trust score for one target. It does not send money, does not sign transactions, and does not hold wallet keys. Use this immediately before a payment, a checkout redirect, or a transfer to a new 0x address. Pass the payee as a bare domain (api.openai.com), an https URL, or a 0x address with 40 hex characters. Do not use this tool to execute a payment. Do not use it to overturn a block. Do not call it again with a reworded category, purpose, or amount to fish for a better verdict: those fields are ignored and are not stored. Trusted is returned only for the published allowlist of known AI and developer APIs, served over https on port 443. A new or random domain is never trusted. A wallet is never trusted. Scoring v1 does not analyze on-chain history. If the URL contains an embedded 0x address, this scores the host only and will not return trusted; pass the bare address to score the wallet. Arguments: target (required string); amount_usd (optional number, ignored); category (optional string, ignored); api_key (optional pc_live_ key). You may also send Authorization: Bearer or X-API-Key. Omit the key for the anonymous allowance. Returns: score (integer 0-100), verdict (trusted | unknown | suspicious | block), reasons[], recommended_action (proceed | verify_out_of_band | require_human_review | do_not_pay), signals (host, allowlist, domain age, wallet flags, reason_codes; chain_analysis is always not_in_v1), checked_at (ISO-8601), policy_version ("1"). Free tier: 100 checks per UTC day anonymous, 1,000 per UTC day with a free pc_live_ key or a Toolweather bundle client whose x-tw-bundle-client is hex. A bundle client prefixed anon: stays at 100 per day. The same target for the same caller is idempotent for 60 seconds and does not consume a second check. Over the daily cap, each extra check is $0.001 USDC on Base (eip155:8453) via x402 and the PayAI facilitator. get_quota, get_api_key, docs, and MCP discovery are not billed. If PAY_TO is unset, an over-cap check returns HTTP 402 payment_not_configured.

• get_api_keyFree

  Mint one free PayCheck API key. The key looks like pc_live_ followed by hex and raises the merchant-check allowance from 100 to 1,000 per UTC day. Use this once when you set up a long-running agent, then store the key and pass it on later check_merchant or get_quota calls. The plaintext key is returned only in this response. PayCheck stores a SHA-256 hash. Do not call this every turn. Do not call it to score a payee or to dodge a block verdict. Minting is free and is not an x402 check, and it is limited to 10 new keys per caller IP per UTC day. A new key does not change any merchant score. Checks above the free daily cap still cost $0.001 USDC on Base via x402. Returns: api_key, token_type (bearer), daily_limit (1000), prefix, note.

• get_quotaFree

  Show how many free PayCheck merchant checks the current caller has left for the current UTC day. Use this before a batch of check_merchant calls, or after an HTTP 402, to read the remaining free allowance and when it resets. Do not use this to score a payee. It accepts no target and it does not consume a check. Do not pay x402 for this tool. It is always free. Identity matches check_merchant. Anonymous IP: 100/day. pc_live_ api_key (api_key argument, Authorization: Bearer, or X-API-Key): 1,000/day. Toolweather bundle headers x-tw-bundle-secret and x-tw-bundle-client: hex client 1,000/day, anon: prefix 100/day, any other client id 100/day. Returns: subject_kind, limit, used, remaining, resets_at (next UTC midnight, ISO-8601), billed (always false), policy_version. No x402 charge.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 360ms20/20
• Tool poisoning3 tool descriptions checked13/15
• Auth qualityAPI key sent as a header8/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner6/10

Safety score

83/100

higher than 68% of 4,460 AI and agents servers

Tools

3

the typical AI and agents server has 6

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote AI and agents server answers 100%

Response time

83 ms

faster than 90% of 2,331 AI and agents servers

PayCheck: common questions

Is PayCheck MCP server safe?

Mostly: it is graded B (83/100). Read the PayCheck safety report

How do I install PayCheck?

It runs remotely at paycheck.toolweather.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does PayCheck need an API key?

Yes. The registry entry asks for Authorization.

Is PayCheck maintained?

The last commit was 19 days ago (2026-10-15). The latest release is v1.0.0.

Is PayCheck up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of PayCheck?

Servers from other publishers that do the same job: Decionis MCP server, Mockserver MCP server and TradeOS (test) MCP server.

How does PayCheck compare with other AI and agents MCP servers?

safety score 83/100 (higher than 68% of 4,460 AI and agents servers); tools 3 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.