MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Payments & trading

PayFresco Payment Planner

Check fit for PayFresco processing, application readiness, payout cash flow, and currency plans.

Checks passed
12 / 22

2 failed · 8 not measured

Median response
520 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
8

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
310
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 520 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name payfresco-payment-planner.

  • Pass
    Lists tools

    tools/list returned 8 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 520 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 520 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    9 of 68 parameters have a description (13%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-03T06:04:50.529777Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using PayFresco Payment Planner

Connect to this server

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/mcp

Capabilities

Tools 8

application_handoff

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.

Discovered
application_readiness

Self-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.

Discovered
assess_payment_setup

Compare 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.

Discovered
build_readiness_checklist

Build 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.

Discovered
check_eligibility

Quick 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.

Discovered
estimate_payout_schedule

Illustrate 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.

Discovered
plan_currency_settlement

Build 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.

Discovered
start_application

Send 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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected520 ms8