Remote MCP · Endpoint

co.tasklinkr/skills MCP server

No. co.tasklinkr/skills answered an MCP handshake 23 minutes ago.

UpLast checked 23 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
co.tasklinkr/skills
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
582 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Executable skill packages for agents: vetted competence, ready to run, not just documents.
Listing
From the official MCP registry (active).
Recent checks of co.tasklinkr/skills
CheckedResultHandshake
23 minutes agoHandshake completed582 ms
8 days agoHandshake completed57 ms
9 days agoHandshake completed73 ms
11 days agoHandshake completed62 ms
12 days agoHandshake completed44 ms
13 days agoHandshake completed76 ms
14 days agoHandshake completed192 ms
14 days agoHandshake completed77 ms
16 days agoHandshake completed65 ms
19 days agoHandshake completed74 ms
21 days agoHandshake completed97 ms
24 days agoHandshake completed91 ms
26 days agoHandshake completed114 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 co.tasklinkr/skills and makes no claim about it beyond what these checks measured.