io.usefulapi/lago
REMOTE · LAGO.USEFULAPI.IO · SCANNED SEP 20
Read Lago customers, subscriptions, invoices, usage and revenue analytics; write events.
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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1832 tokens (~76/item across 24 items; 24 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 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/lago MCP server?
io.usefulapi/lago is a hosted endpoint at https://lago.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 · lago.usefulapi.io
claude mcp add --transport http io-usefulapi-lago 'https://lago.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-lago": {
"url": "https://lago.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-lago": {
"type": "http",
"url": "https://lago.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-lago] url = "https://lago.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-lago": {
"type": "remote",
"url": "https://lago.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-lago --url 'https://lago.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-lago:
url: "https://lago.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-lago": {
"Transport": "http",
"Url": "https://lago.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-lago -t streamable-http -u 'https://lago.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-lago": {
"type": "http",
"url": "https://lago.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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −10
- Stability: pass → 0.27 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 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.
- 8 Sept 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.
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://lago.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 | ed6112eb209009fd0e3703ab9029fa09 |
| SANs: usefulapi.io, lago.usefulapi.io, *.lago.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 lago.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://lago.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://lago.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://lago.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://lago.usefulapi.io/mcp |
| Authorisation server | https://lago.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lago.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://lago.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 →
lago_analytics_gross_revenue Analytics: gross revenue ~89
Monthly gross revenue (finalized invoice payments + advance fees, net of tax/discounts). Lago API: GET /analytics/gross_revenue.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency filter (ISO 4217, e.g. USD). |
| external_customer_id | string | – | Filter revenue at the customer level. |
| months | integer | – | Number of months to return. |
No output schema declared.
No examples provided.
lago_analytics_mrr Analytics: MRR ~62
Monthly recurring revenue (MRR) from subscription fees. Lago API: GET /analytics/mrr.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Currency filter (ISO 4217, e.g. USD). |
| months | integer | – | Number of months to return. |
No output schema declared.
No examples provided.
lago_create_customer Create customer ~212
Creates a customer in Lago (additive). Lago API: POST /customers with body { "customer": { ... } }.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Billing country code (ISO 3166 alpha-2). |
| currency | string | – | Customer currency (ISO 4217). |
| string | – | Email of the customer. | |
| external_id | string | yes | The customer external unique identifier (required, provided by your application). |
| legal_name | string | – | Legal company name. |
| legal_number | string | – | Legal company number. |
| metadata | array | – | Structured metadata to attach to the customer (Lago expects an array of {key, value, display_in_invoice?} objects). |
| name | string | – | Full name of the customer. |
| phone | string | – | Phone number. |
| tax_identification_number | string | – | Tax identification number. |
| timezone | string | – | Customer timezone, e.g. America/New_York. |
| url | string | – | Customer URL. |
No output schema declared.
No examples provided.
lago_create_event Create usage event ~179
Records a usage/metering event in Lago. This WILL be counted toward the customer's usage and affects billing. Idempotent via transaction_id. Lago API: POST /events with body { "event": { ... } }.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The billable metric code this event targets (required). |
| external_subscription_id | string | yes | The subscription external id to link the event to (required). |
| precise_total_amount_cents | string | – | Precise total amount in cents, used by the dynamic pricing model. |
| properties | object | – | Additional event properties used to compute the fee (required for sum/max/unique aggregations). |
| timestamp | – | – | Unix timestamp in seconds (or ISO); defaults to event reception time. |
| transaction_id | string | yes | Unique identifier for the event — the idempotency key (required). |
No output schema declared.
No examples provided.
lago_get_billable_metric Get billable metric ~45
Retrieve a single billable metric by code. Lago API: GET /billable_metrics/{code}.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The billable metric's unique code. |
No output schema declared.
No examples provided.
lago_get_credit_note Get credit note ~48
Retrieve a single credit note by its Lago id. Lago API: GET /credit_notes/{lago_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| lago_id | string | yes | The credit note's Lago id (UUID). |
No output schema declared.
No examples provided.
lago_get_customer Get customer ~46
Retrieve a single customer by external id. Lago API: GET /customers/{external_customer_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| external_customer_id | string | yes | The customer external unique identifier (from your application). |
No output schema declared.
No examples provided.
lago_get_customer_current_usage Get customer current usage ~86
Retrieve a customer's usage-based billing data for the current period. Lago API: GET /customers/{external_customer_id}/current_usage.
| Name | Type | Req | Description |
|---|---|---|---|
| apply_taxes | boolean | – | Whether taxes should be applied. Defaults to true. |
| external_customer_id | string | yes | The customer external unique identifier. |
| external_subscription_id | string | yes | The subscription's external unique identifier (required). |
No output schema declared.
No examples provided.
lago_get_customer_past_usage Get customer past usage ~102
Retrieve a customer's usage-based billing data for past periods. Lago API: GET /customers/{external_customer_id}/past_usage.
| Name | Type | Req | Description |
|---|---|---|---|
| billable_metric_code | string | – | Filter usage to a specific billable metric code. |
| external_customer_id | string | yes | The customer external unique identifier. |
| external_subscription_id | string | yes | The subscription's external unique identifier (required). |
| periods_count | integer | – | Number of past billing periods to return. |
No output schema declared.
No examples provided.
lago_get_customer_portal_url Get customer portal URL ~47
Get a customer's billing portal URL. Lago API: GET /customers/{external_customer_id}/portal_url.
| Name | Type | Req | Description |
|---|---|---|---|
| external_customer_id | string | yes | The customer external unique identifier. |
No output schema declared.
No examples provided.
lago_get_invoice Get invoice ~45
Retrieve a single invoice by its Lago id. Lago API: GET /invoices/{lago_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| lago_id | string | yes | The invoice's Lago id (UUID). |
No output schema declared.
No examples provided.
lago_get_plan Get plan ~37
Retrieve a single plan by code. Lago API: GET /plans/{code}.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The plan's unique code. |
No output schema declared.
No examples provided.
lago_get_subscription Get subscription ~41
Retrieve a single subscription by external id. Lago API: GET /subscriptions/{external_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | yes | The subscription's external unique identifier. |
No output schema declared.
No examples provided.
lago_list_add_ons List add-ons ~51
List add-ons, paginated. Lago API: GET /add_ons.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
lago_list_billable_metrics List billable metrics ~52
List billable metrics, paginated. Lago API: GET /billable_metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
lago_list_coupons List coupons ~49
List coupons, paginated. Lago API: GET /coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
lago_list_credit_notes List credit notes ~65
List credit notes, optionally filtered by customer. Lago API: GET /credit_notes.
| Name | Type | Req | Description |
|---|---|---|---|
| external_customer_id | string | – | Filter by customer external id. |
| page | integer | – | Page number for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
lago_list_customer_subscriptions List customer subscriptions ~43
List a customer's subscriptions. Lago API: GET /customers/{external_customer_id}/subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| external_customer_id | string | yes | The customer external unique identifier. |
No output schema declared.
No examples provided.
lago_list_customers List customers ~49
List customers in Lago, paginated. Lago API: GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
lago_list_fees List fees ~106
List fees, optionally filtered by customer, subscription, or fee type. Lago API: GET /fees.
| Name | Type | Req | Description |
|---|---|---|---|
| external_customer_id | string | – | Filter by customer external id. |
| external_subscription_id | string | – | Filter by subscription external id. |
| fee_type | string | – | Filter by fee type: charge | add_on | subscription | credit | commitment. |
| page | integer | – | Page number for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
lago_list_invoices List invoices ~158
List invoices, optionally filtered by customer, status, payment status, or issuing date. Lago API: GET /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| external_customer_id | string | – | Filter by customer external id. |
| issuing_date_from | string | – | Filter invoices issued on/after this date (yyyy-mm-dd). |
| issuing_date_to | string | – | Filter invoices issued on/before this date (yyyy-mm-dd). |
| page | integer | – | Page number for pagination. |
| payment_status | string | – | Filter by a single payment status: pending | failed | succeeded. |
| per_page | integer | – | Number of records per page. |
| status | string | – | Filter by a single status: draft | finalized | failed | pending | voided. |
No output schema declared.
No examples provided.
lago_list_plans List plans ~48
List billing plans, paginated. Lago API: GET /plans.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
lago_list_subscriptions List subscriptions ~103
List subscriptions, optionally filtered by customer, plan, or status. Lago API: GET /subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| external_customer_id | string | – | Filter by customer external id. |
| page | integer | – | Page number for pagination. |
| per_page | integer | – | Number of records per page. |
| plan_code | string | – | Filter by plan code. |
| status | string | – | Filter by a single status: active | pending | canceled | terminated. Default active. |
No output schema declared.
No examples provided.
lago_list_wallets List wallets ~69
List a customer's prepaid credit wallets. Lago API: GET /customers/{external_customer_id}/wallets.
| Name | Type | Req | Description |
|---|---|---|---|
| external_customer_id | string | yes | The customer external unique identifier. |
| page | integer | – | Page number for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
What is the io.usefulapi/lago MCP server?
io.usefulapi/lago is an MCP server listed in the public MCP registry as io.usefulapi/lago. Read Lago customers, subscriptions, invoices, usage and revenue analytics; write events. This page covers its hosted endpoint (https://lago.usefulapi.io/mcp).
Is the io.usefulapi/lago MCP server safe to use?
io.usefulapi/lago scores 80 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/lago MCP server expose?
io.usefulapi/lago exposes 24 tools: lago_list_customers, lago_get_customer, lago_get_customer_current_usage, lago_get_customer_past_usage, lago_list_customer_subscriptions, and 19 more. Their descriptions and schemas cost roughly 1,832 tokens of context every time the server is loaded.
Does the io.usefulapi/lago MCP server require authentication?
Yes. io.usefulapi/lago 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/lago MCP server still maintained?
io.usefulapi/lago 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.