Remote MCP · Endpoint

RepoPilot MCP server

No. RepoPilot answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://repopilot.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.repopilot/repopilot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
85 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Repository evidence for agents before they adopt dependencies, enter codebases, compare, or merge.
Listing
From the official MCP registry (active).
Recent checks of RepoPilot
CheckedResultHandshake
5 hours agoHandshake completed85 ms
2 days agoHandshake completed73 ms
4 days agoHandshake completed66 ms
5 days agoHandshake completed91 ms
7 days agoHandshake completed82 ms
8 days agoHandshake completed71 ms
9 days agoHandshake completed72 ms
12 days agoHandshake completed70 ms
13 days agoHandshake completed72 ms
15 days agoHandshake completed126 ms
16 days agoHandshake completed92 ms
17 days agoHandshake completed74 ms
19 days agoHandshake completed70 ms
19 days agoHandshake completed67 ms
20 days agoHandshake completed76 ms
21 days agoHandshake completed83 ms
22 days agoHandshake completed64 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 RepoPilot and makes no claim about it beyond what these checks measured.