Remote MCP · Endpoint

TaskBullet Site Guide MCP server

No. TaskBullet Site Guide answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://taskbullet.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.GriffMurder/taskbullet-site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
213 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public, no-auth MCP for taskbullet.com: services, pricing, intent routing and the right next URL.
Listing
From the official MCP registry (active).
Recent checks of TaskBullet Site Guide
CheckedResultHandshake
5 hours agoHandshake completed213 ms
9 days agoHandshake completed83 ms
10 days agoHandshake completed131 ms
11 days agoHandshake completed92 ms
12 days agoHandshake completed114 ms
14 days agoHandshake completed655 ms
14 days agoHandshake completed126 ms
15 days agoHandshake completed201 ms
17 days agoHandshake completed108 ms
19 days agoHandshake completed143 ms
21 days agoHandshake completed100 ms
24 days agoHandshake completed111 ms
26 days agoHandshake completed73 ms
28 days agoHandshake completed123 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.

Listing data comes from the official MCP registry. Glide is not affiliated with TaskBullet Site Guide and makes no claim about it beyond what these checks measured.