Remote MCP · Endpoint

Teppi MCP server

No. Teppi answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.teppi.xyz/mcp

The last check completed an MCP handshake.

Registry name
xyz.teppi/teppi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
495 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Check what a paid x402 endpoint or MCP server delivered, from probes anyone can repeat.
Listing
From the official MCP registry (active).
Recent checks of Teppi
CheckedResultHandshake
1 hour agoHandshake completed495 ms
2 days agoHandshake completed561 ms
4 days agoHandshake completed586 ms
5 days agoHandshake completed534 ms
7 days agoHandshake completed614 ms
8 days agoHandshake completed596 ms
9 days agoHandshake completed799 ms
12 days agoHandshake completed586 ms
13 days agoHandshake completed492 ms
15 days agoHandshake completed692 ms
17 days agoHandshake completed472 ms
18 days agoHandshake completed455 ms
19 days agoHandshake completed469 ms
20 days agoHandshake completed528 ms
21 days agoHandshake completed484 ms
21 days agoHandshake completed971 ms
23 days agoHandshake completed481 ms

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

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 Teppi and makes no claim about it beyond what these checks measured.