RetryHub
REMOTE · CHATGPT.RETRYHUB.COM
Merchant account rescue and prep: shutdown checklists, fit hints, policy and dispute-ratio checks.
Available components
Last scanned (8 hours ago)
Scores higher than 53% 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability44
- 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 2092 tokens (~139/item across 15 items; 8 tools + 7 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "build_shutdown_checklist" implies "shutdown" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- 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
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 67
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.retryhub.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.retryhub.com | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 66bad4660abcd04b47e0784102b63eac81d |
| SANs: chatgpt.retryhub.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.retryhub.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| retryhub.com. | No DS | 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.retryhub.com/mcp | Verified | 200 | |
| http (plaintext) | http://chatgpt.retryhub.com/mcp | HTTPS enforced | 308 | https://chatgpt.retryhub.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 →
build_application_checklist Build an application checklist ~194
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_type | string | yes | Business type or niche, such as supplement subscriptions or online coaching. |
| country_or_entity | string | yes | Country of the business entity, such as United States or Germany. |
| processing_history | string | yes | Whether the business is new, processing now, recently shut down, or under a hold or limitation. |
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string|null | yes | – |
| business_label | string|null | yes | – |
| cta | object | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| history_label | string|null | yes | – |
| never_share_here | array | yes | – |
| ok | boolean | yes | – |
| region_label | string|null | yes | – |
| sections | array | yes | – |
No examples provided.
build_shutdown_checklist Build a shutdown checklist ~197
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.
| Name | Type | Req | Description |
|---|---|---|---|
| notes | string | – | Optional short context. Do not include names, emails, card numbers, or government IDs. |
| processor | string | yes | The processor involved. Use other when it is not Stripe, PayPal, or Shopify Payments. |
| situation | string | yes | What the merchant is dealing with. |
| still_selling | boolean | – | True when checkout is still taking orders. |
| Name | Type | Req | Description |
|---|---|---|---|
| cta | object | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| ok | boolean | yes | – |
| processor_label | string|null | yes | – |
| situation_label | string|null | yes | – |
| steps | array | yes | – |
No examples provided.
check_dispute_ratio Check a dispute ratio ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| monthly_disputes | integer | – | Disputes or chargebacks in the same month, if the merchant gave a count. |
| monthly_transactions | integer | – | Settled transactions in the month, if the merchant gave a count. |
| summary | string | – | Optional pasted summary, such as 12 disputes out of 400 transactions, or 1.5%. |
| Name | Type | Req | Description |
|---|---|---|---|
| basis_points | number|null | yes | – |
| basis_points_label | string|null | yes | – |
| cta | object | yes | – |
| disclaimer | string | yes | – |
| dispute_percent_label | string|null | yes | – |
| dispute_ratio | number|null | yes | – |
| error | string|null | yes | – |
| fixes | array | yes | – |
| formula | string | yes | – |
| input_mode | – | yes | – |
| monthly_disputes | number|null | yes | – |
| monthly_transactions | number|null | yes | – |
| network_context | array | yes | – |
| not_a_network_ratio | string | yes | – |
| ok | boolean | yes | – |
| reading | string|null | yes | – |
| used_numeric_fields | boolean | yes | – |
No examples provided.
check_policy_readiness Check policy readiness ~284
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_type | string | yes | Business type or niche, such as supplement subscriptions or online coaching. |
| delivery_model | string | – | How customers receive what they buy. Leave unset if unknown. |
| policy_text | string | yes | Refund, cancellation, shipping, or terms text pasted from the merchant's own site. No customer names or order details. |
| sells_subscriptions | boolean | – | True when the business bills customers on a recurring basis. Leave unset if unknown. |
| statement_descriptor | string | – | The name that appears on the customer's card statement, if the merchant knows it. |
| Name | Type | Req | Description |
|---|---|---|---|
| business_label | string|null | yes | – |
| characters_checked | number | yes | – |
| checks | array | yes | – |
| cta | object | yes | – |
| delivery_model | – | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| fix_list_text | string|null | yes | – |
| not_legal_review | string | yes | – |
| ok | boolean | yes | – |
| reading | – | yes | – |
| reading_label | string|null | yes | – |
| subscription_checks | boolean | yes | – |
| summary | string|null | yes | – |
No examples provided.
compare_processor_fit Compare processor fit ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| current_processor | string | yes | The processor the merchant uses now. Use none for a business that has not processed yet. |
| niche | string | yes | Business niche, such as supplement subscriptions. |
| situation | string | yes | How things stand with the current processor. |
| Name | Type | Req | Description |
|---|---|---|---|
| cta | object | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| ok | boolean | yes | – |
| processor_label | string|null | yes | – |
| reading | string|null | yes | – |
| rows | array | yes | – |
| verdict | – | yes | – |
| verdict_label | string|null | yes | – |
No examples provided.
match_merchant_account Match a merchant account ~247
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country_or_entity | string | yes | Country of the business entity, such as United States or Germany. |
| current_processor | string | – | Current or previous processor name, if the merchant mentions one. |
| monthly_processing_volume | string | yes | Monthly card volume in the merchant's own words, such as $80,000. |
| niche | string | yes | Business niche or vertical, such as skincare subscriptions. |
| what_happened | string | yes | What happened: shutdown, limitation, fund hold, or a new business. No account numbers. |
| Name | Type | Req | Description |
|---|---|---|---|
| cta | object | yes | – |
| disclaimer | string | yes | – |
| documents | array | yes | – |
| error | string|null | yes | – |
| fit | – | yes | – |
| fit_label | string|null | yes | – |
| niche_label | string|null | yes | – |
| ok | boolean | yes | – |
| published_statements | array | yes | – |
| rationale | string|null | yes | – |
| region_label | string|null | yes | – |
| situation_summary | string|null | yes | – |
| timeline | string|null | yes | – |
No examples provided.
start_application Start a RetryHub application ~356
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.
| 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 RetryHub 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.
start_application_handoff Start a RetryHub application ~221
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country_or_entity | string | yes | Country of the business entity, such as United States or Germany. |
| current_processor | string | – | Current or previous processor name, if the merchant mentioned one. |
| monthly_volume_band | string | yes | Monthly card volume band in US dollars, mapped from what the merchant said. Use not_sure if unknown. |
| niche | string | yes | Business niche, such as skincare subscriptions. |
| situation | string | yes | The merchant's processing situation. |
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string|null | yes | – |
| approval_window | string|null | yes | – |
| cta | object | yes | – |
| disclaimer | string | yes | – |
| error | string|null | yes | – |
| ok | boolean | yes | – |
| powered_by | string | yes | – |
| privacy_note | string | yes | – |
| summary | array | yes | – |
| summary_text | string|null | yes | – |
| telegram_url | string|null | yes | – |
No examples provided.
How do I install the RetryHub MCP server?
RetryHub is a hosted endpoint at https://chatgpt.retryhub.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.retryhub.com
claude mcp add --transport http com-retryhub-retryhub 'https://chatgpt.retryhub.com/mcp'
What is the RetryHub MCP server?
RetryHub is an MCP server listed in the public MCP registry as com.retryhub/retryhub. Merchant account rescue and prep: shutdown checklists, fit hints, policy and dispute-ratio checks. This page covers its hosted endpoint (https://chatgpt.retryhub.com/mcp).
Is the RetryHub MCP server safe to use?
RetryHub scores 68 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 RetryHub MCP server expose?
RetryHub exposes 8 tools: match_merchant_account, build_shutdown_checklist, check_dispute_ratio, build_application_checklist, start_application_handoff, and 3 more. Their descriptions and schemas cost roughly 1,855 tokens of context every time the server is loaded.
Does the RetryHub MCP server require authentication?
No. We connected to RetryHub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RetryHub MCP server still maintained?
RetryHub 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.
What did VerifyMCP test on the RetryHub MCP server?
VerifyMCP ran 14 checks on RetryHub, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.