Developer · Remote MCP server

GitHub Repository Intelligence

Repo intel for AI coding agents: overview, PRs, contributors, hot files, CI, deps. Remote MCP.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.heisencodex-jpg/github-repo-intel-mcp
Version
0.3.1
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-05-21
Updated
2026-05-21
Publisher
heisencodex-jpg (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/heisencodex-jpg) · how
Listed under
GitHub MCP servers
Repository
github.com/heisencodex-jpg/github-repo-intel-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://cg-nguyen--github-repo-intel-mcp.apify.actor/mcpAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401
Checked on
2026-10-05

How the live check works

How to connect GitHub Repository Intelligence

GitHub Repository Intelligence is a remote MCP server: there is nothing to install. Its endpoint is https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Github Public Repos McpDive into the world of open-source with the GitHub Repo Explorer. Utilize the GitHub.Remote · HTTPLive check: ✗ no handshakegithub-public-repos-mcp.mcpize.run
Github Repo Intelligence MCPGitHub repo maintainability verdicts-maintained, slowing, at-risk, abandoned-via MCP.Remote · HTTPLive check: sign-in requiredjoeslade--github-repo-intelligence-mcp.apify.actor
Github Repo MCPMCP server for GitHub repo health, commit summaries, issue triage, and RAG Q&A.Local · stdionpm: @thedhruv07/github-repo-mcp
GitHub Repo ShapeParse owner and repo from a GitHub URL. Path discarded.Remote · HTTPLive check: ✓ handshakeagent-observatory-sensor.nolimit-observatory.workers.dev
Github StatsMCP server for GitHub repo stats: stars, forks, contributors, activity.Local · stdionpm: sovereign-github-stats-mcp
Github Webhook MCPMCP server bridging GitHub webhooks via Cloudflare Worker for real-time event streaming.Local · stdionpm: github-webhook-mcp
Github_privateGitHub Private MCP Pack - access private repos, org data via OAuth.Remote · HTTPLive check: ✓ handshakegateway.pipeworx.io
github-twinPersonal RAG over your GitHub history (commits, code, reviews), served to Claude Code over MCP.Local · stdioPyPI: github-twin