ifthenpay Payments MCP
REMOTE · AI.IFTHENPAY.COM
Remote MCP for ifthenpay payments: Multibanco, MB WAY and Payshop.
Available components
Last scanned (7 hours ago)
Scores higher than 66% 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1556 tokens (~194/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "mbway_request_payment" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 15 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 14 Oct 26 +1
- Stability: 0.97 → pass security
- 13 Oct 26 −1
- Stability: pass → 0.97 functional
- 10 Oct 26 +2
- Stability: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
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://ai.ifthenpay.com/mcp/payments/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ifthenpay.com | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 79f01eb10b0fafd213bb8154962f31fa |
| SANs: ifthenpay.com, *.ifthenpay.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 insecure
Validation of ai.ifthenpay.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ifthenpay.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=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai.ifthenpay.com/mcp/payments/ | Verified | 200 | |
| http (plaintext) | http://ai.ifthenpay.com/mcp/payments/ | HTTPS enforced | 301 | https://ai.ifthenpay.com/mcp/payments/ |
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 →
creditcard_create_payment ~171
Creates a credit/debit card payment session and returns a payment URL. The customer is redirected to a hosted checkout page to complete payment with their card.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Payment amount in EUR (e.g. 10.50). |
| cancel_url | string | yes | URL to redirect the customer if they cancel the payment. |
| ccard_key | string | yes | ifthenpay Credit Card key. |
| error_url | string | yes | URL to redirect the customer if the payment fails. |
| language | string | – | Language for the checkout page (e.g. "pt", "en"). Defaults to "pt". |
| order_id | string | yes | Unique order identifier in your system (max 15 characters). |
| success_url | string | yes | URL to redirect the customer after a successful payment. |
No output schema declared.
No examples provided.
mbway_check_status ~64
Checks the status of a previously requested MB WAY payment. Returns pending, paid, declined, timeout, or cancelled.
| Name | Type | Req | Description |
|---|---|---|---|
| mbway_key | string | yes | ifthenpay MB WAY key. |
| request_id | string | yes | Request ID returned by mbway_request_payment. |
No output schema declared.
No examples provided.
mbway_request_payment ~136
Sends an MB WAY payment request to the customer's mobile phone. The customer approves the payment in the MB WAY app. Use mbway_check_status to check the result.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Payment amount in EUR (e.g. 10.50). |
| description | string | – | Short payment description shown in the MB WAY app. |
| mbway_key | string | yes | ifthenpay MB WAY key. |
| order_id | string | yes | Unique order identifier in your system (max 15 characters). |
| phone | string | yes | Customer mobile number in format "351#912345678" (country code # number). |
No output schema declared.
No examples provided.
multibanco_create_reference ~105
Creates a Multibanco payment reference that the customer can use to pay at any ATM or via online banking in Portugal.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Payment amount in EUR (e.g. 10.50). |
| expiry_days | integer | – | Number of days until the reference expires. Defaults to no expiry if omitted. |
| mb_key | string | yes | ifthenpay Multibanco key. |
| order_id | string | yes | Unique order identifier in your system. |
No output schema declared.
No examples provided.
payments_list ~293
Lists completed payments using the ifthenpay Backoffice Key. Filter by payment method, date range, order ID, reference or request ID. Returns up to 1000 most recent payments if no filters are applied.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | Filter by exact payment amount. |
| bo_key | string | yes | ifthenpay Backoffice Key (provided when signing the contract). |
| date_end | string | – | End date/time in format dd-MM-yyyy HH:mm:ss (e.g. 31-01-2024 23:59:59). |
| date_start | string | – | Start date/time in format dd-MM-yyyy HH:mm:ss (e.g. 01-01-2024 00:00:00). |
| entity | string | – | Payment method entity filter. Use: MB, MBWAY, PAYSHOP, CCARD, GOOGLE, APPLE, PIX, or a 5-digit Multibanco entity number. Leave blank for all methods. |
| order_id | string | – | Filter by order identifier. |
| reference | string | – | Filter by payment reference (Multibanco/Payshop reference or orderId for other methods). |
| request_id | string | – | Filter by the unique request token returned at payment creation. |
| sub_entity | string | – | Payment method key or sub-entity (e.g. MB KEY, MBWAY KEY, PAYSHOP KEY). Leave blank to match all. |
No output schema declared.
No examples provided.
payshop_create_reference ~121
Creates a Payshop payment reference that the customer can use to pay at any Payshop agent or CTT (postal service) in Portugal.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Payment amount in EUR (e.g. 10.50). |
| expiry_date | string | – | Expiry date in YYYYMMDD format (e.g. 20301231). Leave blank for no expiry. |
| order_id | string | yes | Unique order identifier in your system (max 25 characters). |
| payshop_key | string | yes | ifthenpay Payshop key. |
No output schema declared.
No examples provided.
pinpay_create_payment ~397
Creates a Pay by Link / PINPAY payment. Returns a shareable payment URL and a PIN code. The hosted checkout supports multiple payment methods including Credit Card, Google Pay, and Apple Pay.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | string | – | Payment methods to show in the gateway, separated by semicolons. Format: METHOD|KEY (e.g. "MBWAY|MBWAY-KEY;MB|MB-KEY;PAYSHOP|PAYSHOP-KEY;CCARD|CCARD-KEY"). Leave blank to use gateway defaults. |
| amount | number | yes | Payment amount in EUR (e.g. 10.50). |
| btn_close_label | string | – | Label text for the close/back button. |
| btn_close_url | string | – | URL for the close/back button on the payment page. |
| cancel_url | string | – | URL to redirect the customer if they cancel. |
| description | string | – | Short description shown on the payment page (max 200 characters). |
| error_url | string | – | URL to redirect the customer if the payment fails. |
| expiry_date | string | – | Link expiry date in YYYYMMDD format (e.g. 20301231). Leave blank for no expiry. |
| gateway_key | string | yes | ifthenpay Gateway key for Pay by Link / PINPAY. |
| lang | string | – | Language for the payment page: pt, en, es, fr. Defaults to pt. |
| order_id | string | yes | Unique order identifier in your system (max 15 characters). |
| otp | string | – | One-time payment: "true" makes the link expire after a single payment. |
| selected_method | string | – | Pre-select a payment method: 1=Multibanco, 2=MB WAY, 3=Payshop, 4=Credit Card, 8=Pix. |
| success_url | string | – | URL to redirect the customer after a successful payment. |
No output schema declared.
No examples provided.
pix_create_payment ~269
Creates a PIX payment for Brazilian customers. Returns a payment URL and a QR code value. Customer must have a CPF number (Brazilian tax ID).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Payment amount in BRL (e.g. 50.00). |
| customer_address | string | – | Customer street address. |
| customer_city | string | – | Customer city. |
| customer_cpf | string | yes | Customer CPF number (Brazilian tax ID), digits only (e.g. 74026594025). |
| customer_email | string | yes | Customer email address. |
| customer_name | string | yes | Full name of the customer (max 150 characters). |
| customer_phone | string | yes | Customer phone number including country code (e.g. +5585912345678). |
| customer_state | string | – | Customer state (e.g. CE, SP). |
| customer_zip_code | string | – | Customer postal/ZIP code. |
| description | string | – | Short description or reference for the payment (max 200 characters). |
| order_id | string | yes | Unique order identifier in your system (max 25 characters). |
| pix_key | string | yes | ifthenpay PIX key. |
| redirect_url | string | yes | URL to redirect the customer after payment. Check payment status via the status API after redirect. |
No output schema declared.
No examples provided.
How do I install the ifthenpay Payments MCP server?
ifthenpay Payments MCP is a hosted endpoint at https://ai.ifthenpay.com/mcp/payments/, 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 · ai.ifthenpay.com
claude mcp add --transport http com-ifthenpay-payments 'https://ai.ifthenpay.com/mcp/payments/'
What is the ifthenpay Payments MCP server?
ifthenpay Payments MCP is listed in the public MCP registry as com.ifthenpay/payments. Remote MCP for ifthenpay payments: Multibanco, MB WAY and Payshop. This page covers its hosted endpoint (https://ai.ifthenpay.com/mcp/payments/).
Is the ifthenpay Payments MCP server safe to use?
ifthenpay Payments MCP scores 76 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 ifthenpay Payments MCP server expose?
ifthenpay Payments MCP exposes 8 tools: multibanco_create_reference, mbway_request_payment, mbway_check_status, payshop_create_reference, creditcard_create_payment, and 3 more. Their descriptions and schemas cost roughly 1,556 tokens of context every time the server is loaded.
Does the ifthenpay Payments MCP server require authentication?
No. We connected to ifthenpay Payments MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ifthenpay Payments MCP server still maintained?
ifthenpay Payments MCP 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.