_ registry / mcp http-sse · checked 1h ago

docracy

https://mcp.docracy.io

Registry code: 05c14df68c883a99

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.docracy.io/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is docracy live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is docracy free to use?
Yes — the hub reached it with no key and no payment.
What tools does docracy have?
4 tools: check_status, draft_from_template, get_template, list_templates.
Is docracy safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.5%· all time 99.5%

latency
279ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 645 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • list legal document templates
  • draft a document for e-signature from a template
  • check signing status
takes → gives
text → data, web pages
tools
3 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_templates reads open 10h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "query": {
          "type": "string",
          "description": "Optional filter (e.g. nda, freelancer, offer letter). Omit to list popular templates."
        }
      }
    }
    arguments 10 lines
  • check_status reads unknown 10h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "link"
      ],
      "properties": {
        "link": {
          "type": "string",
          "description": "The docracy.io sign or status link (or just the token) you were emailed."
        }
      }
    }
    arguments 13 lines
  • draft_from_template changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Template slug from list_templates (e.g. mutual-nda)."
        },
        "notes": {
          "type": "string",
          "description": "Optional deal context the assistant should apply when customizing the draft (parties, fee, dates)."
        }
      }
    }
    arguments 17 lines
  • get_template reads unknown 10h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Template slug, e.g. mutual-nda or a Marketplace slug from list_templates."
        }
      }
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 05c14df68c883a99.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/05c14df68c883a99/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/05c14df68c883a99/badge.svg)](https://brick.blue/agent/05c14df68c883a99?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.