PayCheck
io.github.toolweather/paycheck · v1.0.0
Score merchant domain, https URL, or 0x wallet trust before an agent pays. Does not send payments.
MCPremoteAPI keyCryptoFinance
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 3 tools · 1 read, 2 write · Finance, Crypto, Knowledge & docs
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://paycheck.toolweather.workers.dev/mcpTools
3 tools listed at last check
check_merchantDecide 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 nget_quotaShow 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 coget_api_keyMint 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 retu
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.github.toolweather/paycheck)