Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Polar MCP by usefulapi

REMOTE · POLAR-SH.USEFULAPI.IO

Products, customers, orders, subscriptions, benefits, revenue metrics and refunds.

0 this week 18 Trust /100

Last scanned (17 hours ago)

Scores higher than 3% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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
Transport & Reachability0
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.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 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
  • 1 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 “check_revenue_and_mrr_over_a_period” functional
    • New prompt “find_cancelled_subscriptions_and_their_customers” functional
    • New prompt “refund_an_order_or_create_a_checkout_link” functional
    • New prompt “review_recent_orders” functional
    • New prompt “see_what_a_customer_has_right_now” 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
    • Stability: 0.97 → pass security
    • Server version: 1.29.1 → 1.29.2 functional
    • Server version: 1.29.0 → 1.29.1 functional
  • 29 Oct 26 +1
    • 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
  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 21 Nov 2026 · Probed https://polar-sh.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 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA256 93e2fea3bbc31354138c8a47c5e87592
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 polar-sh.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
usefulapi.io. No DS 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://polar-sh.usefulapi.io/mcp Redirected 302 https://usefulapi.io/polar-sh/
http (plaintext) http://polar-sh.usefulapi.io/mcp Inconclusive 302 http://polar-sh.usefulapi.io/mcp
MCP tools · 26 exposed · ~2,525 tokens

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 →

Tool Tokens
polar_cancel_subscription ~84

Cancel a subscription at the end of its current period. The customer keeps access until then. Polar: PATCH /v1/subscriptions/{id}.

NameTypeReqDescription
customer_cancellation_commentstring–The customer's own words.
customer_cancellation_reasonstring–Why the customer is leaving, for your churn reporting.
subscription_idstringyesThe subscription to cancel.

No output schema declared.

No examples provided.

polar_create_checkout_link ~114

Create a reusable checkout URL for one or more products — the link you put in a page or an email. Polar: POST /v1/checkout-links/.

NameTypeReqDescription
allow_discount_codesboolean–Let the buyer enter a discount code. Defaults to true.
discount_idstring–Apply this discount automatically.
labelstring–An internal label for the link.
productsarrayyesProduct ids the link sells.
success_urlstring–Where to send the buyer after payment.

No output schema declared.

No examples provided.

polar_create_refund ~122

Refund an order, in full or in part. This moves real money back to the customer. Polar: POST /v1/refunds/.

NameTypeReqDescription
amountinteger–Amount in the currency's minor unit (cents). Omit to refund the full order.
commentstring–An internal note about the refund.
order_idstringyesThe order to refund.
reasonstringyesWhy the refund is being issued.
revoke_benefitsboolean–Also revoke the benefits the order granted. Defaults to false.

No output schema declared.

No examples provided.

polar_get_customer ~40

Fetch a single customer by Polar id. Polar: GET /v1/customers/{id}.

NameTypeReqDescription
customer_idstringyesThe customer's Polar id.

No output schema declared.

No examples provided.

polar_get_customer_state ~67

Fetch everything about one customer in a single call — active subscriptions, granted benefits and entitlements. The best answer to 'what does this customer currently have?'. Polar: GET /v1/customers/{id}/state.

NameTypeReqDescription
customer_idstringyesThe customer's Polar id.

No output schema declared.

No examples provided.

polar_get_customer_state_by_external_id ~73

Same as polar_get_customer_state, but looked up by YOUR external id rather than Polar's — the usual path when you hold your own user id. Polar: GET /v1/customers/external/{external_id}/state.

NameTypeReqDescription
external_idstringyesYour own id for this customer.

No output schema declared.

No examples provided.

polar_get_meter_quantities ~113

Fetch the aggregated quantities a meter has recorded over a window — what usage-based billing will charge for. Polar: GET /v1/meters/{id}/quantities.

NameTypeReqDescription
customer_idstring–Only this customer's usage.
end_timestampstringyesISO-8601 end of the window.
intervalstringyesBucket size for the series.
meter_idstringyesThe meter's id.
start_timestampstringyesISO-8601 start of the window.

No output schema declared.

No examples provided.

polar_get_metrics ~134

Fetch revenue and subscription metrics over a date range, bucketed by interval — orders, revenue, MRR, active subscriptions. Polar: GET /v1/metrics/.

NameTypeReqDescription
customer_idstring–Only this customer's metrics.
end_datestringyesEnd of the window, YYYY-MM-DD.
intervalstringyesBucket size for the series.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
product_idstring–Only this product's metrics.
start_datestringyesStart of the window, YYYY-MM-DD.

No output schema declared.

No examples provided.

polar_get_order ~44

Fetch a single order with its line items, discount and tax. Polar: GET /v1/orders/{id}.

NameTypeReqDescription
order_idstringyesThe order's id.

No output schema declared.

No examples provided.

polar_get_product ~42

Fetch a single product with its prices and attached benefits. Polar: GET /v1/products/{id}.

NameTypeReqDescription
product_idstringyesThe product's id.

No output schema declared.

No examples provided.

polar_get_subscription ~44

Fetch a single subscription with its product, price and period. Polar: GET /v1/subscriptions/{id}.

NameTypeReqDescription
subscription_idstringyesThe subscription's id.

No output schema declared.

No examples provided.

polar_list_benefit_grants ~82

List who has been granted one benefit, and whether the grant is still active. Polar: GET /v1/benefits/{id}/grants.

NameTypeReqDescription
benefit_idstringyesThe benefit's id.
limitinteger–Page size, 1-100.
pageinteger–1-based page number.

No output schema declared.

No examples provided.

polar_list_benefits ~111

List benefits — the things a product grants, such as licence keys, file downloads or Discord roles. Polar: GET /v1/benefits/.

NameTypeReqDescription
limitinteger–Page size, 1-100.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.
querystring–Free-text search.
typestring–Only benefits of this type.

No output schema declared.

No examples provided.

polar_list_customers ~105

List customers, optionally by email or a text query. Polar: GET /v1/customers/.

NameTypeReqDescription
emailstring–Only the customer with this email.
limitinteger–Page size, 1-100.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.
querystring–Free-text search over name and email.

No output schema declared.

No examples provided.

polar_list_discounts ~91

List discount codes and their redemption limits. Polar: GET /v1/discounts/.

NameTypeReqDescription
limitinteger–Page size, 1-100.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.
querystring–Free-text search over discount names and codes.

No output schema declared.

No examples provided.

polar_list_events ~151

List the raw usage events ingested for metering, filtered by customer, meter, name or time. Polar: GET /v1/events/.

NameTypeReqDescription
customer_idstring–Only this customer's events.
end_timestampstring–ISO-8601 upper bound.
limitinteger–Page size, 1-100.
meter_idstring–Only events matching this meter.
namestring–Only events with this name.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.
start_timestampstring–ISO-8601 lower bound.

No output schema declared.

No examples provided.

polar_list_license_keys ~110

List issued licence keys and their status. Polar: GET /v1/license-keys/.

NameTypeReqDescription
benefit_idstring–Only keys from this benefit.
limitinteger–Page size, 1-100.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.
statusstring–Only keys in this state, e.g. granted, revoked, disabled.

No output schema declared.

No examples provided.

polar_list_meters ~79

List the usage meters that aggregate events into billable quantities. Polar: GET /v1/meters/.

NameTypeReqDescription
limitinteger–Page size, 1-100.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.

No output schema declared.

No examples provided.

polar_list_orders ~175

List orders, filtered by customer, product, subscription, status or a date window. Polar: GET /v1/orders/.

NameTypeReqDescription
created_afterstring–ISO-8601 lower bound on creation time.
created_beforestring–ISO-8601 upper bound on creation time.
customer_idstring–Only this customer's orders.
limitinteger–Page size, 1-100.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.
product_idstring–Only orders for this product.
statusstring–Only orders in this state, e.g. paid, pending, refunded.
subscription_idstring–Only orders from this subscription.

No output schema declared.

No examples provided.

polar_list_organizations ~65

List the organisations the token can act for. Start here — most other tools take an organization_id. Polar: GET /v1/organizations/.

NameTypeReqDescription
limitinteger–Page size, 1-100.
pageinteger–1-based page number.

No output schema declared.

No examples provided.

polar_list_products ~127

List products, optionally filtered by archived state, recurrence or a text query. Polar: GET /v1/products/.

NameTypeReqDescription
is_archivedboolean–Only archived, or only live, products.
is_recurringboolean–Only subscriptions, or only one-off products.
limitinteger–Page size, 1-100.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.
querystring–Free-text search over product names.

No output schema declared.

No examples provided.

polar_list_refunds ~120

List refunds, filtered by order, subscription, customer or success. Polar: GET /v1/refunds/.

NameTypeReqDescription
customer_idstring–Only this customer's refunds.
limitinteger–Page size, 1-100.
order_idstring–Only refunds against this order.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.
succeededboolean–Only successful, or only failed, refunds.

No output schema declared.

No examples provided.

polar_list_subscriptions ~156

List subscriptions, filtered by customer, product, status, active state or cancellation window. Polar: GET /v1/subscriptions/.

NameTypeReqDescription
activeboolean–Only active, or only inactive, subscriptions.
cancel_at_period_endboolean–Only those already set to cancel — your churn pipeline.
customer_idstring–Only this customer's subscriptions.
limitinteger–Page size, 1-100.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.
product_idstring–Only subscriptions to this product.
statusstring–Only subscriptions in this state.

No output schema declared.

No examples provided.

polar_list_webhook_deliveries ~141

List webhook delivery attempts with their HTTP results — the tool for 'why did my webhook not arrive?'. Polar: GET /v1/webhooks/deliveries.

NameTypeReqDescription
end_timestampstring–ISO-8601 upper bound.
endpoint_idstring–Only deliveries to this endpoint.
event_typestring–Only deliveries of this event type.
limitinteger–Page size, 1-100.
pageinteger–1-based page number.
start_timestampstring–ISO-8601 lower bound.
succeededboolean–Only failures, or only successes.

No output schema declared.

No examples provided.

polar_list_webhook_endpoints ~81

List the configured webhook endpoints and their subscribed events. Polar: GET /v1/webhooks/endpoints.

NameTypeReqDescription
limitinteger–Page size, 1-100.
organization_idstring–Restrict to this organisation id. Needed when the token spans several organisations.
pageinteger–1-based page number.

No output schema declared.

No examples provided.

polar_redeliver_webhook_event ~54

Queue one webhook event for redelivery after your endpoint recovered. Polar: POST /v1/webhooks/events/{id}/redeliver.

NameTypeReqDescription
event_idstringyesThe webhook event to resend.

No output schema declared.

No examples provided.

Install

How do I install the Polar MCP by usefulapi server?

Polar MCP by usefulapi is a hosted endpoint at https://polar-sh.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 · polar-sh.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-polar-sh 'https://polar-sh.usefulapi.io/mcp'
Common questions

What is the Polar MCP by usefulapi server?

Polar MCP by usefulapi is listed in the public MCP registry as io.usefulapi/polar-sh. Products, customers, orders, subscriptions, benefits, revenue metrics and refunds. This page covers its hosted endpoint (https://polar-sh.usefulapi.io/mcp).

Is the Polar MCP by usefulapi server safe to use?

Polar 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 Polar MCP by usefulapi server expose?

Polar MCP by usefulapi exposes 26 tools: polar_list_organizations, polar_list_products, polar_get_product, polar_list_customers, polar_get_customer, and 21 more. Their descriptions and schemas cost roughly 2,525 tokens of context every time the server is loaded.

Does the Polar MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Polar 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 Polar MCP by usefulapi server still maintained?

Polar MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Polar MCP by usefulapi server?

VerifyMCP ran 4 checks on Polar MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Polar MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.