PayFresco Payment Planner MCP server
com.payfresco/payment-plannerpayfresco.comstreamable-httpv1.2.0Scanned
Check fit for PayFresco processing, application readiness, payout cash flow, and currency plans.
8 tools: 2 do something that can't be undone and 6 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the PayFresco Payment Planner MCP server can do
The PayFresco Payment Planner MCP server is published by payfresco.com, a domain the MCP Registry verified. It has 8 tools. It can do things that cannot be undone, such as sending, paying or publishing (assess_payment_setup and start_application) and create or change data (6 tools: build_readiness_checklist, plan_currency_settlement, check_eligibility, estimate_payout_schedule and 2 more), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (start_application).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Can't be undone 2Claude Code: ask
assess_payment_setupCompare a registration country, target markets, business category, billing model, presentment currencies, settlement currencies, and payment methods with the PayFresco capability c…1 finding
Why it is in this group
- The name "assess_payment_setup" says "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "assess_payment_setup" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "assess_payment_setup" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
start_applicationSend the merchant's application request to the PayFresco team so they can follow up.Reads text others writeNo findings
Why it is in this group
- The name "start_application" says "start": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
- idempotentHint: false
Changes things 6Claude Code: ask
application_handoffTurn 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
application_readinessSelf-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 descr…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
build_readiness_checklistBuild an operational preparation checklist for website policies, refunds, fulfillment, billing disclosures, currency handling, UK and EEA authentication questions, reconciliation, …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
check_eligibilityQuick qualitative screen of whether a business can apply to PayFresco, from registration country, customer markets, business category, monthly volume band, and processing history.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
estimate_payout_scheduleIllustrate 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…1 finding
Why it is in this group
- The name "estimate_payout_schedule" says "schedule": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "estimate_payout_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "estimate_payout_schedule" says "schedule": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
plan_currency_settlementBuild a route table from customer payment currencies to desired settlement currencies.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (2 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://chatgpt.payfresco.com/mcp: tools/list returned 8 tools to an anonymous client, including assess_payment_setup (irreversible), start_application (irreversible), build_readiness_checklist (write), plan_currency_settlement (write), check_eligibility (write) and 3 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "assess_payment_setup" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "assess_payment_setup" says "payment": a word that usually means money moves, which cannot be taken back.
The server marks "estimate_payout_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "estimate_payout_schedule" says "schedule": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http payment-planner https://chatgpt.payfresco.com/mcpclaude mcp add --transport http payment-planner https://chatgpt.payfresco.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__payment-planner__assess_payment_setup",
"mcp__payment-planner__build_readiness_checklist",
"mcp__payment-planner__plan_currency_settlement",
"mcp__payment-planner__check_eligibility",
"mcp__payment-planner__estimate_payout_schedule",
"mcp__payment-planner__application_handoff",
"mcp__payment-planner__application_readiness",
"mcp__payment-planner__start_application"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as payment-planner. Review it before you use it.
Capability tags behind 1 rule
- mcp__payment-planner__start_application untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.payfresco/payment-planner/verify?hash=4712865e94d6961d3d4f2cbb3e70a6ab78f9ea7c35da86927f5462c4b23f091c" | jq -e '.changed == false'Pinned hash 4712865e94d6, from Nov 16, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.payfresco/payment-planner/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.payfresco/payment-planner)Source: MCP Registry. Synced Nov 3, 2026, 06:17 UTC.
PayFresco Payment Planner MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the PayFresco Payment Planner MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 8 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the PayFresco Payment Planner MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the PayFresco Payment Planner MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: assess_payment_setup and start_application.
What tools does the PayFresco Payment Planner MCP server have?
- 8 tools: 2 irreversible, 6 write. assess_payment_setup, start_application, build_readiness_checklist, plan_currency_settlement, check_eligibility, estimate_payout_schedule, application_handoff and application_readiness.
Does the PayFresco Payment Planner MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the PayFresco Payment Planner MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the PayFresco Payment Planner MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.