Verdoc
MCPB · VERDOC-MCP-0.1.0.MCPB
Deterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402.
Available components
Last scanned (23 hours ago)
Scores higher than 98% of MCPB servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security24
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 109 of 109 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 82 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 241 tokens (~120/item across 2 items; 2 tools + 0 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 +1
- Stability: 0.97 → pass security
- 23 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −3
- Stability: pass → 0.83 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 4 Nov 2026 · Analysed mcpb/https://github.com/verdochello/verdoc-mcp/releases/download/v0.1.0/verdoc-mcp-0.1.0.mcpb@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 109 packages
| Packages resolved | 109 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
verdoc_agents_md ~138
Generate an AGENTS.md for a public GitHub repository: build and test commands quoted from the repository's own manifests with the source file named, a directory map, entry points and edit boundaries. Every path is checked against the git tree and anything ambiguous is marked unverified rather than guessed. Use this before working in a repository you do not already know. Costs $0.02 in USDC from the configured wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | 'markdown' returns the file ready to write to disk; 'json' adds provenance. |
| repo | string | yes | Public GitHub repository as owner/name, or a github.com URL. |
No output schema declared.
No examples provided.
verdoc_scan ~103
Structured facts about a public GitHub repository: toolchain commands with the manifest each was quoted from, directory layout, language split, CI and test presence, a 0-100 documentation-health score, and phantom_paths - paths the README cites that do not exist in the git tree. Deterministic; no language model. Costs $0.01 in USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | Public GitHub repository as owner/name, or a github.com URL. |
No output schema declared.
No examples provided.
How do I install the Verdoc MCP server?
Verdoc ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · verdoc-mcp-0.1.0.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the Verdoc MCP server?
Verdoc is an MCP server listed in the public MCP registry as io.github.verdochello/verdoc-mcp. Deterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402. This page covers its MCPB bundle (https://github.com/verdochello/verdoc-mcp/releases/download/v0.1.0/verdoc-mcp-0.1.0.mcpb).
Is the Verdoc MCP server safe to use?
Verdoc scores 63 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 Verdoc MCP server expose?
Verdoc exposes 2 tools: verdoc_agents_md, verdoc_scan. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
What licence is the Verdoc MCP server under?
Verdoc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.