# OpenGit (remote · opengit.cc)

Search agent-ready open source repos by task, interface, ecosystem and OG score.

- Trust score: 11/100 (low)
- Change this week: −45
- Registry status: active
- Liveness: degraded
- Owner verified: no
- Last scored: 2026-11-05

> **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

## Components

- remote · `opengit.cc`: 11/100 (this document), [markdown](https://verifymcp.io/servers/opengitteam-opengit-mcp/opengit.md), [page](https://verifymcp.io/servers/opengitteam-opengit-mcp/opengit)
- npm · `opengit-mcp`: 39/100, [markdown](https://verifymcp.io/servers/opengitteam-opengit-mcp/opengit-mcp.md), [page](https://verifymcp.io/servers/opengitteam-opengit-mcp/opengit-mcp)

## Channel facts

- Endpoint: `https://opengit.cc/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC not yet verified: we couldn't validate it against a resolver.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

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

### Claude

```bash
claude mcp add --transport http opengitteam-opengit-mcp 'https://opengit.cc/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "opengitteam-opengit-mcp": {
      "url": "https://opengit.cc/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "opengitteam-opengit-mcp": {
      "type": "http",
      "url": "https://opengit.cc/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.opengitteam-opengit-mcp]
url = "https://opengit.cc/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "opengitteam-opengit-mcp": {
      "type": "remote",
      "url": "https://opengit.cc/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add opengitteam-opengit-mcp --url 'https://opengit.cc/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  opengitteam-opengit-mcp:
    url: "https://opengit.cc/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "opengitteam-opengit-mcp": {
      "Transport": "http",
      "Url": "https://opengit.cc/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add opengitteam-opengit-mcp -t streamable-http -u 'https://opengit.cc/mcp'
```

### Other

```json
{
  "mcpServers": {
    "opengitteam-opengit-mcp": {
      "type": "http",
      "url": "https://opengit.cc/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 11, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-04 (score 23, −11)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-03 (score 34, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-02 (score 46, −11)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-31 (score 57, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] TLS certificate: pass → unverified
- [security regression] DNSSEC: fail → unverified
- [security regression] Stability: 0.10 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security improvement] HTTPS: fail → pass
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-30 (score 57, +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.

### 2026-10-28 (score 56, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-27 (score 55)

First indexed and scored.

## MCP tools (7)

### `search_repos` (~122 tokens)

Find agent-ready open source repos for a task. Returns repos ranked by match, then OG score.

Input parameters:

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

### `get_repo` (~58 tokens)

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

Input parameters:

- `name` (string, required)
- `owner` (string, required)

### `list_categories` (~20 tokens)

The categories in the OpenGit index, with repo counts.

### `list_ecosystems` (~32 tokens)

Chains and platforms in the OpenGit index (Solana, Base, Robinhood Chain), with repo counts.

### `tip_repo` (~143 tokens)

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.

Input parameters:

- `amount_usd` (number): Tip in US dollars
- `name` (string, required)
- `network` (string): Pin one chain; leave empty to offer all the repo supports
- `owner` (string, required)

### `list_builders` (~43 tokens)

Featured builders OpenGit highlights (for example Shaw, creator of elizaOS), the chains they build on and the repos they ship.

Input parameters:

- `ecosystem` (string)

### `trending` (~36 tokens)

Fastest-rising repos in the index, by stars gained this week.

Input parameters:

- `ecosystem` (string)
- `limit` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/opengitteam-opengit-mcp/opengit#diagnostics

## Score history

- 2026-11-05: 11
- 2026-11-04: 23
- 2026-11-03: 34
- 2026-11-02: 46
- 2026-11-01: 57
- 2026-10-31: 57
- 2026-10-30: 57
- 2026-10-29: 56
- 2026-10-28: 56
- 2026-10-27: 55

## Common questions

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

### What did VerifyMCP test on the OpenGit MCP server?

VerifyMCP ran 2 checks on OpenGit, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about OpenGit: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://opengit.cc/mcp
- Repository: https://github.com/opengitteam/opengit-mcp
- Website: https://opengit.cc/
- Changelog RSS feed: https://verifymcp.io/servers/opengitteam-opengit-mcp/opengit.xml
- Changelog JSON feed: https://verifymcp.io/servers/opengitteam-opengit-mcp/opengit/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/opengitteam-opengit-mcp/opengit.json
- HTML version of this page: https://verifymcp.io/servers/opengitteam-opengit-mcp/opengit