Remote MCP · Endpoint

Dodo Payments Docs MCP server

No. Dodo Payments Docs answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://knowledge.dodopayments.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.dodopayments/dodo-knowledge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
349 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Semantic search over the current Dodo Payments documentation. No authentication required.
Listing
From the official MCP registry (active).
Recent checks of Dodo Payments Docs
CheckedResultHandshake
8 hours agoHandshake completed349 ms
14 hours agoHandshake completed511 ms
2 days agoHandshake completed605 ms
4 days agoHandshake completed236 ms
7 days agoHandshake completed347 ms
9 days agoHandshake completed330 ms
11 days agoHandshake completed311 ms
14 days agoHandshake completed422 ms
16 days agoHandshake completed475 ms
18 days agoHandshake completed414 ms
20 days agoHandshake completed484 ms
21 days agoHandshake completed314 ms
23 days agoHandshake completed441 ms

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

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.

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