Remote MCP · Endpoint

Programscape MCP server

No. Programscape answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://programscape.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.programscape/programscape
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
703 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Startup credits, programs and perks from checked sources, with saved plans and reported balances.
Listing
From the official MCP registry (active).
Recent checks of Programscape
CheckedResultHandshake
9 hours agoHandshake completed703 ms
4 days agoHandshake completed675 ms
14 days agoHandshake completed545 ms
15 days agoHandshake completed577 ms
15 days agoHandshake completed1.09 s
17 days agoHandshake completed866 ms
18 days agoHandshake completed649 ms
19 days agoHandshake completed548 ms
20 days agoHandshake completed590 ms
21 days agoHandshake completed601 ms
23 days agoHandshake completed568 ms
26 days agoHandshake completed626 ms
28 days agoHandshake completed99 ms

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

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