io.usefulapi/autumn
REMOTE · AUTUMN.USEFULAPI.IO · SCANNED SEP 20
MCP server for Autumn — read customers, plans, balances & invoices; track usage and attach plans.
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 Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2301 tokens (~127/item across 18 items; 18 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 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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/autumn MCP server?
io.usefulapi/autumn is a hosted endpoint at https://autumn.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 · autumn.usefulapi.io
claude mcp add --transport http io-usefulapi-autumn 'https://autumn.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-autumn": {
"url": "https://autumn.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-autumn": {
"type": "http",
"url": "https://autumn.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-autumn] url = "https://autumn.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-autumn": {
"type": "remote",
"url": "https://autumn.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-autumn --url 'https://autumn.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-autumn:
url: "https://autumn.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-autumn": {
"Transport": "http",
"Url": "https://autumn.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-autumn -t streamable-http -u 'https://autumn.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-autumn": {
"type": "http",
"url": "https://autumn.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.
- 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
- 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
- 30 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
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 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 20 Sept 2026 · Probed https://autumn.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 | 21782af7bd17410e0e8c403560c80be4 |
| SANs: usefulapi.io, autumn.usefulapi.io, *.autumn.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 autumn.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://autumn.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://autumn.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://autumn.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://autumn.usefulapi.io/mcp |
| Authorisation server | https://autumn.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://autumn.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://autumn.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 →
attach_plan Attach a plan ~242
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_session_params | object | – | Extra Stripe checkout session params (can carry metadata). |
| customer_id | string | yes | The ID of the customer to attach the plan to. |
| customize | object | – | Optional plan overrides (price, items, licenses, free trial). |
| entity_id | string | – | The ID of the entity to attach the plan to. |
| feature_quantities | array | – | Prepaid feature quantities: array of { feature_id, quantity?, adjustable? }. |
| invoice_mode | object | – | Invoice-mode configuration object (send an invoice instead of auto-charging). |
| plan_id | string | yes | The ID of the plan. |
| redirect_mode | string | – | Checkout redirect mode: always, if_required, or never. |
| success_url | string | – | URL to redirect to after a successful checkout. |
| version | integer | – | The version of the plan to attach. |
No output schema declared.
No examples provided.
autumn_request Raw read request ~111
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | JSON body object to POST (the endpoint's params). |
| path | string | yes | Full API path, e.g. "/v1/customers.get". Only read/preview suffixes are allowed. |
No output schema declared.
No examples provided.
check Check feature access / balance ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer. |
| entity_id | string | – | Entity id for entity-scoped balances (e.g. per-seat limits). |
| feature_id | string | yes | The ID of the feature to check. |
| required_balance | number | – | Minimum balance required for access. Returns allowed:false if below. Defaults to 1. |
| with_preview | boolean | – | Include upgrade/upsell (paywall) info in the response when access is denied. |
No output schema declared.
No examples provided.
create_entity Create an entity ~122
MUTATES Autumn billing data — creates an entity (e.g. a seat) under a customer, tied to a feature. Autumn API: POST /v1/entities.create.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_controls | object | – | Optional billing controls for the entity (spend/usage limits). |
| 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 | – | – | The name of the entity. |
No output schema declared.
No examples provided.
get_customer Get a customer ~82
Fetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances). Autumn API: POST /v1/customers.get.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | Your unique identifier for the customer. |
| expand | array | – | Related data to expand, e.g. invoices, entities, subscriptions.plan, purchases.plan, balances.feature. |
No output schema declared.
No examples provided.
get_entity Get an entity ~91
Fetch a single entity (e.g. a seat) belonging to a customer. Autumn API: POST /v1/entities.get.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer that owns the entity. |
| entity_id | string | yes | The ID of the entity. |
| expand | array | – | Related data to expand, e.g. invoices, entities, subscriptions.plan, purchases.plan, balances.feature. |
No output schema declared.
No examples provided.
get_feature Get a feature ~38
Fetch a single feature by id. Autumn API: POST /v1/features.get.
| Name | Type | Req | Description |
|---|---|---|---|
| feature_id | string | yes | The ID of the feature. |
No output schema declared.
No examples provided.
get_or_create_customer Get or create a customer ~197
MUTATES Autumn billing data — fetches a customer by id, creating them if they do not exist. Autumn API: POST /v1/customers.get_or_create.
| Name | Type | Req | Description |
|---|---|---|---|
| create_in_stripe | boolean | – | Whether to create the customer in Stripe. |
| currency | string | – | Currency to bill this customer in (e.g. usd, eur). |
| customer_id | – | yes | Your unique identifier for the customer (null to create an anonymous customer). |
| string | – | Customer's email address. | |
| expand | array | – | Related data to expand, e.g. invoices, entities, subscriptions.plan, purchases.plan, balances.feature. |
| fingerprint | string | – | Unique identifier to detect duplicate customers / prevent free-trial abuse. |
| metadata | object | – | Arbitrary key/value metadata for the customer. |
| name | string | – | Customer's name. |
| stripe_id | string | – | Existing Stripe customer id, if any. |
No output schema declared.
No examples provided.
get_plan Get a plan ~64
Fetch a single plan by id (optionally a specific version). Autumn API: POST /v1/plans.get.
| Name | Type | Req | Description |
|---|---|---|---|
| plan_id | string | yes | The ID of the plan to retrieve. |
| version | integer | – | The plan version to get. Defaults to the latest. |
No output schema declared.
No examples provided.
list_customers List customers ~157
List/filter customers with cursor pagination. Autumn API: POST /v1/customers.list. Returns { list, next_cursor }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size, 1-5000. Default 50. |
| plans | array | – | Filter by plan: array of { id, versions? } objects. |
| processors | array | – | Filter by processor type: stripe, revenuecat, vercel. |
| search | string | – | Search customers by id, name, or email. |
| start_cursor | string | – | Pagination cursor from a prior response's `next_cursor` (omit / empty for first page). |
| subscription_status | string | – | Filter by status: "active" or "scheduled". Defaults to both. |
No output schema declared.
No examples provided.
list_entities List entities ~176
List a customer's entities with cursor pagination and optional filters. Autumn API: POST /v1/entities.list. Returns { list, next_cursor }.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | Restrict the response to entities owned by this customer id. |
| limit | integer | – | Page size, 1-5000. Default 50. |
| plans | array | – | Filter by plan: array of { id, versions? } objects. |
| processors | array | – | Filter by parent customer processor: stripe, revenuecat, vercel. |
| search | string | – | Search entities by id or name. |
| start_cursor | string | – | Pagination cursor from a prior response's `next_cursor` (omit / empty for first page). |
| subscription_status | string | – | Filter by status: "active" or "scheduled". Defaults to both. |
No output schema declared.
No examples provided.
list_features List features ~31
List all features in the current environment. Autumn API: POST /v1/features.list. Returns { list }.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_invoices List invoices ~158
List invoices with cursor pagination and optional filters. Autumn API: POST /v1/invoices.list. Returns { list, next_cursor }.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Filter to a single customer by id. |
| entity_id | string | – | Filter to a single entity by id (must be paired with customer_id). |
| limit | integer | – | Page size, 1-5000. Default 50. |
| processor_types | array | – | Filter by processor: stripe, revenuecat. |
| start_cursor | string | – | Pagination cursor from a prior response's `next_cursor` (omit / empty for first page). |
| status | array | – | Filter by invoice status: draft, open, paid, void, uncollectible. |
No output schema declared.
No examples provided.
list_plans List plans ~102
List all plans (products) in the current environment. Autumn API: POST /v1/plans.list. Returns { list }.
| Name | Type | Req | Description |
|---|---|---|---|
| all_versions | boolean | – | If true, include all plan versions. |
| customer_id | string | – | Include eligibility info (trial availability, attach scenario) for this customer. |
| entity_id | string | – | Entity id for entity-scoped plans. |
| include_archived | boolean | – | If true, include archived plans. |
No output schema declared.
No examples provided.
open_customer_portal Open customer billing portal ~107
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| configuration_id | string | – | Stripe billing-portal configuration id. |
| customer_id | string | yes | The ID of the customer to open the billing portal for. |
| return_url | string | – | URL to redirect to when the back button is clicked in the portal. |
No output schema declared.
No examples provided.
preview_attach Preview attaching a plan ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer to attach the plan to. |
| customize | object | – | Optional plan overrides (price, items, licenses, free trial). |
| entity_id | string | – | The ID of the entity to attach the plan to. |
| feature_quantities | array | – | Prepaid feature quantities: array of { feature_id, quantity?, adjustable? }. |
| plan_id | string | yes | The ID of the plan. |
| version | integer | – | The version of the plan to attach. |
No output schema declared.
No examples provided.
track_usage Track usage ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The ID of the customer. |
| entity_id | string | – | Entity id for entity-scoped balances. |
| event_name | string | – | Event name to track usage for. Provide this OR feature_id. |
| feature_id | string | – | The feature to track usage for. Provide this OR event_name. |
| idempotencyKey | string | – | Optional key to dedupe retried events. |
| properties | object | – | Additional properties to attach to the usage event. |
| timestamp | integer | – | Unix timestamp (ms) for the event. Defaults to now. |
| value | number | – | Amount of usage to record. Defaults to 1. Negative values credit the balance. |
No output schema declared.
No examples provided.
update_customer Update a customer ~129
MUTATES Autumn billing data — partially updates a customer. Only provided fields change. Autumn API: POST /v1/customers.update.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | – | – | Currency to bill this customer in (e.g. usd, eur). |
| customer_id | string | yes | ID of the customer to update. |
| – | – | Customer's email address. | |
| fingerprint | – | – | Duplicate-detection fingerprint. |
| metadata | – | – | Arbitrary key/value metadata for the customer. |
| name | – | – | Customer's name. |
| new_customer_id | string | – | New id for the customer. |
| stripe_id | – | – | Stripe customer id. |
No output schema declared.
No examples provided.
What is the io.usefulapi/autumn MCP server?
io.usefulapi/autumn is an MCP server listed in the public MCP registry as io.usefulapi/autumn. MCP server for Autumn, read customers, plans, balances & invoices; track usage and attach plans. This page covers its hosted endpoint (https://autumn.usefulapi.io/mcp).
Is the io.usefulapi/autumn MCP server safe to use?
io.usefulapi/autumn 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/autumn MCP server expose?
io.usefulapi/autumn exposes 18 tools: get_customer, list_customers, check, list_invoices, get_entity, and 13 more. Their descriptions and schemas cost roughly 2,301 tokens of context every time the server is loaded.
Does the io.usefulapi/autumn MCP server require authentication?
Yes. io.usefulapi/autumn 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/autumn MCP server still maintained?
io.usefulapi/autumn 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.