Skip to content

Autumn MCP by usefulapi

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

MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.

18 tools: 6 can delete or cancel things, 1 change things and 11 only read.

Tools: 6 delete, 0 irreversible, 1 write, 11 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

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

Anlyon alternative

7 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 Autumn MCP by usefulapi can do

The Autumn MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (6 tools: autumn_get_or_create_customer, autumn_update_customer, autumn_track_usage, autumn_attach_plan and 2 more) and create or change data (1 tool: autumn_request). 11 tools only read.

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

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

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.

18 tools

Deletes or cancels 6Claude Code: deny
  • autumn_attach_planMUTATES Autumn billing data — attaches (subscribes) a plan to a customer; may create an invoice / return a payment URL.No findings

    Why it is in this group

    • The name "autumn_attach_plan" says "attach": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    MUTATES Autumn billing data — attaches (subscribes) a plan to a customer; may create an invoice / return a payment URL. Autumn API: POST /v1/billing.attach. Returns { customer_id, invoice, payment_url, required_action }.

    Annotations the server declares

    • title: Attach a plan
    • destructiveHint: true
  • autumn_create_entityMUTATES Autumn billing data — creates an entity (e.g.No findings

    Why it is in this group

    • The name "autumn_create_entity" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    MUTATES Autumn billing data — creates an entity (e.g. a seat) under a customer, tied to a feature. Autumn API: POST /v1/entities.create.

    Annotations the server declares

    • title: Create an entity
    • destructiveHint: true
  • autumn_get_or_create_customerMUTATES Autumn billing data — fetches a customer by id, creating them if they do not exist.1 finding

    Why it is in this group

    • The name "autumn_get_or_create_customer" says "get": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Warn

      The server marks "autumn_get_or_create_customer" destructive (destructiveHint: true), and its name says "get", a word for reading.

      Matched text

      annotations: {"destructiveHint":true}; The name "autumn_get_or_create_customer" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    MUTATES Autumn billing data — fetches a customer by id, creating them if they do not exist. Autumn API: POST /v1/customers.get_or_create.

    Annotations the server declares

    • title: Get or create a customer
    • destructiveHint: true
  • autumn_open_customer_portalMUTATES Autumn billing data — creates a Stripe billing-portal session for a customer to manage their subscription.No findings

    Why it is in this group

    • The name "autumn_open_customer_portal" says "open": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    MUTATES Autumn billing data — creates a Stripe billing-portal session for a customer to manage their subscription. Autumn API: POST /v1/billing.open_customer_portal. Returns { customer_id, url }.

    Annotations the server declares

    • title: Open customer billing portal
    • destructiveHint: true
  • autumn_track_usageMUTATES Autumn billing data — records a usage event (deducts/credits a feature balance).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 Autumn billing data — records a usage event (deducts/credits a feature balance). Provide EITHER feature_id OR event_name. Autumn API: POST /v1/balances.track.

    Annotations the server declares

    • title: Track usage
    • destructiveHint: true
  • autumn_update_customerMUTATES Autumn billing data — partially updates a customer.No findings

    Why it is in this group

    • The name "autumn_update_customer" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    MUTATES Autumn billing data — partially updates a customer. Only provided fields change. Autumn API: POST /v1/customers.update.

    Annotations the server declares

    • title: Update a customer
    • destructiveHint: true
Changes things 1Claude Code: ask
  • autumn_requestPower-user escape hatch: POST to any Autumn read/preview endpoint not wrapped by a dedicated tool.1 finding

    Why it is in this group

    • The name "autumn_request" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "autumn_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The name "autumn_request" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Power-user escape hatch: POST to any Autumn read/preview endpoint not wrapped by a dedicated tool. READ-ONLY — the path is validated to only allow .get / .list / .check / .preview_* actions; write actions are rejected. Autumn API: POST {path}.

    Annotations the server declares

    • title: Raw read request
    • readOnlyHint: true
Only reads 11Show 11 read-only tools
  • autumn_checkREAD-ONLY entitlement check: does a customer have access to (or enough balance of) a feature?No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    READ-ONLY entitlement check: does a customer have access to (or enough balance of) a feature? Autumn API: POST /v1/balances.check. This tool never records usage — it does not expose send_event or lock.

    Annotations the server declares

    • title: Check feature access / balance
    • readOnlyHint: true
  • autumn_get_customerFetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances).No findings

    Why it is in this group

    • The name "autumn_get_customer" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances). Autumn API: POST /v1/customers.get.

    Annotations the server declares

    • title: Get a customer
    • readOnlyHint: true
  • autumn_get_entityFetch a single entity (e.g.No findings

    Why it is in this group

    • The name "autumn_get_entity" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single entity (e.g. a seat) belonging to a customer. Autumn API: POST /v1/entities.get.

    Annotations the server declares

    • title: Get an entity
    • readOnlyHint: true
  • autumn_get_featureFetch a single feature by id.No findings

    Why it is in this group

    • The name "autumn_get_feature" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single feature by id. Autumn API: POST /v1/features.get.

    Annotations the server declares

    • title: Get a feature
    • readOnlyHint: true
  • autumn_get_planFetch a single plan by id (optionally a specific version).No findings

    Why it is in this group

    • The name "autumn_get_plan" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single plan by id (optionally a specific version). Autumn API: POST /v1/plans.get.

    Annotations the server declares

    • title: Get a plan
    • readOnlyHint: true
  • autumn_list_customersList/filter customers with cursor pagination.No findings

    Why it is in this group

    • The name "autumn_list_customers" says "list": a word for reading.
    Description, as the server wrote it
    List/filter customers with cursor pagination. Autumn API: POST /v1/customers.list. Returns { list, next_cursor }.

    Annotations the server declares

    • title: List customers
    • readOnlyHint: true
  • autumn_list_entitiesList a customer's entities with cursor pagination and optional filters.No findings

    Why it is in this group

    • The name "autumn_list_entities" says "list": a word for reading.
    Description, as the server wrote it
    List a customer's entities with cursor pagination and optional filters. Autumn API: POST /v1/entities.list. Returns { list, next_cursor }.

    Annotations the server declares

    • title: List entities
    • readOnlyHint: true
  • autumn_list_featuresList all features in the current environment.No findings

    Why it is in this group

    • The name "autumn_list_features" says "list": a word for reading.
    Description, as the server wrote it
    List all features in the current environment. Autumn API: POST /v1/features.list. Returns { list }.

    Annotations the server declares

    • title: List features
    • readOnlyHint: true
  • autumn_list_invoicesList invoices with cursor pagination and optional filters.No findings

    Why it is in this group

    • The name "autumn_list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices with cursor pagination and optional filters. Autumn API: POST /v1/invoices.list. Returns { list, next_cursor }.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • autumn_list_plansList all plans (products) in the current environment.No findings

    Why it is in this group

    • The name "autumn_list_plans" says "list": a word for reading.
    Description, as the server wrote it
    List all plans (products) in the current environment. Autumn API: POST /v1/plans.list. Returns { list }.

    Annotations the server declares

    • title: List plans
    • readOnlyHint: true
  • autumn_preview_attachPreview the cost/effect of attaching a plan to a customer WITHOUT charging or changing anything.No findings

    Why it is in this group

    • The name "autumn_preview_attach" says "preview": a word for reading.
    Description, as the server wrote it
    Preview the cost/effect of attaching a plan to a customer WITHOUT charging or changing anything. Read-only. Autumn API: POST /v1/billing.preview_attach.

    Annotations the server declares

    • title: Preview attaching a plan
    • 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:32 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: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://autumn.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://autumn.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.

2 warn
  • The server marks "autumn_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The name "autumn_request" says "request": a word for a change.

    What this check looks for
  • The server marks "autumn_get_or_create_customer" destructive (destructiveHint: true), and its name says "get", a word for reading.

    Matched text

    annotations: {"destructiveHint":true}; The name "autumn_get_or_create_customer" says "get": a word for reading.

    What this check looks for

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: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://autumn.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://autumn.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. Tools17 added, 17 removed.+17 added−17 removedView diff

Install

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

claude mcp add --transport http autumn https://autumn.usefulapi.io/mcp
claude mcp add --transport http autumn https://autumn.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__autumn__autumn_get_customer",
      "mcp__autumn__autumn_list_customers",
      "mcp__autumn__autumn_check",
      "mcp__autumn__autumn_list_invoices",
      "mcp__autumn__autumn_get_entity",
      "mcp__autumn__autumn_list_entities",
      "mcp__autumn__autumn_list_features",
      "mcp__autumn__autumn_get_feature",
      "mcp__autumn__autumn_list_plans",
      "mcp__autumn__autumn_get_plan",
      "mcp__autumn__autumn_preview_attach"
    ],
    "ask": [
      "mcp__autumn__autumn_request"
    ],
    "deny": [
      "mcp__autumn__autumn_get_or_create_customer",
      "mcp__autumn__autumn_update_customer",
      "mcp__autumn__autumn_track_usage",
      "mcp__autumn__autumn_attach_plan",
      "mcp__autumn__autumn_create_entity",
      "mcp__autumn__autumn_open_customer_portal"
    ]
  }
}

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 autumn. 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/autumn/verify?hash=85ba90b1b1400986019770366d0f04bab906dc6342035ab9aeeef60d067537bf" | jq -e '.changed == false'

Pinned hash 85ba90b1b140, 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/autumn/changes.xml

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

Badge

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

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

Autumn MCP by usefulapi: questions and answers

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

Is the Autumn MCP by usefulapi safe?

No scan can promise that. What its definitions show: 18 tools, 7 of which can change, send or delete something, and 2 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 Autumn MCP by usefulapi delete data?

Yes. 6 tools can delete, cancel or revoke something: autumn_get_or_create_customer, autumn_update_customer, autumn_track_usage, autumn_attach_plan, autumn_create_entity and autumn_open_customer_portal.

Can the Autumn 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 Autumn MCP by usefulapi have?

18 tools: 6 destructive, 1 write, 11 read. autumn_get_or_create_customer, autumn_update_customer, autumn_track_usage, autumn_attach_plan, autumn_create_entity, autumn_open_customer_portal, autumn_request, autumn_get_customer and 10 more.

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

Its remote endpoint did not answer the last anonymous look.

Does the Autumn 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 Autumn 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.