io.github.crypto-ninja/github-mcp-server

MCPcommunity
v2.5.7io.github.crypto-ninjaUnknownUpdated 9mo agoGitHub

AI-optimized GitHub MCP server: 112 tools, 98% token reduction, compact responses.

[](#-available-tools) The most comprehensive GitHub MCP server - Full GitHub workflow automation with Actions monitoring, advanced PR management, intelligent code search, and complete file management. Built for AI-powered development teams. 👉 New here? See the Quick Start Guide This server is designed with AI agents in mind: Format | Use Case | Token Savings |…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4GitHub stars
9mo agoLast update
Package
Authorio.github.crypto-ninja
LicenseUnknown
Version2.5.7
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface1 tool · none privileged
Security scan✓ Cleanv2.5.7 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

1 tool · none privileged
Statically extracted from the published packagev2.5.7 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

my-new-repoNo description published

This tool published no description. Forge does not invent one.

0 of 1 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

[](#-available-tools) The most comprehensive GitHub MCP server - Full GitHub workflow automation with Actions monitoring, advanced PR management, intelligent code search, and complete file management. Built for AI-powered development teams. 👉 New here? See the Quick Start Guide This server is designed with AI agents in mind: Format | Use Case | Token Savings | --------|----------|---------------| | Discovery, lists, status checks | 80-97% smaller | | Full details when needed | Full response |…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.

Topics

Related in git & code hosting