OpenGit
REMOTE · OPENGIT.CC · 2 COMPONENTS
Search agent-ready open source repos by task, interface, ecosystem and OG score.
Available components
Last scanned (14 hours ago)
Scores higher than 4% of remote servers
Unreachable for 6 days in a row. Last reached 30 Oct 2026.
Category Code Search and Documentation
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Nov 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Nov 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Nov 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- TLS certificate: pass → unverified ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: fail → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://opengit.cc/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of opengit.cc. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| opengit.cc. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://opengit.cc/mcp | Unreachable | ||
| http (plaintext) | http://opengit.cc/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_repo ~58
Details for one repo: description, interfaces, stars, OG score, links, and the maintainer's payout address if the repo is claimed (from its opengit.json).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| owner | string | yes | – |
No output schema declared.
No examples provided.
list_builders ~43
Featured builders OpenGit highlights (for example Shaw, creator of elizaOS), the chains they build on and the repos they ship.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | – |
No output schema declared.
No examples provided.
list_categories ~20
The categories in the OpenGit index, with repo counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_ecosystems ~32
Chains and platforms in the OpenGit index (Solana, Base, Robinhood Chain), with repo counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_repos ~122
Find agent-ready open source repos for a task. Returns repos ranked by match, then OG score.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| claimed | boolean | – | Only repos whose maintainer has claimed them (they have a payout address you can tip or pay) |
| ecosystem | string | – | Only repos for this chain or platform |
| interface | string | – | Only repos an agent can use this way |
| limit | number | – | – |
| query | string | – | What you need, e.g. "decompile an APK" or "security audit" |
No output schema declared.
No examples provided.
tip_repo ~143
Get an x402 link that tips a claimed repo's maintainer. Request the link with any x402 client or wallet: it answers 402 Payment Required with options on Robinhood Chain (USDG), Base (USDC) and Solana (USDC), and payment goes straight to the maintainer's address from the repo's opengit.json. OpenGit takes nothing. Use it to tip the open source tools you rely on.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | – | Tip in US dollars |
| name | string | yes | – |
| network | string | – | Pin one chain; leave empty to offer all the repo supports |
| owner | string | yes | – |
No output schema declared.
No examples provided.
trending ~36
Fastest-rising repos in the index, by stars gained this week.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
How do I install the OpenGit MCP server?
OpenGit is a hosted endpoint at https://opengit.cc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · opengit.cc
claude mcp add --transport http opengitteam-opengit-mcp 'https://opengit.cc/mcp'
What is the OpenGit MCP server?
OpenGit is an MCP server listed in the public MCP registry as io.github.opengitteam/opengit-mcp. Search agent-ready open source repos by task, interface, ecosystem and OG score. This page covers its hosted endpoint (https://opengit.cc/mcp).
Is the OpenGit MCP server safe to use?
OpenGit scores 11 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OpenGit MCP server expose?
OpenGit exposes 7 tools: search_repos, get_repo, list_categories, list_ecosystems, tip_repo, and 2 more. Their descriptions and schemas cost roughly 454 tokens of context every time the server is loaded.
Does the OpenGit MCP server require authentication?
Its publisher declares no required credentials for OpenGit. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the OpenGit MCP server still maintained?
OpenGit is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 30 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.