SmartRetry Payment Tools
REMOTE · TOOLS.MCP.SMARTRETRY.COM
Free BIN, issuer, MCC and decline code lookups for card payments (Visa, Mastercard, Stripe, Adyen).
Available components
Last scanned (1 hour ago)
Scores higher than 69% 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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 507 tokens (~126/item across 4 items; 4 tools + 0 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 76
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://tools.mcp.smartretry.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=smartretry.com | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | f52e11b15b824cec0eebdfee96a8760e |
| SANs: smartretry.com, tools.mcp.smartretry.com, *.tools.mcp.smartretry.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of tools.mcp.smartretry.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| smartretry.com. | present | 2371 | 13 | Verified |
| tools.mcp.smartretry.com. | Verified address RRset verified with the apex keys |
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; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tools.mcp.smartretry.com/mcp | Verified | 200 | |
| http (plaintext) | http://tools.mcp.smartretry.com/mcp | HTTPS enforced | 301 | https://tools.mcp.smartretry.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 →
lookup_bin BIN lookup ~117
BIN / IIN lookup (card BIN checker). Returns the card network (Visa, Mastercard, Amex and others), card type (credit, debit, prepaid), card level, issuing bank and country for the first 6 to 8 digits of a card number. Use it to identify a card or where it was issued. Never pass a full card number.
| Name | Type | Req | Description |
|---|---|---|---|
| bin | string | yes | The first 6 to 8 digits of a card number (the BIN / IIN). Digits only. Never send a full card number. |
No output schema declared.
No examples provided.
lookup_decline_code Decline code lookup ~138
Explain why a card payment was declined or failed. Accepts a decline code, response code, refusal reason or error message (for example "51", "05", "do_not_honor" or "insufficient funds") from card networks and processors such as Visa, Mastercard, Stripe and Adyen. Optionally narrow by provider.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | A decline code or message, for example "51", "05", "do_not_honor" or "insufficient funds". |
| provider | string | – | Optional provider or card network to narrow the result, for example "Visa", "Mastercard" or "Stripe". |
No output schema declared.
No examples provided.
lookup_issuer Issuing bank lookup ~79
Find card issuing banks by name, with their country, website and phone number. Accepts partial or misspelled names. Use it to confirm the bank behind a card or to find how to contact an issuer.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Issuing bank name or part of it, for example "chase" or "Barclays". |
No output schema declared.
No examples provided.
lookup_mcc Merchant category code (MCC) lookup ~94
Merchant category code (MCC) lookup. Pass a 4-digit MCC for its full definition (category group, high-risk flag, Visa and Mastercard definitions), or describe a business (for example "grocery store" or "software") to find the matching MCC.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A 4-digit merchant category code (for example "5411") or a business type (for example "grocery"). |
No output schema declared.
No examples provided.
How do I install the SmartRetry Payment Tools MCP server?
SmartRetry Payment Tools is a hosted endpoint at https://tools.mcp.smartretry.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 · tools.mcp.smartretry.com
claude mcp add --transport http com-smartretry-payment-tools 'https://tools.mcp.smartretry.com/mcp'
What is the SmartRetry Payment Tools MCP server?
SmartRetry Payment Tools is an MCP server listed in the public MCP registry as com.smartretry/payment-tools. Free BIN, issuer, MCC and decline code lookups for card payments (Visa, Mastercard, Stripe, Adyen). This page covers its hosted endpoint (https://tools.mcp.smartretry.com/mcp).
Is the SmartRetry Payment Tools MCP server safe to use?
SmartRetry Payment Tools scores 77 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 SmartRetry Payment Tools MCP server expose?
SmartRetry Payment Tools exposes 4 tools: lookup_bin, lookup_issuer, lookup_mcc, lookup_decline_code. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.
Does the SmartRetry Payment Tools MCP server require authentication?
No. We connected to SmartRetry Payment Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SmartRetry Payment Tools MCP server still maintained?
SmartRetry Payment Tools 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.