Amberflo MCP by usefulapi
REMOTE · AMBERFLO.USEFULAPI.IO
Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid.
Available components
Last scanned (1 hour ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_a_customer_and_assign_a_pricing_plan” functional
- New prompt “check_a_customer_s_plan_history_and_prepaid_credit” functional
- New prompt “compare_usage_across_customers_for_a_period” functional
- New prompt “find_out_why_a_meter_number_looks_wrong” functional
- New prompt “list_unpaid_invoices_and_read_the_open_one” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 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 5 Nov 2026 · Probed https://amberflo.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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.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 amberflo.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://amberflo.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/amberflo/ |
| http (plaintext) | http://amberflo.usefulapi.io/mcp | Inconclusive | 302 | http://amberflo.usefulapi.io/mcp |
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 →
amberflo_assign_customer_plan Assign customer plan ~133
WRITE: assign/attach a pricing product plan to a customer — this changes what the customer is billed. API: POST /payments/pricing/amberflo/customer-pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId to assign the plan to. |
| end_time_in_seconds | integer | – | When the plan ends, unix epoch seconds. |
| product_id | string | – | Product id the plan belongs to. |
| product_plan_id | string | yes | The productPlanId of the plan to assign. |
| start_time_in_seconds | integer | – | When the plan takes effect, unix epoch seconds. |
No output schema declared.
No examples provided.
amberflo_create_customer Create customer ~148
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| create_in_stripe | boolean | – | When true, also auto-create this customer in Stripe (adds ?autoCreateCustomerInStripe=true). |
| customer_email | string | – | Customer email address. |
| customer_id | string | yes | Unique customerId to assign (your identifier for the customer). |
| customer_name | string | yes | Human-readable customer name. |
| enabled | boolean | – | Whether the customer is enabled. |
| traits | object | – | Arbitrary string traits (key/value metadata). |
No output schema declared.
No examples provided.
amberflo_explain_usage Explain usage ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregation | string | – | Aggregation function: SUM | COUNT | MIN | MAX. |
| end_time_in_seconds | integer | – | Range end, unix epoch seconds. Defaults to now if omitted. |
| filter | object | – | Dimension filter: map of dimension name -> allowed values. |
| group_by | array | – | Dimension names to group by, e.g. ["customerId"]. |
| 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). |
| take_limit | integer | – | Return only the top N records. |
No output schema declared.
No examples provided.
amberflo_get_all_usage Get all usage ~143
Get total usage across all meters over a time range, optionally grouped by customer or filtered to one customer. API: GET /usage/all.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time_in_seconds | integer | – | Range end, unix epoch seconds. Defaults to now if omitted. |
| filter_by_customer_id | string | – | Restrict results to a single customerId. |
| group_by_customer_id | boolean | – | When true, group results by customer (sends groupBy=customerId). |
| start_time_in_seconds | integer | yes | Range start, unix epoch seconds (inclusive). |
| time_grouping_interval | string | yes | Bucket size: HOUR | DAY | WEEK | MONTH. |
No output schema declared.
No examples provided.
amberflo_get_customer Get a customer ~47
Fetch a single customer by its Amberflo customerId. API: GET /customers/?customerId=<id>.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId to fetch. |
No output schema declared.
No examples provided.
amberflo_get_customer_invoice Get customer invoice ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
| day | integer | – | Day of month of a specific past invoice. |
| from_cache | boolean | – | Use cached invoice (faster). Default true. |
| latest | boolean | – | Fetch the current open invoice. Default true. Ignored when a specific invoice is addressed. |
| month | integer | – | Month (1-12) of a specific past invoice. |
| product_id | string | – | Product id. Default "1". |
| product_plan_id | string | – | Product plan id of a specific past invoice (with year/month/day). |
| with_payment_status | boolean | – | Include payment status. Default true. |
| year | integer | – | Year of a specific past invoice. |
No output schema declared.
No examples provided.
amberflo_get_customer_plan Get customer plan ~54
Get a customer's LATEST assigned product plan (pricing). API: GET /payments/pricing/amberflo/customer-pricing?CustomerId=<id>.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
No output schema declared.
No examples provided.
amberflo_get_usage Query usage for a meter ~208
Query aggregated usage for a single meter over a time range, optionally grouped/filtered. API: POST /usage/.
| Name | Type | Req | Description |
|---|---|---|---|
| aggregation | string | yes | Aggregation function: SUM | COUNT | MIN | MAX. |
| end_time_in_seconds | integer | – | Range end, unix epoch seconds. Defaults to now if omitted. |
| filter | object | – | Dimension filter: map of dimension name -> allowed values. |
| group_by | array | – | Dimension names to group results by, e.g. ["customerId"]. |
| meter_api_name | string | yes | The meterApiName to query (from amberflo_list_meters). |
| start_time_in_seconds | integer | yes | Range start, unix epoch seconds (inclusive). |
| take_is_ascending | boolean | – | Sort order for `take` (default false = descending). |
| take_limit | integer | – | Return only the top N groups. |
| time_grouping_interval | string | yes | Bucket size: HOUR | DAY | WEEK | MONTH. |
No output schema declared.
No examples provided.
amberflo_ingest_usage Ingest usage event ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customerId this usage belongs to. |
| dimensions | object | – | Optional dimensions (key/value string metadata) for the event. |
| meter_api_name | string | yes | The meterApiName this event is for. |
| meter_time_in_millis | integer | yes | Event timestamp, unix epoch milliseconds. |
| meter_value | number | yes | The numeric value of the usage event. |
| unique_id | string | – | Optional idempotency/unique id for the event. |
No output schema declared.
No examples provided.
amberflo_list_customer_invoices List customer invoices ~102
List all invoices for a customer (optionally for a specific product), with payment status. API: GET /payments/billing/customer-product-invoice/all.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
| from_cache | boolean | – | Use cached invoices (faster). Default true. |
| product_id | string | – | Product id. Default "1". |
| with_payment_status | boolean | – | Include payment status. Default true. |
No output schema declared.
No examples provided.
amberflo_list_customer_plan_history List customer plan history ~59
List the full history of product plans assigned to a customer over time. API: GET /payments/pricing/amberflo/customer-pricing/list?CustomerId=<id>.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
No output schema declared.
No examples provided.
amberflo_list_customers List customers ~45
List all customers registered in your Amberflo account (id, name, email, traits, enabled). Good first call to discover customer ids. API: GET /customers/.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
amberflo_list_meters List meters ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
amberflo_list_prepaid_orders List prepaid orders ~75
List a customer's active prepaid credit orders for a product. API: GET /payments/pricing/amberflo/customer-prepaid/list?CustomerId=<id>&ProductId=<pid>.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The Amberflo customerId. |
| product_id | string | – | Product id. Default "1". |
No output schema declared.
No examples provided.
How do I install the Amberflo MCP by usefulapi server?
Amberflo MCP by usefulapi is a hosted endpoint at https://amberflo.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 · amberflo.usefulapi.io
claude mcp add --transport http io-usefulapi-amberflo 'https://amberflo.usefulapi.io/mcp'
What is the Amberflo MCP by usefulapi server?
Amberflo MCP by usefulapi is listed in the public MCP registry as io.usefulapi/amberflo. Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid. This page covers its hosted endpoint (https://amberflo.usefulapi.io/mcp).
Is the Amberflo MCP by usefulapi server safe to use?
Amberflo MCP by usefulapi scores 18 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 Amberflo MCP by usefulapi server expose?
Amberflo MCP by usefulapi exposes 14 tools: amberflo_list_customers, amberflo_get_customer, amberflo_list_meters, amberflo_get_usage, amberflo_get_all_usage, and 9 more. Their descriptions and schemas cost roughly 1,600 tokens of context every time the server is loaded.
Does the Amberflo MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Amberflo MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Amberflo MCP by usefulapi server still maintained?
Amberflo MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.