A
licenseA
qualityC
maintenanceSearch 21 sources in one call — GitHub, npm, PyPI, arXiv, HN, X, Reddit, and more. No API keys to juggle, structured JSON back.
21
29
1
MIT
GitHits
by com.githits
Ownership verified
Server Details
Search public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- githits-com/githits-cli
- GitHub Stars
- 77
- Server Listing
- GitHits
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.7/5 across 15 of 15 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool targets a distinct action: code_files lists, code_read reads, code_grep greps, docs_list/docs_read handle docs, pkg_* tools cover distinct package metadata aspects, and search/get_example/search_status are clearly separated by use case. Even the three search-related tools are clearly scoped to different needs.
Naming Consistency2/5
Names are all lowercase snake_case but follow inconsistent patterns: code_read, docs_list are object-first verbs, whereas get_example and search_language are imperative verb-object, and pkg_info or feedback are noun-only. The prefixes (code_, docs_, pkg_, search_) help, but the mix of verb placement and noun-only names makes the set feel less coherent.
Tool Count5/5
15 tools is on the high end but well-scoped for a comprehensive code/package intelligence server. Each tool covers a distinct facet of the domain without redundancy, and the count does not feel padded.
Completeness5/5
The tool surface covers the full lifecycle for the domain: searching, listing, reading files, browsing docs, checking package metadata/deps/vulnerabilities/release notes, and getting examples. There is also feedback and async search follow-up, so no obvious dead ends or missing operations.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceEnables AI assistants to search documentation of packages and services to find implementation details, examples, and specifications.MIT
- AlicenseAqualityDmaintenanceProvides natural language search capabilities for Spryker GitHub repositories, packages, and public documentation. It enables code-level searches across Spryker organizations to help developers find relevant modules and technical information.3MIT
- Flicense-qualityCmaintenanceSemantic search over local source repositories and forum archives, exposing tools to list sources, search code, read code, and search forum discussions.
Try in Browser
Your Connectors
Sign in to create a connector for this server.