agentgates.aiVerified
Confidential computers for AI swarms: sealed VMs (Intel TDX) by the hour, USDC over x402.
Finance & CryptoPayments & trading
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 514 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Payments & trading
Check fit for PayFresco processing, application readiness, payout cash flow, and currency plans.
2 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using PayFresco Payment Planner
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http payfresco-payment-planner https://chatgpt.payfresco.com/mcpCapabilities
Turn business facts already discussed into answers the user can copy into PayFresco's application form, list what to enter only on PayFresco's own site, and give the apply link. Runs the same eligibility screen first. Does not fill in, submit, or send an application, does not contact anyone, and never collects ID numbers, bank details, or contact details.
DiscoveredSelf-check of what a business has prepared before applying to PayFresco: registration documents, a live website with products and prices, a published refund policy, a product description, a volume estimate, processing statements, and, if relevant, an explanation of a previous account closure. Returns ready, missing, not answered, or not applicable for each item, a copyable checklist, and what to expect after applying (approval in about 3 days, the starting volume ramp, the reserve, payouts, and currencies). Readiness is not an approval chance. Does not approve a merchant, quote fees, submit an application, or contact anyone.
DiscoveredCompare a registration country, target markets, business category, billing model, presentment currencies, settlement currencies, and payment methods with the PayFresco capability catalog. Returns documented, conditional, unsupported, and unknown requirements. Does not approve a merchant, quote a fee, submit an application, or contact anyone. Use ISO country and currency codes. Unknown means that requirement has no publication-approved coverage.
DiscoveredBuild an operational preparation checklist for website policies, refunds, fulfillment, billing disclosures, currency handling, UK and EEA authentication questions, reconciliation, and provider questions. Does not collect documents and does not mean legal compliance, underwriting approval, or production readiness. Distinguish the UK, the EU, and the EEA.
DiscoveredQuick qualitative screen of whether a business can apply to PayFresco, from registration country, customer markets, business category, monthly volume band, and processing history. Uses the capability catalog, including sanctioned-jurisdiction and app-prohibited category rules. Returns no_blocker_found, blocked, outside_app_scope, needs_information, or unconfirmed, plus what to prepare and the apply link. Does not approve a merchant, estimate an approval chance for this business, quote fees, submit an application, or contact anyone.
DiscoveredIllustrate PayFresco's 10% reserve on a 90-day rolling basis and its T+2 Monday, Wednesday, and Friday payout cadence using a monthly volume the user supplies, with an optional fee percentage the user supplies. Shows reserve held, released, and balance by month, and an example payout week. Set show_starting_cap to compare the volume with PayFresco's starting volume ramp of up to $3k/day. Labeled as an illustration using the user's numbers. Never invents or quotes a PayFresco fee or exchange rate, and does not move money.
DiscoveredBuild a route table from customer payment currencies to desired settlement currencies. Says whether conversion is required and whether a route is documented. Uses only caller-supplied amounts and exchange-rate assumptions. Does not invent rates or fees. States PayFresco's approved reserve (10%, 90-day rolling) and payout timing (T+2 on Monday, Wednesday, and Friday) as conditional on underwriting, not a promise. Does not move money.
DiscoveredSend the merchant's application request to the PayFresco team so they can follow up. This is the only tool that sends data. Before calling it you MUST: (1) ask whether the merchant wants PayFresco to contact them about an application; (2) collect only name, business name, email, an optional Telegram handle, monthly card volume, the current processor, and what happened (shutdown, hold, or other); (3) show the merchant every value you will send, exactly as you will send it; (4) get an explicit yes in chat. Set consent and user_confirmed to true only after that yes; otherwise the server rejects the request. Never include SSNs or tax IDs, bank account, routing, or IBAN numbers, card numbers, passwords, or ID documents, and do not add other fields. If sending is not available, the result gives the application link and the Telegram bot instead.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 520 ms | 8 |