Remote MCP · Endpoint

Chargebee MCP by usefulapi MCP server

No. Chargebee MCP by usefulapi answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://chargebee.usefulapi.io/mcp

The last check completed an MCP handshake.

Registry name
io.usefulapi/chargebee
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
280 ms
Tools exposed
13 tools
Uptime, last 30 days
66.7% from 18 checks
Described by its publisher as
Read Chargebee customers, subscriptions, invoices, items, transactions, credit notes and coupons.
Website
https://usefulapi.io/chargebee/
Repository
https://github.com/m190/usefulapi-mcp
Listing
From the official MCP registry (active).
Recent checks of Chargebee MCP by usefulapi
CheckedResultHandshake
1 hour agoHandshake completed280 ms
2 days agoHandshake completed278 ms
4 days agoHandshake completed171 ms
6 days agoHandshake completed71 ms
7 days agoHandshake completed209 ms
9 days agoHandshake completed208 ms
10 days agoFailed - the check failed for an unclassified reason—
11 days agoFailed - the check failed for an unclassified reason—
14 days agoHandshake completed187 ms
15 days agoHandshake completed206 ms
17 days agoHandshake completed237 ms
19 days agoHandshake completed145 ms
20 days agoHandshake completed181 ms
21 days agoHandshake completed201 ms
22 days agoFailed - the check failed for an unclassified reason—
22 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—
25 days agoFailed - the check failed for an unclassified reason—

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 18.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Chargebee MCP by usefulapi and makes no claim about it beyond what these checks measured.