Server data from the Official MCP Registry
Repo intel for AI coding agents: overview, PRs, contributors, hot files, CI, deps. Remote MCP.
Repo intel for AI coding agents: overview, PRs, contributors, hot files, CI, deps. Remote MCP.
Remote endpoints: streamable-http: https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp
This is a well-structured MCP server for querying GitHub repository metadata through a hosted endpoint. Authentication is properly implemented via Apify tokens and optional GitHub PATs. The code has good error handling, input validation with Zod, and appropriate rate-limit awareness. Minor concerns include overly broad CORS configuration and lack of explicit request logging for audit trails, but these do not represent security vulnerabilities. Permissions align with the server's read-only GitHub intelligence purpose. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 3 high severity).
5 files analyzed · 8 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
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.
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.
| Tool | What it returns | Typical use |
|---|---|---|
get_repo_overview | Stars, forks, language, license, topics, last push | "Is this repo still maintained?" |
list_recent_prs | Recent PRs with author, state, merge dates | "Show me the last 20 merged PRs by user X" |
get_contributors | Top contributors by commit count | "Who maintains this project?" |
get_hot_files | Most-modified files over the last N commits | "Where's the churn?" |
get_ci_status | Check runs and conclusions for a ref | "Is the default branch green?" |
get_dependencies | Parses 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.
$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.
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.
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"}
}
}'
{
"mcpServers": {
"github-repo-intel": {
"url": "https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp",
"headers": {
"Authorization": "Bearer <APIFY_TOKEN>"
}
}
}
}
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.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.).
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.