CodeWiki MCP — AI-generated docs for GitHub repos
MCP server for codewiki.google — search, fetch docs, and ask questions about any open-source repo
Compare CodeWiki MCP — AI-generated docs for GitHub repos
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →Thin or incomplete trust evidence. Review carefully before production use.
Is CodeWiki MCP — AI-generated docs for GitHub repos safe? CodeWiki MCP — AI-generated docs for GitHub repos scores 18.7/100 (Grade D), ranked #1130 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 22% of recent commits are signed; last pushed 2026-06-22. Every point is earned from checkable signals — never paid placement. How scoring works →
Ranked neighbours in MCP Servers
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
HVTrust Dimensions vs MCP Servers
18.7 / 100 · 40.0% confidenceCodeWiki MCP — AI-generated docs for GitHub repos MCP Servers average (761 agents)
Activity Inputs
26.6 / 100Supply Chain Trust
Is CodeWiki MCP — AI-generated docs for GitHub repos safe?
Does CodeWiki MCP — AI-generated docs for GitHub repos publish package provenance?
Does CodeWiki MCP — AI-generated docs for GitHub repos have an OpenSSF Scorecard?
Is CodeWiki MCP — AI-generated docs for GitHub repos actively maintained?
What license does CodeWiki MCP — AI-generated docs for GitHub repos use?
Are CodeWiki MCP — AI-generated docs for GitHub repos's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain CodeWiki MCP — AI-generated docs for GitHub repos?
For maintainers
HVTrust scores CodeWiki MCP — AI-generated docs for GitHub repos from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/codewiki-mcp-ai-generated-docs-for-github-repos)
<a href="https://hvtracker.net/agents/codewiki-mcp-ai-generated-docs-for-github-repos"><img src="https://hvtracker.net/badge/codewiki-mcp-ai-generated-docs-for-github-repos.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON