Remote MCP · Endpoint

GitHub Repo Change Intelligence MCP server

Yes, as of 34 minutes ago: the server returned an HTTP error.

DownLast checked 34 minutes ago

Server URL

https://github-intel.contentforge-press.workers.dev/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.contentforge-press/github-intel
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
0.0% from 14 checks
Described by its publisher as
Track public GitHub repos: free snapshot, paid release, star & issue intel via x402 USDC.
Listing
From the official MCP registry (active).
Recent checks of GitHub Repo Change Intelligence
CheckedResultHandshake
34 minutes agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
24 days agoFailed - the server returned an HTTP error—
26 days agoFailed - the server returned an HTTP error—
28 days agoFailed - the server returned an HTTP error—

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 7 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with GitHub Repo Change Intelligence and makes no claim about it beyond what these checks measured.