# Git.Top (remote · git.top)

Evidence-backed open-source project search, recommendations, alternatives, and comparisons.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-07

## Components

- remote · `git.top`: 71/100 (this document), [markdown](https://verifymcp.io/servers/haocn-ops-git-top/mcp-core-source-mcp-registry.md), [page](https://verifymcp.io/servers/haocn-ops-git-top/mcp-core-source-mcp-registry)

## Channel facts

- Endpoint: `https://git.top/mcp/core/source/mcp-registry?source=mcp-registry`
- 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-10-07.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 660 tokens (~132/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 52% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Git.Top MCP server?

Git.Top is a hosted endpoint at https://git.top/mcp/core/source/mcp-registry?source=mcp-registry, 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 haocn-ops-git-top 'https://git.top/mcp/core/source/mcp-registry?source=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "haocn-ops-git-top": {
      "url": "https://git.top/mcp/core/source/mcp-registry?source=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "haocn-ops-git-top": {
      "type": "http",
      "url": "https://git.top/mcp/core/source/mcp-registry?source=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.haocn-ops-git-top]
url = "https://git.top/mcp/core/source/mcp-registry?source=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "haocn-ops-git-top": {
      "type": "remote",
      "url": "https://git.top/mcp/core/source/mcp-registry?source=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add haocn-ops-git-top --url 'https://git.top/mcp/core/source/mcp-registry?source=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  haocn-ops-git-top:
    url: "https://git.top/mcp/core/source/mcp-registry?source=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "haocn-ops-git-top": {
      "Transport": "http",
      "Url": "https://git.top/mcp/core/source/mcp-registry?source=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add haocn-ops-git-top -t streamable-http -u 'https://git.top/mcp/core/source/mcp-registry?source=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "haocn-ops-git-top": {
      "type": "http",
      "url": "https://git.top/mcp/core/source/mcp-registry?source=mcp-registry"
    }
  }
}
```

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-10-07 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 13. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-04 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-03 (score 69)

First indexed and scored.

## MCP tools (5)

### `search_projects` (~208 tokens)

Search Git.Top projects by query, category, deployment, difficulty, language, or Cloudflare readiness. Results include project_kind and collection_metadata for resource hubs and curated collections. On large corpora, inspect metadata.candidate_retrieval and metadata.truncated before treating broad results as exhaustive.

Input parameters:

- `category` (string)
- `cloudflare_ready` (boolean)
- `cursor` (string): Opaque next_cursor from a previous search_projects result.
- `deployment` (string)
- `difficulty` (string)
- `language` (string)
- `limit` (integer)
- `query` (string): Search terms, such as openai, cloudflare agent framework, or browser automation. Leave cursor empty for a new search.
- `ranking` (string): Optional browse ranking for broad category/deployment discovery with larger limits. Defaults to exact-intent search ranking.
- `require_d1` (boolean): Fail closed unless the tool result is backed by D1 instead of seed fallback.

### `get_project` (~170 tokens)

Return structured Git.Top knowledge for a project or collection, including the compact agent summary, overview, alternatives, deployments, quality score, agent score, project_kind, and collection_metadata when applicable.

Input parameters:

- `owner` (string): GitHub owner; use with repo when project_id is omitted.
- `project` (string): Alias for project_id; accepts a canonical owner/repo identifier or Git.Top product alias.
- `project_id` (string): Canonical owner/repo identifier or a Git.Top product alias such as claude-code or cursor. The repo field may also contain owner/repo.
- `repo` (string): GitHub repository name, or owner/repo when owner is omitted.
- `require_d1` (boolean): Fail closed unless the tool result is backed by D1 instead of seed fallback.

### `recommend_project` (~67 tokens)

Recommend open source projects for a concrete agent use case and constraints.

Input parameters:

- `constraints` (object)
- `limit` (integer)
- `require_d1` (boolean): Fail closed unless the tool result is backed by D1 instead of seed fallback.
- `use_case` (string, required)

### `get_agent_workflow` (~112 tokens)

Return a structured Git.Top workflow that guides an agent from trends to recommendations, graph, alternatives, score, compare, and trust checks.

Input parameters:

- `constraints` (object)
- `intent` (string): Natural-language selection goal.
- `limit` (integer)
- `project_id` (string): Optional focus project or product alias.
- `require_d1` (boolean): Fail closed unless the tool result is backed by D1 instead of seed fallback.
- `use_case` (string): Concrete project use case.

### `compare_projects` (~72 tokens)

Compare projects by deployment, maintenance, difficulty, Cloudflare readiness, and use case fit.

Input parameters:

- `criteria` (array)
- `deployment` (string)
- `project_ids` (array, required)
- `require_d1` (boolean): Fail closed unless the tool result is backed by D1 instead of seed fallback.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/haocn-ops-git-top/mcp-core-source-mcp-registry#diagnostics

## Score history

- 2026-10-07: 71
- 2026-10-04: 70
- 2026-10-03: 69

## Common questions

### What is the Git.Top MCP server?

Git.Top is an MCP server listed in the public MCP registry as io.github.haocn-ops/git-top. Evidence-backed open-source project search, recommendations, alternatives, and comparisons. This page covers its hosted endpoint (https://git.top/mcp/core/source/mcp-registry?source=mcp-registry).

### Is the Git.Top MCP server safe to use?

Git.Top scores 71 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 Git.Top MCP server expose?

Git.Top exposes 5 tools: search_projects, get_project, recommend_project, get_agent_workflow, compare_projects. Their descriptions and schemas cost roughly 629 tokens of context every time the server is loaded.

### Does the Git.Top MCP server require authentication?

No. We connected to Git.Top without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Git.Top MCP server still maintained?

Git.Top is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://git.top/mcp/core/source/mcp-registry?source=mcp-registry
- Repository: https://github.com/haocn-ops/git-top
- Website: https://git.top/connect?source=mcp-registry
- Changelog RSS feed: https://verifymcp.io/servers/haocn-ops-git-top/mcp-core-source-mcp-registry.xml
- Changelog JSON feed: https://verifymcp.io/servers/haocn-ops-git-top/mcp-core-source-mcp-registry.json
- HTML version of this page: https://verifymcp.io/servers/haocn-ops-git-top/mcp-core-source-mcp-registry