Remote MCP · Endpoint

SkillAgent MCP server

No. SkillAgent answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://skillagent.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.skillagent/skills
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
755 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search and fetch AI agent skills, rules files and MCP servers indexed from GitHub.
Listing
From the official MCP registry (active).
Recent checks of SkillAgent
CheckedResultHandshake
2 hours agoHandshake completed755 ms
2 days agoHandshake completed93 ms
4 days agoHandshake completed552 ms
6 days agoHandshake completed157 ms
7 days agoHandshake completed86 ms
9 days agoHandshake completed461 ms
10 days agoHandshake completed100 ms
11 days agoHandshake completed103 ms
14 days agoHandshake completed484 ms
15 days agoHandshake completed97 ms
17 days agoHandshake completed496 ms
18 days agoHandshake completed570 ms
19 days agoHandshake completed341 ms
20 days agoHandshake completed431 ms
21 days agoHandshake completed422 ms
22 days agoHandshake completed86 ms
23 days agoHandshake completed579 ms

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

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