mcpField
V
Verdoc

Verdoc

Local
verdoc.devDeveloper Tools1Updated 11w ago

About Verdoc

Verdoc analyzes public GitHub repositories and provides coding agents with an AGENTS.md file or structured repository data. Its results quote build and test commands from manifests, verify paths against the git tree, and remain deterministic for a given commit.

Key features

  1. 01Generate an AGENTS.md file
  2. 02Return repository analysis as JSON
  3. 03Quote build and test commands from manifests
  4. 04Check paths against the git tree
  5. 05Mark ambiguous findings as unverified
  6. 06Use quote-only mode without a wallet key

Use cases

  1. 01Prepare context for an agent entering an unfamiliar repository
  2. 02Create a repository-specific AGENTS.md
  3. 03Inspect build and test commands with source files
  4. 04Try a call and view its cost without paying

MCP support

Verdoc exposes repository analysis through two MCP tools: one generates AGENTS.md and the other returns structured JSON. Calls use x402 payments in USDC when a wallet key is configured; without one, the tools run in quote-only mode.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
mcpbverdoc-mcp-0.1.0.mcpb0.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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:

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

Or clone it and point at the file directly:

git clone https://github.com/verdochello/verdoc-mcp && cd verdoc-mcp && npm install
{
  "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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.