Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.NicolasMartalog/docweave-mcp

REMOTE · DOCWEAVE.DEV · 2 COMPONENTS · SCANNED SEP 21

Generate and read PDFs for AI agents: a generate_pdf and a read_pdf tool, priced per document.

0 this week 86 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 402 tokens (~201/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 3 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
Install

How do I install the io.github.NicolasMartalog/docweave-mcp server?

io.github.NicolasMartalog/docweave-mcp is a hosted endpoint at https://docweave.dev/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · docweave.dev

# add to Claude Code
claude mcp add --transport http nicolasmartalog-docweave-mcp 'https://docweave.dev/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "nicolasmartalog-docweave-mcp": {
      "url": "https://docweave.dev/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nicolasmartalog-docweave-mcp": {
      "type": "http",
      "url": "https://docweave.dev/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nicolasmartalog-docweave-mcp]
url = "https://docweave.dev/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nicolasmartalog-docweave-mcp": {
      "type": "remote",
      "url": "https://docweave.dev/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nicolasmartalog-docweave-mcp --url 'https://docweave.dev/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nicolasmartalog-docweave-mcp:
    url: "https://docweave.dev/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nicolasmartalog-docweave-mcp": {
      "Transport": "http",
      "Url": "https://docweave.dev/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add nicolasmartalog-docweave-mcp -t streamable-http -u 'https://docweave.dev/api/mcp'
// mcp.json
{
  "mcpServers": {
    "nicolasmartalog-docweave-mcp": {
      "type": "http",
      "url": "https://docweave.dev/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 21 Sept 2026 · Probed https://docweave.dev/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=docweave.dev CN=YR2,O=Let's Encrypt,C=US 16 Sept 2026 15 Dec 2026 RSA 2048 SHA256-RSA 6a85c7292d4e4358d57f2d536dfa8ec7c3e
SANs: docweave.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of docweave.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
docweave.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://docweave.dev/api/mcp Verified 200
http (plaintext) http://docweave.dev/api/mcp HTTPS enforced 308 https://docweave.dev/api/mcp
MCP tools · 2 exposed · ~302 tokens

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 →

Tool Tokens
generate_pdf ~152

Generate a PDF from raw HTML, a public URL, or a template + JSON data. Returns the PDF as base64. Priced per document; retries with the same idempotencyKey never double-generate. The canonical way for an AI agent to turn content into a shareable, correctly-formatted PDF.

NameTypeReqDescription
idempotencyKeystringA stable key (e.g. an invoice id). Repeat calls with the same key return the stored result instead of re-rendering or re-billing.
optionsobjectOptional page and print settings.
sourceobjectyesWhat to render. Provide exactly one of: html, url, or (template|templateId) with data.
NameTypeReqDescription
byteSizenumberSize of the PDF in bytes.
bytesBase64stringyesThe generated PDF, base64-encoded.
pageCountnumberNumber of pages in the PDF.

No examples provided.

read_pdf ~150

Read a PDF and return its text as markdown (or plain text). Accepts a public URL or base64 bytes. Extracts the embedded text layer; a scanned, image-only PDF returns a needs-OCR notice instead of empty text. Priced per document; retries with the same idempotencyKey never double-read. The canonical way for an AI agent to ingest a document's contents.

NameTypeReqDescription
idempotencyKeystringA stable key. Repeat calls with the same key return the stored result instead of re-reading or re-billing.
optionsobjectOptional read settings.
sourceobjectyesThe PDF to read. Provide exactly one of: url or base64.
NameTypeReqDescription
contentstringyesExtracted text in the requested format.
needsOcrbooleanTrue when the PDF is scanned (no text layer) and needs OCR.
pageCountnumberNumber of pages read.

No examples provided.

Common questions

What is the io.github.NicolasMartalog/docweave-mcp server?

io.github.NicolasMartalog/docweave-mcp is listed in the public MCP registry as io.github.NicolasMartalog/docweave-mcp. Generate and read PDFs for AI agents: a generate_pdf and a read_pdf tool, priced per document. This page covers its hosted endpoint (https://docweave.dev/api/mcp).

Is the io.github.NicolasMartalog/docweave-mcp server safe to use?

io.github.NicolasMartalog/docweave-mcp scores 86 out of 100 on VerifyMCP. 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 io.github.NicolasMartalog/docweave-mcp server expose?

io.github.NicolasMartalog/docweave-mcp exposes 2 tools: generate_pdf, read_pdf. Their descriptions and schemas cost roughly 302 tokens of context every time the server is loaded.

Does the io.github.NicolasMartalog/docweave-mcp server require authentication?

No. We connected to io.github.NicolasMartalog/docweave-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.NicolasMartalog/docweave-mcp server still maintained?

io.github.NicolasMartalog/docweave-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.