mcpbeat Sign in

PayCheck MCP Server

answering

PayCheck is answering right now. Last checked 7 min ago. It exposes 3 tools. Last commit 16 Oct 2026.

Score merchant domain, https URL, or 0x wallet trust before an agent pays. Does not send payments.

Uptime history 24 hours of history
24 hours agonow
100.0%
Uptime 24h
86 of 86 checks
3
Tools
read from the server
77 ms
Response time
average over 24h
0
Stars
last commit 16 Oct 2026

Nothing serious here today

Today is the operative word: we check PayCheck every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 7 min ago.

run in your terminal
claude mcp add paycheck --transport http https://paycheck.toolweather.workers.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "paycheck": {
      "url": "https://paycheck.toolweather.workers.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.paycheck]
url = "https://paycheck.toolweather.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "paycheck": {
      "url": "https://paycheck.toolweather.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "paycheck": {
      "url": "https://paycheck.toolweather.workers.dev/mcp"
    }
  }
}

Available tools 3

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

api
get_api_key
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.
merchant
check_merchant
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.
quota
get_quota
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.

Endpoints

URLTransportStateLatencyChecked
https://paycheck.toolweather.workers.dev/mcp streamable-http answering 58 ms 7 min ago

Alternatives to PayCheck

same job, measured the same way
Pulsefeed X402
by nikolife2016

Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.

67 installs/wk 11 tools answering
x402 Merchant Check
by gradientdecisions

Pre-payment merchant trust checks for x402 agents on Base and Solana.

1 tools answering
Payment Guard MCP
by mlawsonking

Pre-send risk check for AI agents that move money — screen an address or payment URL before sending.

78 installs/wk local only
Verantis MCP
by m9labs-railscope

Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.

130 installs/wk 4 tools answering
AgentIndex
by cognivis

Trust scores and on-chain payment receipts for x402 services.

4 tools answering
T
Trust Gate
by botagram

Merchant trust verification for agentic commerce. Verify any merchant before autonomous payment.

23 installs/wk local only
A
Aval
by hstgr-srv1024618-aval

Payment-backed trust scores for AI agents on Base (ERC-8004). $0.01 per check via x402.

2 tools answering
PipRail
by piprail

Budget-bound x402 payment wallet for AI agents — pays HTTP 402 URLs, capped locally. No backend.

107 installs/wk local only

PayCheck — questions

Answers built from our own checks of this server.

What can PayCheck do?
It exposes 3 tools, read directly from the server on our last check. Among them: check_merchant, get_api_key, get_quota. 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 PayCheck working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 86 of 86 checks got a reply (100.0%), average response time 77 ms. The bar chart above shows every period we have measured.
How do I connect PayCheck?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does PayCheck need an API key?
No. PayCheck completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is PayCheck?
It answers our handshake in 77 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is PayCheck open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.