Recurpay MCP by usefulapi
REMOTE · RECURPAY.USEFULAPI.IO
Read subscriptions, subscribers and orders; manage renewals, billing skips and payment links.
Available components
Last scanned (7 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 65
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://recurpay.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 recurpay.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recurpay.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/recurpay/ |
| http (plaintext) | http://recurpay.usefulapi.io/mcp | Inconclusive | 302 | http://recurpay.usefulapi.io/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 →
recurpay_cancel_customer_subscription ~112
WRITE: cancel one subscriber's subscription in Recurpay (status becomes cancelled; billing and deliveries stop). This is the merchant's action on a customer's subscription, not the cancellation of this MCP server's own plan. Only the merchant can re-activate it. Ask the user to confirm the subscription first.
| Name | Type | Req | Description |
|---|---|---|---|
| cancelled_reason | string | yes | Reason shown on the subscription, e.g. 'Customer asked to cancel'. |
| subscription_id | – | yes | Recurpay subscription id (from recurpay_list_subscriptions). |
No output schema declared.
No examples provided.
recurpay_get_access_scopes ~51
Show the API scopes of the custom app whose token is connected (read-/write- subscriptions, customers, orders, plans, payments, webhooks). Use it when a tool answers 403.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recurpay_get_order ~37
Get one order with its subscriber and line items.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | – | yes | Recurpay order id (from recurpay_list_orders). |
No output schema declared.
No examples provided.
recurpay_get_plan ~46
Get one plan with its selling plans (delivery policy, billing policy, anchors, discounts).
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | – | yes | Recurpay plan id (from recurpay_list_plans). |
No output schema declared.
No examples provided.
recurpay_get_subscriber ~44
Get one subscriber (customer) with contact data, addresses and total spent.
| Name | Type | Req | Description |
|---|---|---|---|
| subscriber_id | – | yes | Recurpay subscriber id (from recurpay_list_subscribers). |
No output schema declared.
No examples provided.
recurpay_get_subscription ~54
Get one subscription with its subscriber, addresses, line items, discount codes, billing/delivery policy, payment method and billing dates.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | – | yes | Recurpay subscription id (from recurpay_list_subscriptions). |
No output schema declared.
No examples provided.
recurpay_list_order_subscriptions ~178
List the subscriptions that belong to one order.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | Only subscriptions created on or before this date. |
| created_at_min | string | – | Only subscriptions created on or after this date. |
| limit | integer | – | Results per page, 1-100 (default 100). |
| order_id | – | yes | Recurpay order id (from recurpay_list_orders). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| sort_by | string | – | Sort direction (default asc). |
| sort_key | string | – | Field to sort by (default id). |
| updated_at_max | string | – | Only subscriptions updated on or before this date. |
| updated_at_min | string | – | Only subscriptions updated on or after this date. |
No output schema declared.
No examples provided.
recurpay_list_orders ~226
List the orders generated by subscriptions (name, subscriber, status, totals). Filter by order name, subscriber email, subscription and dates. Page with next_page.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | Only orders created on or before this date. |
| created_at_min | string | – | Only orders created on or after this date. |
| string | – | Only orders of the subscriber with this email. | |
| limit | integer | – | Results per page, 1-100 (default 100). |
| name | string | – | Only orders with this name (the store's order number). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| sort_by | string | – | Sort direction (default asc). |
| sort_key | string | – | Field to sort by (default id). |
| subscription_id | – | – | Only orders of this subscription. |
| updated_at_max | string | – | Only orders updated on or before this date. |
| updated_at_min | string | – | Only orders updated on or after this date. |
No output schema declared.
No examples provided.
recurpay_list_plan_products ~88
List the products attached to one plan, with the variants excluded from it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 100). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| plan_id | – | yes | Recurpay plan id (from recurpay_list_plans). |
No output schema declared.
No examples provided.
recurpay_list_plans ~233
List the subscription plans (selling plan groups) with their delivery/billing policies and discounts. Filter by plan title, product title/handle and dates. Page with next_page.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | Only plans created on or before this date. |
| created_at_min | string | – | Only plans created on or after this date. |
| limit | integer | – | Results per page, 1-100 (default 100). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| plan_title | string | – | Only plans with this title. |
| product_handle | string | – | Only plans attached to a product with this handle. |
| product_title | string | – | Only plans attached to a product with this title. |
| sort_by | string | – | Sort direction (default asc). |
| sort_key | string | – | Field to sort by (default id). |
| updated_at_max | string | – | Only plans updated on or before this date. |
| updated_at_min | string | – | Only plans updated on or after this date. |
No output schema declared.
No examples provided.
recurpay_list_subscribers ~229
List the store's subscribers (customers with at least one subscription): name, email, phone, addresses, total spent. Filter by name, email and dates. Page with next_page.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | Only subscribers created on or before this date. |
| created_at_min | string | – | Only subscribers created on or after this date. |
| string | – | Only the subscriber with this email. | |
| first_name | string | – | Only subscribers with this first name. |
| last_name | string | – | Only subscribers with this last name. |
| limit | integer | – | Results per page, 1-100 (default 100). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| sort_by | string | – | Sort direction (default asc). |
| sort_key | string | – | Field to sort by (default id). |
| updated_at_max | string | – | Only subscribers updated on or before this date. |
| updated_at_min | string | – | Only subscribers updated on or after this date. |
No output schema declared.
No examples provided.
recurpay_list_subscriptions ~257
List the store's subscriptions (status active/paused/halted/cancelled/draft, subscriber, plan policies, line items, next_billing_at). Filter by status, plan, subscriber email and dates. Use status=halted to find subscriptions whose renewal payment failed. Page with next_page.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | Only subscriptions created on or before this date. |
| created_at_min | string | – | Only subscriptions created on or after this date. |
| string | – | Only subscriptions of the subscriber with this email. | |
| limit | integer | – | Results per page, 1-100 (default 100). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
| plan_id | – | – | Only subscriptions of this plan (id from recurpay_list_plans). |
| sort_by | string | – | Sort direction (default asc). |
| sort_key | string | – | Field to sort by (default id). |
| status | string | – | Only subscriptions with this status. |
| updated_at_max | string | – | Only subscriptions updated on or before this date. |
| updated_at_min | string | – | Only subscriptions updated on or after this date. |
No output schema declared.
No examples provided.
recurpay_list_webhooks ~112
List the webhook subscriptions of the store (topic, address, status). Needs the read-webhooks scope.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | Only webhooks created at or before this date. |
| created_at_min | string | – | Only webhooks created at or after this date. |
| limit | integer | – | Results per page, 1-100 (default 100). |
| page | integer | – | Page number, 1-based (default 1). Use next_page from the previous reply. |
No output schema declared.
No examples provided.
recurpay_renew_subscription ~124
WRITE, MAY CHARGE THE CUSTOMER: renew the subscription now. Recurpay runs the billing cycle immediately, which can charge the subscriber's saved payment method and create an order. Use it e.g. to retry a halted subscription. Only call it when the user explicitly asks for it and set confirm=true. Repeated calls may repeat the charge or notification.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Set true only after the user explicitly approved this action and its customer/charge effects. |
| subscription_id | – | yes | Recurpay subscription id (from recurpay_list_subscriptions). |
No output schema declared.
No examples provided.
recurpay_send_payment_link ~116
WRITE, CONTACTS THE CUSTOMER: generate a payment link for the subscription (renewal payment or payment-method update); Recurpay notifies the subscriber with it. Use it for halted subscriptions. Only call it when the user explicitly asks for it and set confirm=true. Repeated calls may repeat the charge or notification.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Set true only after the user explicitly approved this action and its customer/charge effects. |
| subscription_id | – | yes | Recurpay subscription id (from recurpay_list_subscriptions). |
No output schema declared.
No examples provided.
recurpay_skip_next_billing ~58
WRITE: skip the subscription's next billing/delivery cycle (the next order is not generated). Ask the user to confirm the subscription first.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | – | yes | Recurpay subscription id (from recurpay_list_subscriptions). |
No output schema declared.
No examples provided.
recurpay_update_subscriber ~119
WRITE: change a subscriber's contact data (email, first name, last name, phone). Only the fields you pass are sent. Ask the user to confirm the new values.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | New email address. | |
| first_name | string | – | New first name. |
| last_name | string | – | New last name. |
| phone | string | – | New phone number in international format, e.g. +12025550151. |
| subscriber_id | – | yes | Recurpay subscriber id (from recurpay_list_subscribers). |
No output schema declared.
No examples provided.
recurpay_update_subscription_coupon ~97
WRITE: add or remove a discount code (coupon) on one subscription; it changes what the subscriber pays on the next billings. Ask the user to confirm.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | add = apply the code, remove = take it off. |
| code | string | yes | The discount code title, e.g. TEST20. |
| subscription_id | – | yes | Recurpay subscription id (from recurpay_list_subscriptions). |
No output schema declared.
No examples provided.
How do I install the Recurpay MCP by usefulapi server?
Recurpay MCP by usefulapi is a hosted endpoint at https://recurpay.usefulapi.io/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 · recurpay.usefulapi.io
claude mcp add --transport http io-usefulapi-recurpay 'https://recurpay.usefulapi.io/mcp'
What is the Recurpay MCP by usefulapi server?
Recurpay MCP by usefulapi is listed in the public MCP registry as io.usefulapi/recurpay. Read subscriptions, subscribers and orders; manage renewals, billing skips and payment links. This page covers its hosted endpoint (https://recurpay.usefulapi.io/mcp).
Is the Recurpay MCP by usefulapi server safe to use?
Recurpay MCP by usefulapi scores 18 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 Recurpay MCP by usefulapi server expose?
Recurpay MCP by usefulapi exposes 18 tools: recurpay_get_access_scopes, recurpay_list_subscriptions, recurpay_get_subscription, recurpay_list_subscribers, recurpay_get_subscriber, and 13 more. Their descriptions and schemas cost roughly 2,181 tokens of context every time the server is loaded.
Does the Recurpay MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Recurpay MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Recurpay MCP by usefulapi server still maintained?
Recurpay MCP by usefulapi 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.