Remote MCP · Endpoint

Nepternship MCP server

No. Nepternship answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.nepternship.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.robertisaak/nepternship
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
383 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Warm intros and referrals for internships and entry-level jobs at 3,000+ companies.
Listing
From the official MCP registry (active).
Recent checks of Nepternship
CheckedResultHandshake
7 hours agoHandshake completed383 ms
3 days agoHandshake completed521 ms
12 days agoHandshake completed525 ms
12 days agoHandshake completed458 ms
14 days agoHandshake completed500 ms
15 days agoHandshake completed1.01 s
16 days agoHandshake completed335 ms
17 days agoHandshake completed485 ms
18 days agoHandshake completed577 ms
20 days agoHandshake completed395 ms
22 days agoHandshake completed364 ms
25 days agoHandshake completed407 ms
27 days agoHandshake completed272 ms
29 days agoHandshake completed267 ms

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

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