Git.Top
REMOTE · GIT.TOP · SCANNED SEP 20
Evidence-backed open-source project search, recommendations, alternatives, and comparisons.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Git.Top MCP server?
Git.Top is a hosted endpoint at https://git.top/mcp/core, 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 · git.top
claude mcp add --transport http haocn-ops-git-top 'https://git.top/mcp/core'
{
"mcpServers": {
"haocn-ops-git-top": {
"url": "https://git.top/mcp/core"
}
}
} {
"servers": {
"haocn-ops-git-top": {
"type": "http",
"url": "https://git.top/mcp/core"
}
}
} [mcp_servers.haocn-ops-git-top] url = "https://git.top/mcp/core"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"haocn-ops-git-top": {
"type": "remote",
"url": "https://git.top/mcp/core",
"enabled": true
}
}
} openclaw mcp add haocn-ops-git-top --url 'https://git.top/mcp/core' --transport streamable-http
mcp_servers:
haocn-ops-git-top:
url: "https://git.top/mcp/core" {
"McpServers": {
"haocn-ops-git-top": {
"Transport": "http",
"Url": "https://git.top/mcp/core"
}
}
} assistant mcp add haocn-ops-git-top -t streamable-http -u 'https://git.top/mcp/core'
{
"mcpServers": {
"haocn-ops-git-top": {
"type": "http",
"url": "https://git.top/mcp/core"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Sept 26 0
- “get_project” added an optional parameter “project” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 30 Aug 26 0
- Stability: 0.97 → pass security
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 0
- Schema quality: unverified → good ▲ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Sept 2026 · Probed https://git.top/mcp/core
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=git.top | CN=WE1,O=Google Trust Services,C=US | 19 Aug 2026 | 17 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 34bbb0a1221796c813de92e9509cf87b |
| SANs: git.top, www.git.top, *.www.git.top | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of git.top. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| top. | present | 26780 | 8 | Verified |
| git.top. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; connect-src 'self'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; base-uri 'self'; form-action 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://git.top/mcp/core | Verified | 200 | |
| http (plaintext) | http://git.top/mcp/core | HTTPS enforced | 301 | https://git.top/mcp/core |
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 →
compare_projects ~72
Compare projects by deployment, maintenance, difficulty, Cloudflare readiness, and use case fit.
| Name | Type | Req | Description |
|---|---|---|---|
| criteria | array | – | – |
| deployment | string | – | – |
| project_ids | array | yes | – |
| require_d1 | boolean | – | Fail closed unless the tool result is backed by D1 instead of seed fallback. |
No output schema declared.
No examples provided.
get_agent_workflow ~112
Return a structured Git.Top workflow that guides an agent from trends to recommendations, graph, alternatives, score, compare, and trust checks.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_project ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
recommend_project ~67
Recommend open source projects for a concrete agent use case and constraints.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | object | – | – |
| limit | integer | – | – |
| require_d1 | boolean | – | Fail closed unless the tool result is backed by D1 instead of seed fallback. |
| use_case | string | yes | – |
No output schema declared.
No examples provided.
search_projects ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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).
Is the Git.Top MCP server safe to use?
Git.Top scores 83 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.