Skip to content

Memberful MCP by usefulapi

io.usefulapi/memberfulusefulapi.iostreamable-httpv1.41.4Scanned

Manage Memberful members, subscriptions, plans, passes and coupons via the GraphQL API.

12 tools: 5 can delete or cancel things and 7 only read.

Tools: 5 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Memberful MCP by usefulapi can do

The Memberful MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (5 tools: memberful_create_member, memberful_update_member, memberful_change_subscription_expiration, memberful_create_coupons and 1 more). 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Oct 25, 2026, version 1.41.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Deletes or cancels 5Claude Code: deny
  • memberful_change_subscription_expirationMUTATES Memberful data: change WHEN a subscription expires (extend or shorten access).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Change subscription expiration
    • destructiveHint: true
  • memberful_create_couponsMUTATES Memberful data: create one or more coupon codes for a discount.No findings

    Why it is in this group

    • The name "memberful_create_coupons" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Create coupons
    • destructiveHint: true
  • memberful_create_memberMUTATES Memberful data: create a new member with an email (and optional full name).No findings

    Why it is in this group

    • The name "memberful_create_member" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    MUTATES Memberful data: create a new member with an email (and optional full name). Memberful GraphQL: memberCreate(email, fullName).

    Annotations the server declares

    • title: Create a member
    • destructiveHint: true
  • memberful_graphqlMUTATES Memberful data (potentially): escape hatch to run an arbitrary Memberful GraphQL operation — including any mutation — against your account's /api/graphql endpoint with opti…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Run a GraphQL operation (query or mutation)
    • destructiveHint: true
  • memberful_update_memberMUTATES Memberful data: update a member's metadata (a JSON string; max 50 keys, 40-char keys, 500-char values).No findings

    Why it is in this group

    • The name "memberful_update_member" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Update a member
    • destructiveHint: true
Only reads 7Show 7 read-only tools
  • memberful_get_memberFetch one Memberful member by id: profile, Stripe customer id, unrestricted-access flag, total spend, metadata, address, and their subscriptions (each with plan).No findings

    Why it is in this group

    • The name "memberful_get_member" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Get a member
    • readOnlyHint: true
  • memberful_get_subscriptionFetch one subscription by id: status, activated/expires/trial timestamps, plan, member, orders, coupon.No findings

    Why it is in this group

    • The name "memberful_get_subscription" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one subscription by id: status, activated/expires/trial timestamps, plan, member, orders, coupon. Memberful GraphQL: subscription(id).

    Annotations the server declares

    • title: Get a subscription
    • readOnlyHint: true
  • memberful_list_membersList members (Relay connection): each edge has a cursor + node (profile, Stripe customer id, unrestricted-access flag, total spend, and their subscriptions).No findings

    Why it is in this group

    • The name "memberful_list_members" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List members
    • readOnlyHint: true
  • memberful_list_passesList all passes (Memberful dashboard 'Plans' — the access groups a member subscribes to): id, name.No findings

    Why it is in this group

    • The name "memberful_list_passes" says "list": a word for reading.
    Description, as the server wrote it
    List all passes (Memberful dashboard 'Plans' — the access groups a member subscribes to): id, name. Memberful GraphQL: passes.

    Annotations the server declares

    • title: List passes
    • readOnlyHint: true
  • memberful_list_plansList all plans (Memberful dashboard 'Prices'): name, interval, price (cents), for-sale flag, plan group.No findings

    Why it is in this group

    • The name "memberful_list_plans" says "list": a word for reading.
    Description, as the server wrote it
    List all plans (Memberful dashboard 'Prices'): name, interval, price (cents), for-sale flag, plan group. Memberful GraphQL: plans.

    Annotations the server declares

    • title: List plans
    • readOnlyHint: true
  • memberful_list_subscriptionsList subscriptions (Relay connection): each edge has a cursor + node (status, expires/created timestamps, plan, member).No findings

    Why it is in this group

    • The name "memberful_list_subscriptions" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List subscriptions
    • readOnlyHint: true
  • memberful_queryEscape hatch: run an arbitrary Memberful GraphQL QUERY (read-only) against your account's /api/graphql endpoint with optional variables.No findings

    Why it is in this group

    • The name "memberful_query" says "query": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Run a GraphQL query (read-only)
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://memberful.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://memberful.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://memberful.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://memberful.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. Tools10 added, 10 removed.+10 added−10 removedView diff

Install

Pinned to version 1.41.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http memberful https://memberful.usefulapi.io/mcp
claude mcp add --transport http memberful https://memberful.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__memberful__memberful_get_member",
      "mcp__memberful__memberful_list_members",
      "mcp__memberful__memberful_get_subscription",
      "mcp__memberful__memberful_list_subscriptions",
      "mcp__memberful__memberful_list_plans",
      "mcp__memberful__memberful_list_passes",
      "mcp__memberful__memberful_query"
    ],
    "ask": [],
    "deny": [
      "mcp__memberful__memberful_create_member",
      "mcp__memberful__memberful_update_member",
      "mcp__memberful__memberful_change_subscription_expiration",
      "mcp__memberful__memberful_create_coupons",
      "mcp__memberful__memberful_graphql"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as memberful. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/memberful/verify?hash=dbab3f4466df75ce1fa4a8cdf60909f15bed8145b5dfcf7a88fb178d5dc7f8fe" | jq -e '.changed == false'

Pinned hash dbab3f4466df, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/memberful/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/memberful
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/memberful.svg)](https://radar.anlyon.com/servers/io.usefulapi/memberful)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Memberful MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Memberful MCP by usefulapi safe?

No scan can promise that. What its definitions show: 12 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Memberful MCP by usefulapi delete data?

Yes. 5 tools can delete, cancel or revoke something: memberful_create_member, memberful_update_member, memberful_change_subscription_expiration, memberful_create_coupons and memberful_graphql.

Can the Memberful MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Memberful MCP by usefulapi have?

12 tools: 5 destructive, 7 read. memberful_create_member, memberful_update_member, memberful_change_subscription_expiration, memberful_create_coupons, memberful_graphql, memberful_get_member, memberful_list_members, memberful_get_subscription and 4 more.

Does the Memberful MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Memberful MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Memberful MCP by usefulapi changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 23, 2026. Every change is on this page and in its Atom feed.