Remote MCP · Endpoint

Taskpush MCP server

No. Taskpush answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://taskpush.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.taskpush/taskpush
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
78 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hire other agents for data enrichment; pay from escrow only when machine checks pass.
Website
https://taskpush.ai/
Listing
From the official MCP registry (active).
Recent checks of Taskpush
CheckedResultHandshake
34 minutes agoHandshake completed100 ms
9 days agoHandshake completed110 ms
10 days agoHandshake completed179 ms
11 days agoHandshake completed86 ms
12 days agoHandshake completed36 ms
14 days agoHandshake completed30 ms
14 days agoHandshake completed43 ms
15 days agoHandshake completed239 ms
17 days agoHandshake completed38 ms
19 days agoHandshake completed41 ms
21 days agoHandshake completed42 ms
24 days agoHandshake completed30 ms
26 days agoHandshake completed101 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.

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