io.usefulapi/memberful
REMOTE · MEMBERFUL.USEFULAPI.IO · SCANNED SEP 21
Manage Memberful members, subscriptions, plans, passes and coupons via the GraphQL API.
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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1081 tokens (~90/item across 12 items; 12 tools + 0 resources), lean.Pass
- 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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/memberful MCP server?
io.usefulapi/memberful is a hosted endpoint at https://memberful.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 · memberful.usefulapi.io
claude mcp add --transport http io-usefulapi-memberful 'https://memberful.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-memberful": {
"url": "https://memberful.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-memberful": {
"type": "http",
"url": "https://memberful.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-memberful] url = "https://memberful.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-memberful": {
"type": "remote",
"url": "https://memberful.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-memberful --url 'https://memberful.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-memberful:
url: "https://memberful.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-memberful": {
"Transport": "http",
"Url": "https://memberful.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-memberful -t streamable-http -u 'https://memberful.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-memberful": {
"type": "http",
"url": "https://memberful.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.
- 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
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.1 ▼ security
- Tool “change_subscription_expiration” was removed ▼ security
- Tool “create_coupons” was removed ▼ security
- Tool “create_member” was removed ▼ security
- Tool “get_member” was removed ▼ security
- Tool “get_subscription” was removed ▼ security
- Tool “list_members” was removed ▼ security
- Tool “list_passes” was removed ▼ security
- Tool “list_plans” was removed ▼ security
- Tool “list_subscriptions” was removed ▼ security
- Tool “memberful_graphql” was removed ▼ security
- Tool “memberful_query” was removed ▼ security
- Tool “update_member” was removed ▼ security
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- New tool “change_subscription_expiration”, which the server declares destructive security
- New tool “create_coupons”, which the server declares destructive security
- New tool “create_member”, which the server declares destructive security
- New tool “memberful_graphql”, which the server declares destructive security
- New tool “update_member”, which the server declares destructive security
- MCP protocol: unverified → fail ▼ functional
- Schema quality: excellent → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: pass → unverified ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- New tool “get_member” functional
- New tool “get_subscription” functional
- New tool “list_members” functional
- New tool “list_passes” functional
- New tool “list_plans” functional
- New tool “list_subscriptions” functional
- New tool “memberful_query” 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
- 31 Jul 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
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 21 Sept 2026 · Probed https://memberful.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 | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | eef534e2c3d95416138b6d5606f36466 |
| SANs: usefulapi.io, memberful.usefulapi.io, *.memberful.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 memberful.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://memberful.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://memberful.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://memberful.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://memberful.usefulapi.io/mcp |
| Authorisation server | https://memberful.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://memberful.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://memberful.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 →
change_subscription_expiration Change subscription expiration ~86
MUTATES Memberful data: change WHEN a subscription expires (extend or shorten access). expiresAt is a Unix timestamp in SECONDS (Int). Memberful GraphQL: subscriptionChangeExpirationTime(id, expiresAt).
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | integer | yes | New expiration as a Unix timestamp in SECONDS (Int, required). |
| id | string | yes | The subscription id (required). |
No output schema declared.
No examples provided.
create_coupons Create coupons ~87
MUTATES Memberful data: create one or more coupon codes for a discount. Provide the discount id (discountId) and the coupon code strings. Memberful GraphQL: createCoupons(discountId, coupons).
| Name | Type | Req | Description |
|---|---|---|---|
| codes | array | yes | Coupon code strings to create (at least one, required). |
| discountId | string | – | The discount id to attach the coupons to. |
No output schema declared.
No examples provided.
create_member Create a member ~67
MUTATES Memberful data: create a new member with an email (and optional full name). Memberful GraphQL: memberCreate(email, fullName).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The new member's email (required). | |
| fullName | string | – | The new member's full name. |
No output schema declared.
No examples provided.
get_member Get a member ~59
Fetch one Memberful member by id: profile, Stripe customer id, unrestricted-access flag, total spend, metadata, address, and their subscriptions (each with plan). Memberful GraphQL: member(id).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The member id. |
No output schema declared.
No examples provided.
get_subscription Get a subscription ~49
Fetch one subscription by id: status, activated/expires/trial timestamps, plan, member, orders, coupon. Memberful GraphQL: subscription(id).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The subscription id. |
No output schema declared.
No examples provided.
list_members List members ~188
List members (Relay connection): each edge has a cursor + node (profile, Stripe customer id, unrestricted-access flag, total spend, and their subscriptions). Paginate with `first` + `after` (pass the last edge's `cursor`); `first` defaults to 50. Set `activeOnly` to return only members with an ACTIVE membership state. For member-state filters beyond active, use memberful_query. Memberful GraphQL: members connection.
| Name | Type | Req | Description |
|---|---|---|---|
| activeOnly | boolean | – | Only return members with an ACTIVE membership state. |
| after | string | – | Cursor for the next page (the `cursor` of the last edge from a prior call). |
| before | string | – | Cursor for the previous page. |
| first | integer | – | Max members to return, from the start (page size). |
| last | integer | – | Max members to return, from the end. |
No output schema declared.
No examples provided.
list_passes List passes ~40
List all passes (Memberful dashboard 'Plans' — the access groups a member subscribes to): id, name. Memberful GraphQL: passes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_plans List plans ~42
List all plans (Memberful dashboard 'Prices'): name, interval, price (cents), for-sale flag, plan group. Memberful GraphQL: plans.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_subscriptions List subscriptions ~166
List subscriptions (Relay connection): each edge has a cursor + node (status, expires/created timestamps, plan, member). Paginate with `first` + `after` (pass the last edge's `cursor`); `first` defaults to 50. NOTE: this uses the top-level `subscriptions` connection, which is sourced from the community SDK — validate against a live account. Memberful GraphQL: subscriptions connection.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Cursor for the next page (the `cursor` of the last edge from a prior call). |
| before | string | – | Cursor for the previous page. |
| first | integer | – | Max subscriptions to return, from the start (page size). |
| last | integer | – | Max subscriptions to return, from the end. |
No output schema declared.
No examples provided.
memberful_graphql Run a GraphQL operation (query or mutation) ~82
MUTATES Memberful data (potentially): escape hatch to run an arbitrary Memberful GraphQL operation — including any mutation — against your account's /api/graphql endpoint with optional variables. Prefer memberful_query for read-only calls.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A GraphQL query or mutation document. |
| variables | object | – | Variables object for the operation. |
No output schema declared.
No examples provided.
memberful_query Run a GraphQL query (read-only) ~109
Escape hatch: run an arbitrary Memberful GraphQL QUERY (read-only) against your account's /api/graphql endpoint with optional variables. Mutations are REJECTED — use the dedicated write tools or memberful_graphql for those. Useful for fields not covered by the curated read tools (e.g. member-state filters beyond active).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A GraphQL query document (must be a query, not a mutation). |
| variables | object | – | Variables object for the query. |
No output schema declared.
No examples provided.
update_member Update a member ~106
MUTATES Memberful data: update a member's metadata (a JSON string; max 50 keys, 40-char keys, 500-char values). Only metadata is supported here; for other inline member fields use memberful_graphql. Memberful GraphQL: memberUpdate(id, metadata).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The member id (required). |
| metadata | string | – | Metadata as a JSON string (max 50 keys, 40-char keys, 500-char values). |
No output schema declared.
No examples provided.
What is the io.usefulapi/memberful MCP server?
io.usefulapi/memberful is an MCP server listed in the public MCP registry as io.usefulapi/memberful. Manage Memberful members, subscriptions, plans, passes and coupons via the GraphQL API. This page covers its hosted endpoint (https://memberful.usefulapi.io/mcp).
Is the io.usefulapi/memberful MCP server safe to use?
io.usefulapi/memberful scores 86 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/memberful MCP server expose?
io.usefulapi/memberful exposes 12 tools: get_member, list_members, get_subscription, list_subscriptions, list_plans, and 7 more. Their descriptions and schemas cost roughly 1,081 tokens of context every time the server is loaded.
Does the io.usefulapi/memberful MCP server require authentication?
Yes. io.usefulapi/memberful 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/memberful MCP server still maintained?
io.usefulapi/memberful is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.