Remote MCP · Endpoint

ai.skillsinput/mcp MCP server

No. ai.skillsinput/mcp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.skillsinput.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.skillsinput/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
31 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
AI-powered career tools: job search, skills intelligence, career roadmaps, and resume building.
Listing
From the official MCP registry (active).
Recent checks of ai.skillsinput/mcp
CheckedResultHandshake
1 hour agoHandshake completed31 ms
2 days agoHandshake completed24 ms
4 days agoHandshake completed18 ms
6 days agoHandshake completed18 ms
7 days agoHandshake completed41 ms
9 days agoHandshake completed42 ms
10 days agoHandshake completed24 ms
11 days agoHandshake completed27 ms
14 days agoHandshake completed28 ms
15 days agoHandshake completed18 ms
17 days agoHandshake completed20 ms
18 days agoHandshake completed19 ms
19 days agoHandshake completed20 ms
21 days agoHandshake completed17 ms
22 days agoHandshake completed29 ms
22 days agoHandshake completed27 ms

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

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