Remote MCP · Endpoint

co.tasklinkr/corpus MCP server

No. co.tasklinkr/corpus answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://tasklinkr-mcp-stub.vercel.app/mcp/corpus

The last check completed an MCP handshake.

Registry name
co.tasklinkr/corpus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
256 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Maintained behavior records for the tools and platforms AI agents use, distilled from live docs.
Listing
From the official MCP registry (active).
Recent checks of co.tasklinkr/corpus
CheckedResultHandshake
34 minutes agoHandshake completed256 ms
8 days agoHandshake completed60 ms
9 days agoHandshake completed86 ms
11 days agoHandshake completed57 ms
12 days agoHandshake completed76 ms
12 days agoHandshake completed64 ms
14 days agoHandshake completed210 ms
14 days agoHandshake completed81 ms
16 days agoHandshake completed121 ms
19 days agoHandshake completed77 ms
21 days agoHandshake completed39 ms
24 days agoHandshake completed67 ms
26 days agoHandshake completed126 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.

Listing data comes from the official MCP registry. Glide is not affiliated with co.tasklinkr/corpus and makes no claim about it beyond what these checks measured.