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.docracy1/docracy

REMOTE · MCP.DOCRACY.IO · SCANNED OCT 14

Free, no-signup e-signatures. check_status free for anyone; find_documents needs paid key.

Available components

0 this week 80 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 Security57
Transport & Reachability100
Schema Quality & AI Usability84
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 309 tokens (~77/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.docracy1/docracy MCP server?

io.github.docracy1/docracy is a hosted endpoint at https://mcp.docracy.io/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 · mcp.docracy.io

# add to Claude Code
claude mcp add --transport http docracy1-docracy 'https://mcp.docracy.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "docracy1-docracy": {
      "url": "https://mcp.docracy.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "docracy1-docracy": {
      "type": "http",
      "url": "https://mcp.docracy.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.docracy1-docracy]
url = "https://mcp.docracy.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "docracy1-docracy": {
      "type": "remote",
      "url": "https://mcp.docracy.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add docracy1-docracy --url 'https://mcp.docracy.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  docracy1-docracy:
    url: "https://mcp.docracy.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "docracy1-docracy": {
      "Transport": "http",
      "Url": "https://mcp.docracy.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add docracy1-docracy -t streamable-http -u 'https://mcp.docracy.io/mcp'
// mcp.json
{
  "mcpServers": {
    "docracy1-docracy": {
      "type": "http",
      "url": "https://mcp.docracy.io/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.

  • 28 Sept 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 Sept 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
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 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
  • 17 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
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 14 Oct 2026 · Probed https://mcp.docracy.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=docracy.io CN=WE1,O=Google Trust Services,C=US 18 Sept 2026 17 Dec 2026 ECDSA 256 ECDSA-SHA256 c6374c7aa83cbbf413c0f068eb449a7c
SANs: docracy.io, mcp.docracy.io, *.mcp.docracy.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.docracy.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
docracy.io. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.docracy.io/mcp Verified 200
http (plaintext) http://mcp.docracy.io/mcp HTTPS enforced 301 https://mcp.docracy.io/mcp
MCP tools · 4 exposed · ~309 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
check_status ~57

Look up the status of a Docracy signing chain from a sign or status link — who's signed, who's still pending.

NameTypeReqDescription
linkstringyesThe docracy.io sign or status link (or just the token) you were emailed.

No output schema declared.

No examples provided.

draft_from_template ~114

Start an agentic drafting workflow from a trusted Docracy template. Returns the prepare URL (fields already placed where applicable), library page, and drafting hints. Does NOT auto-send for signature — the human reviews and sends on docracy.io. Optional notes are echoed as a drafting brief for the assistant.

NameTypeReqDescription
notesstring–Optional deal context the assistant should apply when customizing the draft (parties, fee, dates).
slugstringyesTemplate slug from list_templates (e.g. mutual-nda).

No output schema declared.

No examples provided.

get_template ~65

Fetch metadata for one Docracy template by slug (title, description, key clauses / drafting hints when available) plus the prepare URL to open it for e-signature.

NameTypeReqDescription
slugstringyesTemplate slug, e.g. mutual-nda or a Marketplace slug from list_templates.

No output schema declared.

No examples provided.

list_templates ~73

List free and Marketplace legal templates from Docracy (NDAs, contractor agreements, offer letters, etc.). Optional text filter. Returns slugs and prepare URLs — does not create or send documents.

NameTypeReqDescription
querystring–Optional filter (e.g. nda, freelancer, offer letter). Omit to list popular templates.

No output schema declared.

No examples provided.

Common questions

What is the io.github.docracy1/docracy MCP server?

io.github.docracy1/docracy is an MCP server listed in the public MCP registry as io.github.docracy1/docracy. Free, no-signup e-signatures. check_status free for anyone; find_documents needs paid key. This page covers its hosted endpoint (https://mcp.docracy.io/mcp).

Is the io.github.docracy1/docracy MCP server safe to use?

io.github.docracy1/docracy scores 80 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.docracy1/docracy MCP server expose?

io.github.docracy1/docracy exposes 4 tools: check_status, list_templates, get_template, draft_from_template. Their descriptions and schemas cost roughly 309 tokens of context every time the server is loaded.

Does the io.github.docracy1/docracy MCP server require authentication?

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

Is the io.github.docracy1/docracy MCP server still maintained?

io.github.docracy1/docracy is still listed as active in the MCP registry. We last reached this channel on 14 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.