Remote MCP · Endpoint

SwiftSkills MCP server

No. SwiftSkills answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://swiftskills.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.swiftskills/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
118 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search a curated catalog of agent skills, MCP servers and rules for Swift, SwiftUI, Xcode and iOS.
Listing
From the official MCP registry (active).
Recent checks of SwiftSkills
CheckedResultHandshake
17 minutes agoHandshake completed118 ms
8 days agoHandshake completed79 ms
9 days agoHandshake completed73 ms
11 days agoHandshake completed623 ms
12 days agoHandshake completed1.08 s
13 days agoHandshake completed233 ms
14 days agoHandshake completed74 ms
14 days agoHandshake completed103 ms
16 days agoHandshake completed111 ms
19 days agoHandshake completed97 ms
21 days agoHandshake completed85 ms
24 days agoHandshake completed309 ms
26 days agoHandshake completed152 ms
28 days agoHandshake completed169 ms

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

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