Remote MCP · Endpoint

Teppek MCP server

No. Teppek answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.teppek.com/mcp

The last check completed an MCP handshake.

Registry name
com.teppek/teppek
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
994 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Agent-accessible map of global supply & demand: jobs, homes, cars & services your AI can act on
Listing
From the official MCP registry (active).
Recent checks of Teppek
CheckedResultHandshake
1 hour agoHandshake completed994 ms
2 days agoHandshake completed715 ms
4 days agoHandshake completed691 ms
5 days agoHandshake completed912 ms
7 days agoHandshake completed768 ms
8 days agoHandshake completed1.05 s
9 days agoHandshake completed862 ms
12 days agoHandshake completed713 ms
13 days agoHandshake completed1.11 s
15 days agoHandshake completed848 ms
16 days agoHandshake completed811 ms
17 days agoHandshake completed525 ms
19 days agoHandshake completed714 ms
20 days agoHandshake completed654 ms
20 days agoHandshake completed859 ms
21 days agoHandshake completed592 ms
22 days agoHandshake completed1.94 s

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