io.usefulapi/recurly
REMOTE · RECURLY.USEFULAPI.IO · SCANNED SEP 20
MCP server for Recurly — accounts, subscriptions, invoices, plans; cancel & pause subs.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1119 tokens (~139/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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/recurly MCP server?
io.usefulapi/recurly is a hosted endpoint at https://recurly.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 · recurly.usefulapi.io
claude mcp add --transport http io-usefulapi-recurly 'https://recurly.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-recurly": {
"url": "https://recurly.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-recurly": {
"type": "http",
"url": "https://recurly.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-recurly] url = "https://recurly.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-recurly": {
"type": "remote",
"url": "https://recurly.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-recurly --url 'https://recurly.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-recurly:
url: "https://recurly.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-recurly": {
"Transport": "http",
"Url": "https://recurly.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-recurly -t streamable-http -u 'https://recurly.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-recurly": {
"type": "http",
"url": "https://recurly.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 2 Aug 26 0
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 1 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ 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 20 Sept 2026 · Probed https://recurly.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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e9f93f1b69b3a631134438904c78f0d7 |
| SANs: usefulapi.io, recurly.usefulapi.io, *.recurly.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 recurly.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://recurly.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://recurly.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://recurly.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://recurly.usefulapi.io/mcp |
| Authorisation server | https://recurly.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recurly.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://recurly.usefulapi.io/mcp | Inconclusive | 401 |
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 →
recurly_cancel_subscription Cancel subscription (WRITE — changes billing) ~104
Cancel a subscription. By default it stays active until the end of the current term (`term_end`); pass timeframe `bill_date` to cancel effective the next bill date. This changes billing state. Recurly: PUT /subscriptions/{subscription_id}/cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | Subscription id (no prefix) or "uuid-<uuid>". |
| timeframe | string | – | When cancellation takes effect. Default term_end (end of current term). |
No output schema declared.
No examples provided.
recurly_get_account Get account ~87
Fetch one account by its id (no prefix, e.g. e28zov4fw0v2) or by your own code prefixed with `code-` (e.g. code-bob). Recurly: GET /accounts/{account_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | Account id (no prefix) or "code-<your account code>". |
No output schema declared.
No examples provided.
recurly_get_subscription Get subscription ~62
Fetch one subscription by its id (no prefix) or by uuid prefixed with `uuid-`. Recurly: GET /subscriptions/{subscription_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | Subscription id (no prefix) or "uuid-<uuid>". |
No output schema declared.
No examples provided.
recurly_list_accounts List accounts ~197
List customer accounts on the site. Supports cursor pagination and filtering. Recurly: GET /accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| begin_time | string | – | ISO 8601 lower bound (inclusive) for the `sort` field, e.g. 2026-01-01T00:00:00Z. |
| string | – | Filter by account email (filter_account_email). | |
| end_time | string | – | ISO 8601 upper bound (exclusive) for the `sort` field. |
| limit | integer | – | Page size, 1–200. Default 20 (Recurly default). |
| order | string | – | Sort direction. Default desc. |
| past_due | boolean | – | If true, only past-due accounts. |
| sort | string | – | Field to order by. Default created_at. |
| subscriber | boolean | – | If true, only accounts with a subscription; if false, only without. |
No output schema declared.
No examples provided.
recurly_list_invoices List invoices ~211
List invoices across the site, or for one account when `account_id` is given (GET /accounts/{account_id}/invoices). Recurly: GET /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Optional: scope to one account. Id (no prefix) or "code-<code>". |
| begin_time | string | – | ISO 8601 lower bound (inclusive) for the `sort` field, e.g. 2026-01-01T00:00:00Z. |
| end_time | string | – | ISO 8601 upper bound (exclusive) for the `sort` field. |
| limit | integer | – | Page size, 1–200. Default 20 (Recurly default). |
| order | string | – | Sort direction. Default desc. |
| sort | string | – | Field to order by. Default created_at. |
| state | string | – | Filter by invoice state. |
| type | string | – | Filter by invoice type. |
No output schema declared.
No examples provided.
recurly_list_plans List plans ~155
List the site's subscription plans, optionally filtered by state. Recurly: GET /plans.
| Name | Type | Req | Description |
|---|---|---|---|
| begin_time | string | – | ISO 8601 lower bound (inclusive) for the `sort` field, e.g. 2026-01-01T00:00:00Z. |
| end_time | string | – | ISO 8601 upper bound (exclusive) for the `sort` field. |
| limit | integer | – | Page size, 1–200. Default 20 (Recurly default). |
| order | string | – | Sort direction. Default desc. |
| sort | string | – | Field to order by. Default created_at. |
| state | string | – | Filter by plan state. |
No output schema declared.
No examples provided.
recurly_list_subscriptions List subscriptions ~201
List subscriptions across the site, optionally scoped to one account and/or filtered by state. Provide `account_id` to use GET /accounts/{account_id}/subscriptions; otherwise GET /subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Optional: scope to one account. Id (no prefix) or "code-<code>". |
| begin_time | string | – | ISO 8601 lower bound (inclusive) for the `sort` field, e.g. 2026-01-01T00:00:00Z. |
| end_time | string | – | ISO 8601 upper bound (exclusive) for the `sort` field. |
| limit | integer | – | Page size, 1–200. Default 20 (Recurly default). |
| order | string | – | Sort direction. Default desc. |
| sort | string | – | Field to order by. Default created_at. |
| state | string | – | Filter by subscription state. |
No output schema declared.
No examples provided.
recurly_pause_subscription Pause subscription (WRITE — changes billing) ~102
Pause a subscription for a number of upcoming billing cycles. Set `remaining_pause_cycles` to 0 to resume/cancel an existing pause. This changes billing state. Recurly: PUT /subscriptions/{subscription_id}/pause.
| Name | Type | Req | Description |
|---|---|---|---|
| remaining_pause_cycles | integer | yes | Number of billing cycles to pause. 0 resumes/cancels a scheduled pause. |
| subscription_id | string | yes | Subscription id (no prefix) or "uuid-<uuid>". |
No output schema declared.
No examples provided.
What is the io.usefulapi/recurly MCP server?
io.usefulapi/recurly is an MCP server listed in the public MCP registry as io.usefulapi/recurly. MCP server for Recurly, accounts, subscriptions, invoices, plans; cancel & pause subs. This page covers its hosted endpoint (https://recurly.usefulapi.io/mcp).
Is the io.usefulapi/recurly MCP server safe to use?
io.usefulapi/recurly scores 85 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 io.usefulapi/recurly MCP server expose?
io.usefulapi/recurly exposes 8 tools: recurly_list_accounts, recurly_get_account, recurly_list_subscriptions, recurly_get_subscription, recurly_list_invoices, and 3 more. Their descriptions and schemas cost roughly 1,119 tokens of context every time the server is loaded.
Does the io.usefulapi/recurly MCP server require authentication?
Yes. io.usefulapi/recurly asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/recurly MCP server still maintained?
io.usefulapi/recurly is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.