Check an x402-paid API endpoint's trust score before paying it - live-probed, not self-reported.
Nothing to run from here
Amberflo 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
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http amberflo-mcp https://amberflo.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# amberflo_list_customers, amberflo_get_customer, amberflo_list_meters and 11 more
Amberflo 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 amberflo-mcp https://amberflo.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
14 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.
List all customers registered in your Amberflo account (id, name, email, traits, enabled). Good first call to discover customer ids. API: GET /customers/.
No parameter schema on file.
Fetch a single customer by its Amberflo customerId. API: GET /customers/?customerId=<id>.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId to fetch. |
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.
No parameter schema on file.
Query aggregated usage for a single meter over a time range, optionally grouped/filtered. API: POST /usage/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| meter_api_name | string | yes | The meterApiName to query (from amberflo_list_meters). |
| aggregation | string | yes | Aggregation function: SUM | COUNT | MIN | MAX. |
| time_grouping_interval | string | yes | Bucket size: HOUR | DAY | WEEK | MONTH. |
| start_time_in_seconds | integer | yes | Range start, unix epoch seconds (inclusive). |
| end_time_in_seconds | integer | no | Range end, unix epoch seconds. Defaults to now if omitted. |
| group_by | array | no | Dimension names to group results by, e.g. ["customerId"]. |
| filter | object | no | Dimension filter: map of dimension name -> allowed values. |
| take_limit | integer | no | Return only the top N groups. |
| take_is_ascending | boolean | no | Sort order for take (default false = descending). |
Get total usage across all meters over a time range, optionally grouped by customer or filtered to one customer. API: GET /usage/all.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_time_in_seconds | integer | yes | Range start, unix epoch seconds (inclusive). |
| end_time_in_seconds | integer | no | Range end, unix epoch seconds. Defaults to now if omitted. |
| time_grouping_interval | string | yes | Bucket size: HOUR | DAY | WEEK | MONTH. |
| group_by_customer_id | boolean | no | When true, group results by customer (sends groupBy=customerId). |
| filter_by_customer_id | string | no | Restrict results to a single customerId. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| meter_api_name | string | yes | The meterApiName to explain (from amberflo_list_meters). |
| start_time_in_seconds | integer | yes | Range start, unix epoch seconds (inclusive). |
| end_time_in_seconds | integer | no | Range end, unix epoch seconds. Defaults to now if omitted. |
| take_limit | integer | no | Return only the top N records. |
| group_by | array | no | Dimension names to group by, e.g. ["customerId"]. |
| filter | object | no | Dimension filter: map of dimension name -> allowed values. |
| aggregation | string | no | Aggregation function: SUM | COUNT | MIN | MAX. |
Get a customer's LATEST assigned product plan (pricing). API: GET /payments/pricing/amberflo/customer-pricing?CustomerId=<id>.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
List the full history of product plans assigned to a customer over time. API: GET /payments/pricing/amberflo/customer-pricing/list?CustomerId=<id>.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
List all invoices for a customer (optionally for a specific product), with payment status. API: GET /payments/billing/customer-product-invoice/all.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
| product_id | string | no | Product id. Default "1". |
| from_cache | boolean | no | Use cached invoices (faster). Default true. |
| with_payment_status | boolean | no | Include payment status. Default true. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
| product_id | string | no | Product id. Default "1". |
| from_cache | boolean | no | Use cached invoice (faster). Default true. |
| with_payment_status | boolean | no | Include payment status. Default true. |
| latest | boolean | no | Fetch the current open invoice. Default true. Ignored when a specific invoice is addressed. |
| product_plan_id | string | no | Product plan id of a specific past invoice (with year/month/day). |
| year | integer | no | Year of a specific past invoice. |
| month | integer | no | Month (1-12) of a specific past invoice. |
| day | integer | no | Day of month of a specific past invoice. |
List a customer's active prepaid credit orders for a product. API: GET /payments/pricing/amberflo/customer-prepaid/list?CustomerId=<id>&ProductId=<pid>.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
| product_id | string | no | Product id. Default "1". |
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/.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | Unique customerId to assign (your identifier for the customer). |
| customer_name | string | yes | Human-readable customer name. |
| customer_email | string | no | Customer email address. |
| enabled | boolean | no | Whether the customer is enabled. |
| traits | object | no | Arbitrary string traits (key/value metadata). |
| create_in_stripe | boolean | no | When true, also auto-create this customer in Stripe (adds ?autoCreateCustomerInStripe=true). |
WRITE: assign/attach a pricing product plan to a customer — this changes what the customer is billed. API: POST /payments/pricing/amberflo/customer-pricing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId to assign the plan to. |
| product_plan_id | string | yes | The productPlanId of the plan to assign. |
| product_id | string | no | Product id the plan belongs to. |
| start_time_in_seconds | integer | no | When the plan takes effect, unix epoch seconds. |
| end_time_in_seconds | integer | no | When the plan ends, unix epoch seconds. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| meter_api_name | string | yes | The meterApiName this event is for. |
| meter_value | number | yes | The numeric value of the usage event. |
| meter_time_in_millis | integer | yes | Event timestamp, unix epoch milliseconds. |
| customer_id | string | yes | The customerId this usage belongs to. |
| dimensions | object | no | Optional dimensions (key/value string metadata) for the event. |
| unique_id | string | no | Optional idempotency/unique id for the event. |
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 Amberflo 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 digest5355706a95704acb671bba3339e56a571c6912a106169c07c7904f9ab75966c4
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 |
|---|---|---|
| amberflo_list_customers | no tags | |
| amberflo_get_customer | untrusted-input | untrusted-input: keyword "fetch" |
| amberflo_list_meters | no tags | |
| amberflo_get_usage | no tags | |
| amberflo_get_all_usage | no tags | |
| amberflo_explain_usage | no tags | |
| amberflo_get_customer_plan | no tags | |
| amberflo_list_customer_plan_history | no tags | |
| amberflo_list_customer_invoices | no tags | |
| amberflo_get_customer_invoice | no tags | |
| amberflo_list_prepaid_orders | no tags | |
| amberflo_create_customer | state-write | state-write: declares destructiveHint: true |
| amberflo_assign_customer_plan | state-write | state-write: declares destructiveHint: true |
| amberflo_ingest_usage | 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 digest5355706a95704acb
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 Amberflo 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.