GitHub Repository Intelligence

io.github.heisencodex-jpgPublished by GitHub account heisencodex-jpgv0.3.1Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Hosted MCP endpoint that gives an assistant read-only intelligence on any GitHub repository: overview, recent PRs, contributors, hot files, CI status and parsed

What you can do
Read repository facts: stars, forks, language, license, topics and last push date, plus top contributors by commit count and recent pull requests with author, state and merge dates.
When to use it
Use it when an assistant should reason about a GitHub codebase without filesystem or shell access, for example repo onboarding briefs, PR-review preparation, or dependency and supply-chain audits across several repositories.
Requirements
A remote streamable-HTTP endpoint reached with an Apify API token sent as a bearer Authorization header; a free Apify account provides the token. An optional GitHub personal access token can be passed in tool arguments for higher rate limits and private repositories.
Before you install
The Apify token is a billable credential: calls cost $0.005 each after the free allowance, so usage spends money. An optional GitHub token passed in tool arguments gives access to private repositories and should be scoped narrowly. Repository data is sent to the hosted Apify service and on to the GitHub API. The server is read-only and cannot change repository state.

Installation

In SourceWeft

  1. Open GitHub Repository Intelligence in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.heisencodex-jpg%2Fgithub-repo-intel-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "github-repository-intelligence": {
      "type": "http",
      "url": "https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

GitHub Repository Intelligence MCP Server

A hosted Model Context Protocol server that gives AI coding agents structured intelligence about any GitHub repository — overview, recent PRs, contributors, hot files, CI status, and dependencies — through a single MCP endpoint.

No local setup. No git clone. No Octokit boilerplate. Plug your agent into the MCP URL and start asking questions.

Why this exists

Local GitHub MCP servers exist, but they require every user to set up Node/Python, install the server, manage tokens, and keep it patched. This Actor runs on Apify's platform and is reachable as a hosted streamable-HTTP MCP endpoint — your agent just needs the URL.

It's useful when you want an LLM to reason about a codebase without giving it filesystem or shell access: think code-review bots, repo-onboarding helpers, dependency-audit agents, refactor planners.

Hosted vs local — when this saves you time

This ActorLocal MCP server
SetupPaste URL + token into client configgit clone, install deps, manage Node/Python versions
DistributionSame URL works for every teammateEach teammate sets up their own
UpdatesAlways latest server buildYou patch + redeploy
Auth surfaceOne Apify token + optional GitHub PAT in tool argsGitHub PAT lives on every machine
Cost when idle$0 (Standby mode, billed per call)Whatever your laptop/server costs
When local winsAir-gapped repos, on-prem GitHub Enterprise—

Three workflows it shortens

  1. Repo onboarding — drop the URL into Claude Code, ask "give me a one-page brief on kubernetes/kubernetes: maintainers, top 10 hot files, current PR pipeline, CI health." One conversation, six tool calls, no clones.
  2. PR-review prep — before reviewing a stranger's PR, run get_contributors + list_recent_prs + get_hot_files on the target repo to know who you're dealing with and where the churn actually lives.
  3. Dependency / supply-chain audit — get_dependencies across a list of repos in a loop, no shell access required, no risk of malicious npm install running on your machine.

Tools exposed

ToolWhat it returnsTypical use
get_repo_overviewStars, forks, language, license, topics, last push"Is this repo still maintained?"
list_recent_prsRecent PRs with author, state, merge dates"Show me the last 20 merged PRs by user X"
get_contributorsTop contributors by commit count"Who maintains this project?"
get_hot_filesMost-modified files over the last N commits"Where's the churn?"
get_ci_statusCheck runs and conclusions for a ref"Is the default branch green?"
get_dependenciesParses package.json, requirements.txt, go.mod, Cargo.toml, pyproject.toml"What does this project depend on?"

Every tool accepts an optional github_token parameter. With no token you get GitHub's 60-req/hour limit on public repos. Provide a fine-grained PAT and you get 5,000 req/hour and can access private repos.

Pricing

$0.005 per tool call. First 100 calls free per user.

Pay-per-event model — you only pay when a tool actually executes. No subscription, no minimums. The server runs in Apify Standby mode, so you're not billed for idle time.

Usage

From an MCP-aware client (Claude Desktop, Cursor, Continue, etc.)

The Actor exposes a Streamable-HTTP MCP transport at:

https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp

Authentication uses your Apify token via the Authorization: Bearer <APIFY_TOKEN> header — most MCP clients let you configure this in their server config.

Example tool call (raw JSON-RPC)

bash
curl -X POST https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp \  -H "Authorization: Bearer <APIFY_TOKEN>" \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{    "jsonrpc": "2.0",    "id": 1,    "method": "tools/call",    "params": {      "name": "get_repo_overview",      "arguments": {"owner": "facebook", "repo": "react"}    }  }'

From Claude Desktop config

json
{  "mcpServers": {    "github-repo-intel": {      "url": "https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp",      "headers": {        "Authorization": "Bearer <APIFY_TOKEN>"      }    }  }}

Limits and caveats

  • Free tier on Apify gets you $5/month of usage credits — enough for ~1,000 free tool calls before the per-event price kicks in.
  • The get_hot_files tool scans up to 200 commits and makes one API call per commit, so it eats GitHub rate limit the fastest. Pass a github_token if you call it often.
  • get_ci_status reads the GitHub Checks API — it surfaces GitHub Actions, CodeQL, and any third-party check that posts back via the Checks API. Repos that run their CI entirely on external systems (Prow, Buildkite, CircleCI without GitHub integration) may show 0 check runs even when the build is green. The response includes a note field flagging this case.
  • This is a read-only server. It cannot create PRs, comment on issues, or modify any repository state.
  • All data comes straight from the GitHub REST API — no caching layer, so freshness equals what the GitHub API returns.

Source & roadmap

Author: luongnp. Open to feature requests — file an issue on the Actor page if you want a tool added (issues board, releases, dependency vulnerabilities via Dependabot API, etc.).

Source: README.md at commit d2f9e39

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.