RetryHub

com.retryhub/retryhubretryhub.comstreamable-httpv1.2.0Scanned 1 hour ago

Merchant account rescue and prep: shutdown checklists, fit hints, policy and dispute-ratio checks.

8 tools: 1 do something that can't be undone, 6 change things and 1 only read.

Reads private data · 0
Reads text others write · 1
Can send data out · 0
2 findings

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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 1Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

start_applicationSend the merchant's application request to the RetryHub 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 RetryHub 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 RetryHub 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 6Creates or changes something that can be changed back.Claude Code: ask

build_application_checklistUse when a merchant asks what documents to prepare before applying for a high-risk merchant account.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
Use when a merchant asks what documents to prepare before applying for a high-risk merchant account. Inputs are the business type, the country or entity, and the processing history (new business, processing now, recently shut down, or under a fund hold or limitation). Returns a document checklist tailored to those answers, a list of things never to paste into the chat, and a link to the RetryHub application. Describes documents by type only. Does not collect or review documents, approve an account, or quote fees. Do not send card numbers, government IDs, or bank details.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
build_shutdown_checklistUse when a merchant asks what to do after a Stripe, PayPal, or Shopify Payments shutdown, limitation, account review, or fund hold.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
Use when a merchant asks what to do after a Stripe, PayPal, or Shopify Payments shutdown, limitation, account review, or fund hold. Returns a practical checklist: what to save, how to answer the processor, how reserves and holds work in general, how to keep legitimate sales from stalling, and a backup-processor step that links to RetryHub when the situation is in scope. This is not legal advice and it does not predict when held funds will be released. Do not send card numbers, government IDs, or bank details.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
check_dispute_ratioUse when a merchant gives a monthly transaction count and dispute count, or pastes a short summary of those figures, and wants the dispute ratio.1 finding
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.
Findings
- Info
  The description mentions "credentials".
  Matched text
  description: "...not send card numbers or other account credentials."
  What this check looks for
Description, as the server wrote it
Use when a merchant gives a monthly transaction count and dispute count, or pastes a short summary of those figures, and wants the dispute ratio. Computes disputes divided by transactions, explains how that simple ratio differs from Visa VAMP and Mastercard ECM, and summarizes publicly described monitoring thresholds with source links. Suggests ordinary operational fixes. Does not determine whether a card network has identified the business, and it is not legal or financial advice. Do not send card numbers or other account credentials.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
check_policy_readinessUse when a merchant pastes the refund, cancellation, shipping, or terms text from their website and asks whether it is ready for a merchant account review.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
Use when a merchant pastes the refund, cancellation, shipping, or terms text from their website and asks whether it is ready for a merchant account review. Inputs are the business type, the pasted policy text, and optionally whether they sell subscriptions, how they deliver (physical goods, digital or service, or both), and their card statement descriptor. Returns a found or missing result for the gaps reviewers commonly ask about (refund policy and window, how to cancel, renewal terms, delivery or access timing, contact method, descriptor) with a suggested fix for each. It is a keyword check, not a legal review, and it does not approve an account. The pasted text is not stored or repeated back. Do not include customer names, order details, card numbers, or bank details.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
match_merchant_accountUse when a merchant asks whether a high-risk merchant account review may fit their business.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
Use when a merchant asks whether a high-risk merchant account review may fit their business. Inputs are the niche, monthly processing volume, country or entity, the current processor if any, and what happened (for example a shutdown, a limitation, a fund hold, or a new business). Returns a qualitative fit of likely good fit, needs review, or outside this app's scope, the documents people typically prepare, a qualitative timeline, and a link to the RetryHub application when the category is in scope. Does not approve an account, quote fees, or promise a timeline. Do not send card numbers, government IDs, or bank details.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
start_application_handoffUse when a merchant is ready to apply with RetryHub and wants to carry what they already said in this chat into the application.1 finding
Why it is in this group
- The name "start_application_handoff" says "start": 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 "start_application_handoff" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_application_handoff" says "start": a word for a change.
  What this check looks for
Description, as the server wrote it
Use when a merchant is ready to apply with RetryHub and wants to carry what they already said in this chat into the application. Inputs are non-sensitive answers only: niche, monthly volume band, country or entity, current processor, and situation. Returns a short summary the merchant can paste into the application or the RetryHub Telegram bot, plus both links. Nothing is stored and the answers are not added to the links. Does not submit an application, approve an account, or quote fees. Do not send names, emails, card numbers, government IDs, or bank details.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true

Only reads 1Looks things up and changes nothing.Show 1 read-only tool

compare_processor_fitUse when a merchant asks whether to stay with their current processor (such as Stripe, PayPal, Shopify Payments, or Square) or move to a high-risk merchant account.No findings
Why it is in this group
- The name "compare_processor_fit" says "compare": a word for reading.
Description, as the server wrote it
Use when a merchant asks whether to stay with their current processor (such as Stripe, PayPal, Shopify Payments, or Square) or move to a high-risk merchant account. Inputs are the current processor, the niche, and the current situation. Returns a qualitative side-by-side on onboarding, category tolerance, account stability, reserves, paperwork, pricing approach, and disputes, with a plain-language reading of which path to look at first. Gives no fee numbers or approval odds and is not financial advice. Do not send card numbers, government IDs, or bank details.
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.; start_application
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.

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info

Warnstart_application_handoff
The server marks "start_application_handoff" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_application_handoff" says "start": a word for a change.
What this check looks for
Infocheck_dispute_ratio
The description mentions "credentials".
Matched text
description: "...not send card numbers or other account credentials."
What this check looks for

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.

All changes to this server

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http retryhub https://chatgpt.retryhub.com/mcp

claude mcp add --transport http retryhub https://chatgpt.retryhub.com/mcp

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

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__retryhub__compare_processor_fit"
    ],
    "ask": [
      "mcp__retryhub__match_merchant_account",
      "mcp__retryhub__build_shutdown_checklist",
      "mcp__retryhub__check_dispute_ratio",
      "mcp__retryhub__build_application_checklist",
      "mcp__retryhub__start_application_handoff",
      "mcp__retryhub__check_policy_readiness",
      "mcp__retryhub__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 retryhub. Review it before you use it.

Capability tags behind 1 rule

mcp__retryhub__start_application untrusted-input

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://anlyon.dev/api/v1/servers/com.retryhub/retryhub/verify?hash=4ee9494f69eec0cf83f226bd63324df4bff559b856b016da6c5d201688890a58" | jq -e '.changed == false'

Pinned hash 4ee9494f69ee, from Nov 3, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.retryhub/retryhub/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/com.retryhub/retryhub.svg)](https://anlyon.dev/servers/com.retryhub/retryhub)

Source: MCP Registry. Synced Nov 3, 2026, 06:17 UTC.