Check an x402-paid API endpoint's trust score before paying it - live-probed, not self-reported.
Nothing to run from here
Autumn is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
18
tools declared
remote
at its publisher
—
calls last 7d
What it does
MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http autumn-mcp https://autumn.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# get_customer, list_customers, check and 15 more
Autumn costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http autumn-mcp https://autumn.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Fetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances). Autumn API: POST /v1/customers.get.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | Your unique identifier for the customer. |
| expand | array | no | Related data to expand, e.g. invoices, entities, subscriptions.plan, purchases.plan, balances.feature. |
List/filter customers with cursor pagination. Autumn API: POST /v1/customers.list. Returns { list, next_cursor }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_cursor | string | no | Pagination cursor from a prior response's next_cursor (omit / empty for first page). |
| limit | integer | no | Page size, 1-5000. Default 50. |
| plans | array | no | Filter by plan: array of { id, versions? } objects. |
| subscription_status | string | no | Filter by status: "active" or "scheduled". Defaults to both. |
| search | string | no | Search customers by id, name, or email. |
| processors | array | no | Filter by processor type: stripe, revenuecat, vercel. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer. |
| feature_id | string | yes | The ID of the feature to check. |
| entity_id | string | no | Entity id for entity-scoped balances (e.g. per-seat limits). |
| required_balance | number | no | Minimum balance required for access. Returns allowed:false if below. Defaults to 1. |
| with_preview | boolean | no | Include upgrade/upsell (paywall) info in the response when access is denied. |
List invoices with cursor pagination and optional filters. Autumn API: POST /v1/invoices.list. Returns { list, next_cursor }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | no | Filter to a single customer by id. |
| entity_id | string | no | Filter to a single entity by id (must be paired with customer_id). |
| status | array | no | Filter by invoice status: draft, open, paid, void, uncollectible. |
| processor_types | array | no | Filter by processor: stripe, revenuecat. |
| start_cursor | string | no | Pagination cursor from a prior response's next_cursor (omit / empty for first page). |
| limit | integer | no | Page size, 1-5000. Default 50. |
Fetch a single entity (e.g. a seat) belonging to a customer. Autumn API: POST /v1/entities.get.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer that owns the entity. |
| entity_id | string | yes | The ID of the entity. |
| expand | array | no | Related data to expand, e.g. invoices, entities, subscriptions.plan, purchases.plan, balances.feature. |
List a customer's entities with cursor pagination and optional filters. Autumn API: POST /v1/entities.list. Returns { list, next_cursor }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | Restrict the response to entities owned by this customer id. |
| start_cursor | string | no | Pagination cursor from a prior response's next_cursor (omit / empty for first page). |
| limit | integer | no | Page size, 1-5000. Default 50. |
| plans | array | no | Filter by plan: array of { id, versions? } objects. |
| subscription_status | string | no | Filter by status: "active" or "scheduled". Defaults to both. |
| search | string | no | Search entities by id or name. |
| processors | array | no | Filter by parent customer processor: stripe, revenuecat, vercel. |
List all features in the current environment. Autumn API: POST /v1/features.list. Returns { list }.
No parameter schema on file.
Fetch a single feature by id. Autumn API: POST /v1/features.get.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| feature_id | string | yes | The ID of the feature. |
List all plans (products) in the current environment. Autumn API: POST /v1/plans.list. Returns { list }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | no | Include eligibility info (trial availability, attach scenario) for this customer. |
| entity_id | string | no | Entity id for entity-scoped plans. |
| include_archived | boolean | no | If true, include archived plans. |
| all_versions | boolean | no | If true, include all plan versions. |
Fetch a single plan by id (optionally a specific version). Autumn API: POST /v1/plans.get.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan_id | string | yes | The ID of the plan to retrieve. |
| version | integer | no | The plan version to get. Defaults to the latest. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer to attach the plan to. |
| plan_id | string | yes | The ID of the plan. |
| entity_id | string | no | The ID of the entity to attach the plan to. |
| feature_quantities | array | no | Prepaid feature quantities: array of { feature_id, quantity?, adjustable? }. |
| version | integer | no | The version of the plan to attach. |
| customize | object | no | Optional plan overrides (price, items, licenses, free trial). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Full API path, e.g. "/v1/customers.get". Only read/preview suffixes are allowed. |
| body | object | no | JSON body object to POST (the endpoint's params). |
MUTATES Autumn billing data — fetches a customer by id, creating them if they do not exist. Autumn API: POST /v1/customers.get_or_create.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string/null | yes | Your unique identifier for the customer (null to create an anonymous customer). |
| name | string | no | Customer's name. |
| string | no | Customer's email address. | |
| fingerprint | string | no | Unique identifier to detect duplicate customers / prevent free-trial abuse. |
| metadata | object | no | Arbitrary key/value metadata for the customer. |
| stripe_id | string | no | Existing Stripe customer id, if any. |
| create_in_stripe | boolean | no | Whether to create the customer in Stripe. |
| currency | string | no | Currency to bill this customer in (e.g. usd, eur). |
| expand | array | no | Related data to expand, e.g. invoices, entities, subscriptions.plan, purchases.plan, balances.feature. |
MUTATES Autumn billing data — partially updates a customer. Only provided fields change. Autumn API: POST /v1/customers.update.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | ID of the customer to update. |
| name | string/null | no | Customer's name. |
| string/null | no | Customer's email address. | |
| fingerprint | string/null | no | Duplicate-detection fingerprint. |
| metadata | no | Arbitrary key/value metadata for the customer. | |
| stripe_id | string/null | no | Stripe customer id. |
| currency | string/null | no | Currency to bill this customer in (e.g. usd, eur). |
| new_customer_id | string | no | New id for the customer. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer. |
| feature_id | string | no | The feature to track usage for. Provide this OR event_name. |
| event_name | string | no | Event name to track usage for. Provide this OR feature_id. |
| value | number | no | Amount of usage to record. Defaults to 1. Negative values credit the balance. |
| entity_id | string | no | Entity id for entity-scoped balances. |
| properties | object | no | Additional properties to attach to the usage event. |
| timestamp | integer | no | Unix timestamp (ms) for the event. Defaults to now. |
| idempotencyKey | string | no | Optional key to dedupe retried events. |
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 }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer to attach the plan to. |
| plan_id | string | yes | The ID of the plan. |
| entity_id | string | no | The ID of the entity to attach the plan to. |
| feature_quantities | array | no | Prepaid feature quantities: array of { feature_id, quantity?, adjustable? }. |
| version | integer | no | The version of the plan to attach. |
| success_url | string | no | URL to redirect to after a successful checkout. |
| redirect_mode | string | no | Checkout redirect mode: always, if_required, or never. |
| invoice_mode | object | no | Invoice-mode configuration object (send an invoice instead of auto-charging). |
| checkout_session_params | object | no | Extra Stripe checkout session params (can carry metadata). |
| customize | object | no | Optional plan overrides (price, items, licenses, free trial). |
MUTATES Autumn billing data — creates an entity (e.g. a seat) under a customer, tied to a feature. Autumn API: POST /v1/entities.create.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer to create the entity for. |
| entity_id | string | yes | The ID of the entity. |
| feature_id | string | yes | The ID of the feature this entity is associated with. |
| name | string/null | no | The name of the entity. |
| billing_controls | object | no | Optional billing controls for the entity (spend/usage limits). |
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 }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer to open the billing portal for. |
| return_url | string | no | URL to redirect to when the back button is clicked in the portal. |
| configuration_id | string | no | Stripe billing-portal configuration id. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Autumn or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.11.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest0b23149409a31fb9cb947b85effce4a4f1bc695a321fda3f36a759417b711efc
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_customer | untrusted-input | untrusted-input: keyword "fetch" |
| list_customers | no tags | |
| check | no tags | |
| list_invoices | no tags | |
| get_entity | untrusted-input | untrusted-input: keyword "fetch" |
| list_entities | no tags | |
| list_features | no tags | |
| get_feature | untrusted-input | untrusted-input: keyword "fetch" |
| list_plans | no tags | |
| get_plan | untrusted-input | untrusted-input: keyword "fetch" |
| preview_attach | no tags | |
| autumn_request | no tags | |
| get_or_create_customer | state-write | state-write: declares destructiveHint: true |
| update_customer | state-write | state-write: declares destructiveHint: true |
| track_usage | state-write | state-write: declares destructiveHint: true |
| attach_plan | state-write | state-write: declares destructiveHint: true |
| create_entity | state-write | state-write: declares destructiveHint: true |
| open_customer_portal | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest0b23149409a31fb9
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Autumn can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.