Amberflo MCP by usefulapi
io.usefulapi/amberflousefulapi.iostreamable-httpv1.40.4Scanned
Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid.
14 tools: 3 can delete or cancel things and 11 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
3 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 Amberflo MCP by usefulapi can do
The Amberflo MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (3 tools: amberflo_create_customer, amberflo_assign_customer_plan and amberflo_ingest_usage). 11 tools only read.
1 tool reads private data (amberflo_list_customers); 1 tool brings in text other people can write (amberflo_list_customers).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.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.
14 tools
Deletes or cancels 3Claude Code: deny
amberflo_assign_customer_planWRITE: assign/attach a pricing product plan to a customer — this changes what the customer is billed.No findings
Why it is in this group
- The name "amberflo_assign_customer_plan" says "assign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: assign/attach a pricing product plan to a customer — this changes what the customer is billed. API: POST /payments/pricing/amberflo/customer-pricing.
Annotations the server declares
- title: Assign customer plan
- destructiveHint: true
amberflo_create_customerWRITE: create/register a new customer in Amberflo (id + name required; optional email, enabled flag, and traits).No findings
Why it is in this group
- The name "amberflo_create_customer" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: create/register a new customer in Amberflo (id + name required; optional email, enabled flag, and traits). Optionally auto-create the customer in Stripe. API: POST /customers/.
Annotations the server declares
- title: Create customer
- destructiveHint: true
amberflo_ingest_usageWRITE: record/ingest a single usage meter event (writes billable usage data) to the Amberflo ingestion host.No findings
Why it is in this group
- The description's first verb is "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it WRITE: record/ingest a single usage meter event (writes billable usage data) to the Amberflo ingestion host. API: POST /ingest/ on the ingest base URL.
Annotations the server declares
- title: Ingest usage event
- destructiveHint: true
Only reads 11Show 11 read-only tools
amberflo_explain_usageExplain/drill into the raw meter events behind a meter's usage over a time range — useful to debug why a number looks off.No findings
Why it is in this group
- The name "amberflo_explain_usage" says "explain": a word for reading.
Description, as the server wrote it Explain/drill into the raw meter events behind a meter's usage over a time range — useful to debug why a number looks off. API: POST /usage/explain.
Annotations the server declares
- title: Explain usage
- readOnlyHint: true
amberflo_get_all_usageGet total usage across all meters over a time range, optionally grouped by customer or filtered to one customer.No findings
Why it is in this group
- The name "amberflo_get_all_usage" says "get": a word for reading.
Description, as the server wrote it Get total usage across all meters over a time range, optionally grouped by customer or filtered to one customer. API: GET /usage/all.
Annotations the server declares
- title: Get all usage
- readOnlyHint: true
amberflo_get_customerFetch a single customer by its Amberflo customerId.No findings
Why it is in this group
- The name "amberflo_get_customer" says "get": a word for reading.
Description, as the server wrote it Fetch a single customer by its Amberflo customerId. API: GET /customers/?customerId=<id>.
Annotations the server declares
- title: Get a customer
- readOnlyHint: true
amberflo_get_customer_invoiceGet a single customer invoice: the CURRENT open invoice (latest=true, default) or a SPECIFIC past invoice by product_plan_id + year + month + day.No findings
Why it is in this group
- The name "amberflo_get_customer_invoice" says "get": a word for reading.
Description, as the server wrote it Get a single customer invoice: the CURRENT open invoice (latest=true, default) or a SPECIFIC past invoice by product_plan_id + year + month + day. API: GET /payments/billing/customer-product-invoice.
Annotations the server declares
- title: Get customer invoice
- readOnlyHint: true
amberflo_get_customer_planGet a customer's LATEST assigned product plan (pricing).No findings
Why it is in this group
- The name "amberflo_get_customer_plan" says "get": a word for reading.
Description, as the server wrote it Get a customer's LATEST assigned product plan (pricing). API: GET /payments/pricing/amberflo/customer-pricing?CustomerId=<id>.
Annotations the server declares
- title: Get customer plan
- readOnlyHint: true
amberflo_get_usageQuery aggregated usage for a single meter over a time range, optionally grouped/filtered.No findings
Why it is in this group
- The name "amberflo_get_usage" says "get": a word for reading.
Description, as the server wrote it Query aggregated usage for a single meter over a time range, optionally grouped/filtered. API: POST /usage/.
Annotations the server declares
- title: Query usage for a meter
- readOnlyHint: true
amberflo_list_customer_invoicesList all invoices for a customer (optionally for a specific product), with payment status.No findings
Why it is in this group
- The name "amberflo_list_customer_invoices" says "list": a word for reading.
Description, as the server wrote it List all invoices for a customer (optionally for a specific product), with payment status. API: GET /payments/billing/customer-product-invoice/all.
Annotations the server declares
- title: List customer invoices
- readOnlyHint: true
amberflo_list_customer_plan_historyList the full history of product plans assigned to a customer over time.No findings
Why it is in this group
- The name "amberflo_list_customer_plan_history" says "list": a word for reading.
Description, as the server wrote it List the full history of product plans assigned to a customer over time. API: GET /payments/pricing/amberflo/customer-pricing/list?CustomerId=<id>.
Annotations the server declares
- title: List customer plan history
- readOnlyHint: true
amberflo_list_customersList all customers registered in your Amberflo account (id, name, email, traits, enabled).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "amberflo_list_customers" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it List all customers registered in your Amberflo account (id, name, email, traits, enabled). Good first call to discover customer ids. API: GET /customers/.
Annotations the server declares
- title: List customers
- readOnlyHint: true
amberflo_list_metersList all meter definitions in your account (id, meterApiName, label, meterType, aggregation, etc.).No findings
Why it is in this group
- The name "amberflo_list_meters" says "list": a word for reading.
Description, as the server wrote it List all meter definitions in your account (id, meterApiName, label, meterType, aggregation, etc.). Use meterApiName values here as inputs to usage tools. API: GET /meters.
Annotations the server declares
- title: List meters
- readOnlyHint: true
amberflo_list_prepaid_ordersList a customer's active prepaid credit orders for a product.No findings
Why it is in this group
- The name "amberflo_list_prepaid_orders" says "list": a word for reading.
Description, as the server wrote it List a customer's active prepaid credit orders for a product. API: GET /payments/pricing/amberflo/customer-prepaid/list?CustomerId=<id>&ProductId=<pid>.
Annotations the server declares
- title: List prepaid orders
- 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 outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- 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.
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
- 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: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://amberflo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://amberflo.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.
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: 3 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://amberflo.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://amberflo.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http amberflo https://amberflo.usefulapi.io/mcpclaude mcp add --transport http amberflo https://amberflo.usefulapi.io/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__amberflo__amberflo_list_customers",
"mcp__amberflo__amberflo_get_customer",
"mcp__amberflo__amberflo_list_meters",
"mcp__amberflo__amberflo_get_usage",
"mcp__amberflo__amberflo_get_all_usage",
"mcp__amberflo__amberflo_explain_usage",
"mcp__amberflo__amberflo_get_customer_plan",
"mcp__amberflo__amberflo_list_customer_plan_history",
"mcp__amberflo__amberflo_list_customer_invoices",
"mcp__amberflo__amberflo_get_customer_invoice",
"mcp__amberflo__amberflo_list_prepaid_orders"
],
"ask": [],
"deny": [
"mcp__amberflo__amberflo_create_customer",
"mcp__amberflo__amberflo_assign_customer_plan",
"mcp__amberflo__amberflo_ingest_usage"
]
}
}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 amberflo. Review it before you use it.
Capability tags behind 1 rule
- mcp__amberflo__amberflo_list_customers private-data, untrusted-input
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/amberflo/verify?hash=2e8195cd220dfab33a6851d24a981f83b1412e0847cffd536b45b5d05a0d23a9" | jq -e '.changed == false'Pinned hash 2e8195cd220d, 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/amberflo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/amberflo)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Amberflo MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Amberflo MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 14 tools, 3 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 Amberflo MCP by usefulapi delete data?
- Yes. 3 tools can delete, cancel or revoke something: amberflo_create_customer, amberflo_assign_customer_plan and amberflo_ingest_usage.
Can the Amberflo 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 Amberflo MCP by usefulapi have?
- 14 tools: 3 destructive, 11 read. amberflo_create_customer, amberflo_assign_customer_plan, amberflo_ingest_usage, amberflo_list_customers, amberflo_get_customer, amberflo_list_meters, amberflo_get_usage, amberflo_get_all_usage and 6 more.
Does the Amberflo MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Amberflo 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 Amberflo MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.