Is io.github.heisencodex-jpg/github-repo-intel-mcp safe to use?

io.github.heisencodex-jpg/github-repo-intel-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.heisencodex-jpg/github-repo-intel-mcp?

io.github.heisencodex-jpg/github-repo-intel-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.heisencodex-jpg/github-repo-intel-mcp?

io.github.heisencodex-jpg/github-repo-intel-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

io.github.heisencodex-jpg/github-repo-intel-mcp

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

GitHub

No known CVEs

No license

Maintenance unknown

No commit data

Works with most clients

Transport:

0 tools

Grade F

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

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

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-heisencodex-jpg-github-repo-intel-mcp-2)](https://mcppedia.org/s/io-github-heisencodex-jpg-github-repo-intel-mcp-2)

Read me

What io.github.heisencodex-jpg/github-repo-intel-mcp does

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.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

23/100across 5 weighted dimensions

How we score →

0255075100

−77

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.heisencodex-jpg/github-repo-intel-mcp safe to use?: io.github.heisencodex-jpg/github-repo-intel-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.heisencodex-jpg/github-repo-intel-mcp?: io.github.heisencodex-jpg/github-repo-intel-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.heisencodex-jpg/github-repo-intel-mcp?: io.github.heisencodex-jpg/github-repo-intel-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Similar servers

Others in other

View all →

Headroom95

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.

62.7k 3

Pi Lean Ctx94

Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.

3.4k 6

Sigmap94

97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server

606 6

Brigade93

One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.

62 5

MCP Security Weekly

Get CVE alerts and security updates for io.github.heisencodex-jpg/github-repo-intel-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

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

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-heisencodex-jpg-github-repo-intel-mcp-2)](https://mcppedia.org/s/io-github-heisencodex-jpg-github-repo-intel-mcp-2)

Read me

What io.github.heisencodex-jpg/github-repo-intel-mcp does

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

GitHub Repository Intelligence MCP Server

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 Actor	Local MCP server
Setup	Paste URL + token into client config	`git clone`, install deps, manage Node/Python versions
Distribution	Same URL works for every teammate	Each teammate sets up their own
Updates	Always latest server build	You patch + redeploy
Auth surface	One Apify token + optional GitHub PAT in tool args	GitHub PAT lives on every machine
Cost when idle	$0 (Standby mode, billed per call)	Whatever your laptop/server costs
When local wins	Air-gapped repos, on-prem GitHub Enterprise	—

Three workflows it shortens

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.
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.
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

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.

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)

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",
 

... [View full README on GitHub](https://github.com/heisencodex-jpg/github-repo-intel-mcp#readme)

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

23/100across 5 weighted dimensions

How we score →

0255075100

−77

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.heisencodex-jpg/github-repo-intel-mcp safe to use?: io.github.heisencodex-jpg/github-repo-intel-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.heisencodex-jpg/github-repo-intel-mcp?: io.github.heisencodex-jpg/github-repo-intel-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.heisencodex-jpg/github-repo-intel-mcp?: io.github.heisencodex-jpg/github-repo-intel-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Similar servers

Others in other

View all →

Headroom95

Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.

62.7k 3

Pi Lean Ctx94

Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.

3.4k 6

Sigmap94

97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server

606 6

Brigade93

One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.

62 5

MCP Security Weekly

Get CVE alerts and security updates for io.github.heisencodex-jpg/github-repo-intel-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?