PayFresco Payment Planner
REMOTE · CHATGPT.PAYFRESCO.COM
Check fit for PayFresco processing, application readiness, payout cash flow, and currency plans.
Available components
Last scanned (4 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability34
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1716 tokens (~171/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 13% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://chatgpt.payfresco.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chatgpt.payfresco.com | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 51e51083dd32ddb5ace063b001d921f59f1 |
| SANs: chatgpt.payfresco.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of chatgpt.payfresco.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| payfresco.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chatgpt.payfresco.com/mcp | Verified | 200 | |
| http (plaintext) | http://chatgpt.payfresco.com/mcp | HTTPS enforced | 308 | https://chatgpt.payfresco.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
application_handoff Prepare an application handoff ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_model | string | – | – |
| business_category | string | – | – |
| has_refund_policy | boolean | – | – |
| monthly_volume_band | string | – | – |
| notes | string | – | – |
| payment_methods | array | – | – |
| presentment_currencies | array | – | – |
| processing_history | string | – | – |
| product_description | string | – | – |
| registration_country | string | – | – |
| settlement_currencies | array | – | – |
| target_markets | array | – | – |
| top_sales_country | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string|null | yes | – |
| approved_facts | array | yes | – |
| cta | – | yes | – |
| disclaimer | string | yes | – |
| enter_only_on_payfresco_site | array | yes | – |
| error | string|null | yes | – |
| limitations | array | yes | – |
| merchant_approval | string | yes | – |
| missing_information | array | yes | – |
| next_steps | array | yes | – |
| notes_ignored_as_data | boolean | yes | – |
| ok | boolean | yes | – |
| paste_ready_summary | string | yes | – |
| refused_actions | array | yes | – |
| screen_result | string | yes | – |
| submitted | boolean | yes | – |
| summary_fields | array | yes | – |
No examples provided.
application_readiness Check application readiness ~240
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_category | string | – | – |
| closure_explanation_ready | boolean | – | – |
| notes | string | – | – |
| previous_account_closed_by_provider | boolean | – | – |
| processing_history | string | – | – |
| processing_statements_ready | boolean | – | – |
| product_description_ready | boolean | – | – |
| refund_policy_published | boolean | – | – |
| registration_documents_ready | boolean | – | – |
| volume_estimate_ready | boolean | – | – |
| website_live_with_products_and_prices | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string|null | yes | – |
| approved_facts | array | yes | – |
| checklist_text | string | yes | – |
| cta | – | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| items | array | yes | – |
| limitations | array | yes | – |
| merchant_approval | string | yes | – |
| missing_information | array | yes | – |
| notes_ignored_as_data | boolean | yes | – |
| ok | boolean | yes | – |
| open_count | number | yes | – |
| readiness_is_not_odds | string | yes | – |
| ready_count | number | yes | – |
| refused_actions | array | yes | – |
| summary | string | yes | – |
| what_to_expect | array | yes | – |
No examples provided.
assess_payment_setup Assess a payment setup ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_model | string | – | – |
| business_category | string | – | – |
| notes | string | – | – |
| payment_methods | array | – | – |
| presentment_currencies | array | – | – |
| registration_country | string | – | – |
| settlement_currencies | array | – | – |
| target_markets | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| conditional_matches | array | yes | – |
| confirmation_questions | array | yes | – |
| disclaimer | string | yes | – |
| documented_matches | array | yes | – |
| error | string|null | yes | – |
| evidence_references | array | yes | – |
| limitations | array | yes | – |
| market_groups | array | yes | – |
| merchant_approval | string | yes | – |
| missing_information | array | yes | – |
| notes_ignored_as_data | boolean | yes | – |
| ok | boolean | yes | – |
| refused_actions | array | yes | – |
| unknown_requirements | array | yes | – |
| unsupported_requirements | array | yes | – |
No examples provided.
build_readiness_checklist Build a readiness checklist ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_model | string | – | – |
| business_category | string | – | – |
| notes | string | – | – |
| payment_methods | array | – | – |
| presentment_currencies | array | – | – |
| registration_country | string | – | – |
| settlement_currencies | array | – | – |
| target_markets | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| compliance_claimed | boolean | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| items | array | yes | – |
| limitations | array | yes | – |
| missing_information | array | yes | – |
| ok | boolean | yes | – |
| refused_actions | array | yes | – |
No examples provided.
check_eligibility Check eligibility ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_category | string | – | – |
| monthly_volume_band | string | – | – |
| notes | string | – | – |
| previous_account_closed_by_provider | boolean | – | – |
| processing_history | string | – | – |
| registration_country | string | – | – |
| target_markets | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string|null | yes | – |
| approved_facts | array | yes | – |
| blockers | array | yes | – |
| checks | array | yes | – |
| cta | – | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| headline | string | yes | – |
| limitations | array | yes | – |
| merchant_approval | string | yes | – |
| missing_information | array | yes | – |
| notes_ignored_as_data | boolean | yes | – |
| ok | boolean | yes | – |
| refused_actions | array | yes | – |
| screen_result | string | yes | – |
| things_to_prepare | array | yes | – |
No examples provided.
estimate_payout_schedule Estimate a payout schedule ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| example_week_start | string | – | – |
| fee_percent_assumption | number | – | – |
| monthly_volume | number | yes | – |
| months | integer | – | – |
| notes | string | – | – |
| show_starting_cap | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| cadence_example | array | yes | – |
| cta | – | yes | – |
| currency | string|null | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| fee_percent_assumption | string|null | yes | – |
| fee_source | string | yes | – |
| label | string | yes | – |
| limitations | array | yes | – |
| monthly_rows | array | yes | – |
| monthly_volume | string|null | yes | – |
| notes_ignored_as_data | boolean | yes | – |
| ok | boolean | yes | – |
| payout_policy | object | yes | – |
| refused_actions | array | yes | – |
| reserve_policy | object | yes | – |
| starting_cap | – | yes | – |
| steady_state_reserve_balance | string|null | yes | – |
No examples provided.
plan_currency_settlement Plan currency settlement ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_payment_currencies | array | – | – |
| desired_settlement_currencies | array | – | – |
| exchange_rate_assumptions | array | – | – |
| hypothetical_amounts | array | – | – |
| notes | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions_note | string | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| limitations | array | yes | – |
| missing_information | array | yes | – |
| ok | boolean | yes | – |
| refused_actions | array | yes | – |
| routes | array | yes | – |
No examples provided.
start_application Start a PayFresco application ~359
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | yes | Business name. |
| consent | boolean | yes | True only if the merchant explicitly agreed in chat to send these details to PayFresco and be contacted. |
| current_processor | string | – | Current or previous processor, such as Stripe. |
| string | yes | Contact email for the follow-up. | |
| monthly_volume | string | yes | Monthly card volume in the merchant's words, such as $80,000 or 80k. |
| name | string | yes | Contact name. |
| telegram | string | – | Optional Telegram username, such as @shopowner. |
| user_confirmed | boolean | yes | True only after you showed the merchant every value below and they confirmed it is correct. |
| what_happened | string | yes | shutdown, hold (fund hold or limitation), or other. |
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string | yes | – |
| error | string|null | yes | – |
| message | string | yes | – |
| ok | boolean | yes | – |
| product | string | yes | – |
| reference | string|null | yes | – |
| sent_fields | array | yes | – |
| source | string | yes | – |
| status | string | yes | – |
| submitted | boolean | yes | – |
| telegram_url | string | yes | – |
No examples provided.
How do I install the PayFresco Payment Planner MCP server?
PayFresco Payment Planner is a hosted endpoint at https://chatgpt.payfresco.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · chatgpt.payfresco.com
claude mcp add --transport http com-payfresco-payment-planner 'https://chatgpt.payfresco.com/mcp'
What is the PayFresco Payment Planner MCP server?
PayFresco Payment Planner is an MCP server listed in the public MCP registry as com.payfresco/payment-planner. Check fit for PayFresco processing, application readiness, payout cash flow, and currency plans. This page covers its hosted endpoint (https://chatgpt.payfresco.com/mcp).
Is the PayFresco Payment Planner MCP server safe to use?
PayFresco Payment Planner scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PayFresco Payment Planner MCP server expose?
PayFresco Payment Planner exposes 8 tools: assess_payment_setup, build_readiness_checklist, plan_currency_settlement, check_eligibility, estimate_payout_schedule, and 3 more. Their descriptions and schemas cost roughly 1,593 tokens of context every time the server is loaded.
Does the PayFresco Payment Planner MCP server require authentication?
No. We connected to PayFresco Payment Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PayFresco Payment Planner MCP server still maintained?
PayFresco Payment Planner is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.