Remote MCP · Endpoint

Nothing.gripe MCP server

No. Nothing.gripe answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://nothing.gripe/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.AmithKumar1/nothing-gripe
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
111 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Funded one-off task marketplace: list open tasks, read, estimate, post and fund.
Listing
From the official MCP registry (active).
Recent checks of Nothing.gripe
CheckedResultHandshake
3 hours agoHandshake completed111 ms
9 days agoHandshake completed174 ms
10 days agoHandshake completed201 ms
11 days agoHandshake completed111 ms
12 days agoHandshake completed137 ms
14 days agoHandshake completed182 ms
14 days agoHandshake completed112 ms
15 days agoHandshake completed59 ms
17 days agoHandshake completed148 ms
19 days agoHandshake completed114 ms
21 days agoHandshake completed288 ms
24 days agoHandshake completed119 ms
26 days agoHandshake completed103 ms
28 days agoHandshake completed94 ms

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

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