Verdoc

io.github.verdochelloPublished by GitHub account verdochellov0.1.0Updated Nov 3, 2026

Deterministic AGENTS.md and repo analysis for coding agents, paid per call in USDC over x402.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Generates AGENTS.md files and structured repo analysis for coding agents, paid per call in USDC over x402.

What you can do
  • Produce a ready-to-commit AGENTS.md for a public GitHub repository
  • Return the same analysis as structured JSON
  • Quote build and test commands from the repository's own manifests, naming the source file
  • Verify paths against the git tree and mark ambiguous findings as unverified
  • Run in quote-only mode to preview cost and output without paying
When to use it
Useful when a coding agent is dropped into an unfamiliar public repository and would otherwise spend many tokens reading it first. It suits teams that want deterministic, repeatable repository context and are willing to pay a few cents per call in USDC.
Requirements
Runs locally over stdio, typically as the bundled .mcpb file or via npx from the GitHub repository (Node.js). Needs a wallet with USDC on Base, Polygon or Arbitrum in EVM_PRIVATE_KEY to actually buy results; without it the server runs quote-only. VERDOC_MAX_SPEND_USD sets the per-call ceiling (default 0.05). Network access to the Verdoc endpoint is required.
Before you install
EVM_PRIVATE_KEY gives the server the ability to spend from that wallet, so use a dedicated, low-balance wallet. Each paid call costs $0.01 or $0.02, capped by VERDOC_MAX_SPEND_USD. Only public GitHub repositories are supported, and repositories over 20,000 tracked files are rejected. The README states the key is never logged, written to disk or transmitted except as a payment signature, and that payee and chain are pinned in source.

Installation

In SourceWeft

  1. Open Verdoc in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

verdoc-mcp

Give your coding agent the context of a repository it has never seen, for two cents, without an account or an API key.

An agent dropped into an unfamiliar codebase has to read it before it can work in it - and that costs tens of thousands of tokens every time. verdoc-mcp exposes two tools that answer the same questions directly:

toolwhat you getprice
verdoc_agents_mdan AGENTS.md ready to commit$0.02
verdoc_scanthe same analysis as structured JSON$0.01

Build and test commands are quoted from the repository's own manifests, with the file each one came from named. Every path is checked against the git tree. Anything ambiguous is marked unverified rather than guessed.

No language model runs on the server. The same commit always returns the same answer.

Install

Easiest: download the .mcpb bundle and drag it into Claude Desktop, or point any MCPB-aware client at it directly - dependencies are bundled inside, nothing to install separately.

Not on npm yet. Two other ways to install straight from this repository:

json
{  "mcpServers": {    "verdoc": {      "command": "npx",      "args": ["-y", "github:verdochello/verdoc-mcp"],      "env": { "EVM_PRIVATE_KEY": "0x..." }    }  }}

Or clone it and point at the file directly:

bash
git clone https://github.com/verdochello/verdoc-mcp && cd verdoc-mcp && npm install
json
{  "mcpServers": {    "verdoc": {      "command": "node",      "args": ["/absolute/path/to/verdoc-mcp/index.mjs"],      "env": { "EVM_PRIVATE_KEY": "0x..." }    }  }}

Works with Claude Desktop, Claude Code, Cursor, or any MCP client.

Without a key it still runs. The tools report what they would cost and what they would return, and buy nothing. That is the intended way to try it.

Paying

The wallet needs USDC on Base, Polygon or Arbitrum. It does not need ETH - x402 payments are signed off-chain and the facilitator pays the gas.

variabledefaultmeaning
EVM_PRIVATE_KEY-wallet that pays. Omit to run in quote-only mode.
VERDOC_MAX_SPEND_USD0.05hard per-call ceiling. Nothing above it is ever signed.
VERDOC_ORIGINhttps://verdoc.devoverride the endpoint (testing).

About that private key

You are handing a program the ability to spend your money, so here is exactly what this one does and does not do.

  • The key is read from the environment. It is never logged, never written to disk, and never sent anywhere. Error messages are scrubbed of anything that looks like a key before being returned.
  • The payee and the chain are pinned in the source. Before signing anything, the client reads the live payment offer and checks it. If Verdoc ever asks to be paid at a different address, or on a chain not in the list, this refuses and tells you instead of paying. That means a compromise of our own domain or DNS cannot redirect your funds.
  • Every call is capped by VERDOC_MAX_SPEND_USD, checked before a signature exists.

Use a wallet you funded for this purpose. That is good practice with any paying agent tool, including this one.

What it will refuse to do

These are tested in selftest.mjs, and the refusals are the part worth reading:

  • pay an address other than the pinned one - even if the live endpoint asks
  • pay on a chain outside the pinned set, including testnets
  • pay more than your ceiling
  • treat a short or empty 200 response as a real answer

Limits

Public GitHub repositories only. Repositories over 20,000 tracked files are rejected: GitHub truncates the git tree above that, and every claim this service makes depends on having the complete tree.

Licence

MIT. The service it calls is at verdoc.dev - OpenAPI | x402 discovery

Source: README.md at commit 6972228

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts