Git.Top

REMOTE · GIT.TOP · SCANNED AUG 3

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

Available components

65 65 Trust /100

Trust breakdown (6 categories)

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 →

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 Usability53

AI-judged instruction clarity (fair).Partial
Context-footprint check failed: tool/resource definitions use about 636 tokens (~127/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 Management10

Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage83

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
50% of tool parameters carry a description.Partial

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · git.top

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http haocn-ops-git-top https://git.top/mcp/core

# ~/.codex/config.toml

[mcp_servers.haocn-ops-git-top]
url = "https://git.top/mcp/core"

// opencode.json

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

# add to OpenClaw

openclaw mcp add haocn-ops-git-top --url https://git.top/mcp/core --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  haocn-ops-git-top:
    url: "https://git.top/mcp/core"

// mcp.json

{
  "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.

Changelog Show cosmetic changes

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.

2 Aug 26 +1
- “search_projects” reworded the description of “query” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
1 Aug 26 +7
- Authorization: unverified → partial ▲ security
- Stability: unverified → 0.03 ▲ functional
31 Jul 26 57

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 3 Aug 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	21 Jun 2026	19 Sept 2026	ECDSA 256	ECDSA-SHA256	f4814a6bbe858de80ec0bfe945b5f54c
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

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=()

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

MCP tools — 5 exposed · ~605 tokens

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.

Tool Tokens

compare_projects ~72

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

Input Output Examples

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.

Input Output Examples

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 ~146

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 Output Examples

Name	Type	Req	Description
owner	string	—	GitHub owner; use with repo when project_id is omitted.
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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

31 Jul 3 Aug