Remote MCP · Endpoint

dev.tmpstate/tmpstate MCP server

No. dev.tmpstate/tmpstate answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tmpstate.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.tmpstate/tmpstate
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
128 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Zero-key temporary JSON database for agents: one tool call, no signup, no OAuth, no API keys.
Website
https://tmpstate.dev/
Listing
From the official MCP registry (active).
Recent checks of dev.tmpstate/tmpstate
CheckedResultHandshake
1 hour agoHandshake completed128 ms
2 days agoHandshake completed767 ms
4 days agoHandshake completed139 ms
5 days agoHandshake completed72 ms
7 days agoHandshake completed155 ms
8 days agoHandshake completed75 ms
9 days agoHandshake completed735 ms
12 days agoHandshake completed855 ms
13 days agoHandshake completed762 ms
15 days agoHandshake completed80 ms
16 days agoHandshake completed105 ms
18 days agoHandshake completed129 ms
19 days agoHandshake completed791 ms
20 days agoHandshake completed663 ms
20 days agoHandshake completed89 ms
21 days agoHandshake completed109 ms
22 days agoHandshake completed805 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.

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