io.usefulapi/amberflo
REMOTE · AMBERFLO.USEFULAPI.IO · SCANNED SEP 20
Query and manage Amberflo metering & billing: customers, meters, usage, plans, invoices, prepaid.
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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1600 tokens (~114/item across 14 items; 14 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 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/amberflo MCP server?
io.usefulapi/amberflo 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'
{
"mcpServers": {
"io-usefulapi-amberflo": {
"url": "https://amberflo.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-amberflo": {
"type": "http",
"url": "https://amberflo.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-amberflo] url = "https://amberflo.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-amberflo": {
"type": "remote",
"url": "https://amberflo.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-amberflo --url 'https://amberflo.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-amberflo:
url: "https://amberflo.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-amberflo": {
"Transport": "http",
"Url": "https://amberflo.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-amberflo -t streamable-http -u 'https://amberflo.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-amberflo": {
"type": "http",
"url": "https://amberflo.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.
- 1 Sept 26 +1
- Stability: 0.97 → pass security
- 31 Aug 26 −1
- Stability: pass → 0.97 functional
- 30 Aug 26 +1
- Stability: 0.97 → pass security
- 29 Aug 26 −1
- Stability: pass → 0.97 functional
- 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
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://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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 41d8f6602b3631350e6985fd3564eed6 |
| SANs: usefulapi.io, amberflo.usefulapi.io, *.amberflo.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 | 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://amberflo.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://amberflo.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://amberflo.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://amberflo.usefulapi.io/mcp |
| Authorisation server | https://amberflo.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://amberflo.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 →
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.
What is the io.usefulapi/amberflo MCP server?
io.usefulapi/amberflo is an MCP server 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 io.usefulapi/amberflo MCP server safe to use?
io.usefulapi/amberflo scores 86 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/amberflo MCP server expose?
io.usefulapi/amberflo 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 io.usefulapi/amberflo MCP server require authentication?
Yes. io.usefulapi/amberflo 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/amberflo MCP server still maintained?
io.usefulapi/amberflo 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.