Integrations

Use Git.Top as project intelligence inside agents and developer tools.

Git.Top exposes the same project knowledge through REST, MCP, and GRP. Use it when an agent needs to choose open-source AI projects by deployment fit, alternatives, quality signals, data confidence, and graph context.

Connect an agent Start quickstart Inspect MCP discovery OpenAPI Production status

REST/api/*

Search, project lookup, recommendation, comparison, graph, quality, and schemas.

MCP core/mcp/core

Five-tool first-use profile for project search and selection.

GRP/api/grp/query

Goal-level graph reasoning for plans, project sets, comparisons, and stacks.

Trust/status

D1 source, sync freshness, quality, and corpus coverage checks.

REST

Embed direct project intelligence

curl "https://git.top/api/search?q=cloudflare%20agent&limit=5"
curl "https://git.top/api/project/cloudflare/agents"
curl "https://git.top/api/compare?repos=cloudflare/agents,langchain-ai/langchain&deployment=cloudflare"

Best for product UIs, API clients, dashboards, and workflows that want typed HTTP responses.

MCP

Install as an agent tool source

curl -X POST https://git.top/mcp \
  -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Best for clients that already speak Model Context Protocol and want tool schemas before calling.

GRP

Ask for graph-grounded plans

curl -X POST https://git.top/api/grp/query \
  -H "content-type: application/json" \
  -d '{"goal":"build a Cloudflare-ready coding agent stack","mode":"plan","constraints":{"deploy":["cloudflare"]}}'

Best for higher-level planning where relationships, roles, alternatives, and deployment fit matter together.

Production Checklist

Checks before citing a recommendation

Confirm source metadata.Use /status or /api/health and prefer metadata.source=d1.

Inspect confidence evidence.Use project classification and quality_signal_confidence before presenting quality scores as authoritative.

Check corpus fit.Use /coverage when the user's task depends on broad category representation.

Fail closed when needed.Use require_d1=true on REST knowledge endpoints when seed fallback is not acceptable.

Boundaries

What Git.Top is not

Not a generic GitHub leaderboard.Ranking is tuned for agent project selection, not raw popularity.

Not private repository indexing yet.The public site covers open-source repositories in the current V1 taxonomy.

Not a compliance certification source.Use Git.Top as structured discovery and evidence, then verify licenses, security, and deployment requirements directly.