autumn

Tools

18 tools: 12 read-only, 0 change data, 6 high risk (delete, pay, send or run code).

No tool name points to sending messages.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 4,294 tokens of tool definitions and a 327 ms handshake.

• high riskget_or_create_customerMUTATES Autumn billing data - fetches a customer by id, creating them if they do not exist. Autumn API: POST /v1/customers.get_or_create.
• high riskupdate_customerMUTATES Autumn billing data - partially updates a customer. Only provided fields change. Autumn API: POST /v1/customers.update.
• high risktrack_usageMUTATES 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.
• high riskattach_planMUTATES 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 }.
• high riskcreate_entityMUTATES Autumn billing data - creates an entity (e.g. a seat) under a customer, tied to a feature. Autumn API: POST /v1/entities.create.
• high riskopen_customer_portalMUTATES 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 }.
• read-onlyget_customerFetch a single Autumn customer by id, optionally expanding related data (invoices, entities, subscriptions, balances). Autumn API: POST /v1/customers.get.
• read-onlylist_customersList/filter customers with cursor pagination. Autumn API: POST /v1/customers.list. Returns { list, next_cursor }.
• read-onlycheckREAD-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.
• read-onlylist_invoicesList invoices with cursor pagination and optional filters. Autumn API: POST /v1/invoices.list. Returns { list, next_cursor }.
• read-onlyget_entityFetch a single entity (e.g. a seat) belonging to a customer. Autumn API: POST /v1/entities.get.
• read-onlylist_entitiesList a customer's entities with cursor pagination and optional filters. Autumn API: POST /v1/entities.list. Returns { list, next_cursor }.
• read-onlylist_featuresList all features in the current environment. Autumn API: POST /v1/features.list. Returns { list }.
• read-onlyget_featureFetch a single feature by id. Autumn API: POST /v1/features.get.
• read-onlylist_plansList all plans (products) in the current environment. Autumn API: POST /v1/plans.list. Returns { list }.
• read-onlyget_planFetch a single plan by id (optionally a specific version). Autumn API: POST /v1/plans.get.
• read-onlypreview_attachPreview the cost/effect of attaching a plan to a customer WITHOUT charging or changing anything. Read-only. Autumn API: POST /v1/billing.preview_attach.
• read-onlyautumn_requestPower-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}.

Levels are read from each tool's name, description and annotations. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-03, 327 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-042026-10-03

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in CRM and sales, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/autumn.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/autumn.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/autumn.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/autumn.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.