Lago MCP by usefulapi
REMOTE · LAGO.USEFULAPI.IO
Read Lago customers, subscriptions, invoices, usage and revenue analytics; write events.
Available components
Last scanned (4 hours 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_or_record_a_usage_event” functional
- New prompt “check_a_customer_s_usage_and_subscriptions” functional
- New prompt “find_unpaid_invoices_and_the_customers_behind_them” functional
- New prompt “review_plans_billable_metrics_coupons_and_add_ons” functional
- New prompt “track_monthly_recurring_and_gross_revenue” 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://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 | 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 lago.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://lago.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/lago/ |
| http (plaintext) | http://lago.usefulapi.io/mcp | Inconclusive | 302 | http://lago.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 →
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 ~183
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 | string|number | – | 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.
How do I install the Lago MCP by usefulapi server?
Lago MCP by usefulapi 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'
What is the Lago MCP by usefulapi server?
Lago MCP by usefulapi is 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 Lago MCP by usefulapi server safe to use?
Lago 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 Lago MCP by usefulapi server expose?
Lago MCP by usefulapi 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,836 tokens of context every time the server is loaded.
Does the Lago MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Lago 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 Lago MCP by usefulapi server still maintained?
Lago 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.