A
licenseC
qualityA
maintenanceMCP server for gittr.space, a decentralized Git platform on Nostr, enabling AI agents to create repos, push code, manage issues/PRs, and work with Lightning bounties using Nostr identity.
75
1
MIT
gitbeacon-mcp
by jcislo
Related Servers
Alternatives to gitbeacon-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP (Model Context Protocol) server for GitHub API integration. This server provides comprehensive tools for interacting with GitHub repositories, issues, pull requests, branches, and code search through a unified interface.155 npmMIT
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server for querying GitHub repository analytics from OSSInsight, providing repo metadata, trending repos, curated collections, search, compare, and collection rankings without an API key.61MIT
- AlicenseBqualityCmaintenanceMCP server that exposes GitHub operations as tools for AI agents, enabling code search, issue management, and PR review.12MIT
- FlicenseCqualityCmaintenanceMCP server that enables LLMs to search GitHub, clone repositories, and perform read-only git/GitHub operations such as listing branches, commits, issues, and pull requests.25-
- AlicenseAqualityBmaintenanceMCP server that enables AI assistants to look up and analyze GitHub repositories, including stars, forks, description, open issues, and README content.244 npmMIT
TDQS
A4.1/5.0
Scored across 6 tools
Disambiguation4/5
Tools like get_brief, get_latest_digest, and get_digests all handle digests, but descriptions clearly distinguish current/full/historical. The only potential confusion is between get_brief and get_latest_digest; however, the 'brief' vs 'full' wording resolves it.
Naming Consistency5/5
All tools follow the exact same get_<noun> pattern in lowercase snake_case with no deviations. This is a perfectly consistent naming convention.
Tool Count5/5
Six tools is well within the optimal range (3-15) and each tool serves a distinct purpose without unnecessary bloat. The count is well-scoped for the API's domain.
Completeness4/5
The surface covers the core digest workflow: index for polling, brief/latest for current data, digests for history, repos for trending, and sample for testing. A possible gap is the lack of a fetch-by-ID endpoint, but core operations are covered.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive