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

md-share

https://docs-md.com

Registry code: ebdb9861d285ae90

api record

Docs MD publishes markdown at a public link (https://docs-md.com/<id>) with no account.

Use share_markdown when the user wants to send, publish, hand off or review a markdown document (plans, specs, reports, READMEs, agent handoffs). Default expiry is 30 days; use "never" only when asked for a permanent link.

endpoint
https://docs-md.com/api/mcp
protocol
streamable-http ·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 md-share live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is md-share free to use?
Yes — the hub reached it with no key and no payment.
What tools does md-share have?
4 tools: delete_share, share_markdown, update_share, read_share.
Is md-share 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.5%

90 days 99.8%· all time 99.8%

latency
229ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 455 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
documents & files storage & sharing
used for
  • share markdown as a public link
  • update a shared markdown page
  • delete a shared page
takes → gives
text → web pages
tools
3 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 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.

  • delete_share changes data unknown never probed

    Permanently delete a share using its id and edit token.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id",
    "edit_token"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The share id (the URL path segment)"
    },
    "edit_token": {
      "type": "string",
      "description": "Edit token returned when the share was created"
    }
  }
}
    arguments 17 lines
  • share_markdown changes data unknown never probed

    Publish markdown at a public docs-md.com link that renders it (tables, code, mermaid diagrams, table of contents). Use it to send a plan, spec, report, README or agent handoff to a person or another agent. Returns the URL, a raw-markdown URL and an edit token for later updates or deletion.

    mcp-tool

    {
  "type": "object",
  "required": [
    "content"
  ],
  "properties": {
    "expiry": {
      "enum": [
        "1d",
        "7d",
        "30d",
        "never"
      ],
      "type": "string",
      "description": "How long the link stays live (default 30d; \"never\" keeps it forever)"
    },
    "content": {
      "type": "string",
      "description": "The markdown content to share (up to 120,000 characters)"
    },
    "filename": {
      "type": "string",
      "description": "Optional file name shown as the page title, e.g. \"HANDOFF.md\" or \"plan.md\""
    }
  }
}
    arguments 26 lines
  • update_share changes data unknown never probed

    Replace the content of an existing share using its id and edit token.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id",
    "edit_token",
    "content"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The share id (the URL path segment)"
    },
    "content": {
      "type": "string",
      "description": "The new markdown content"
    },
    "filename": {
      "type": "string",
      "description": "Optional new filename"
    },
    "edit_token": {
      "type": "string",
      "description": "Edit token returned when the share was created"
    }
  }
}
    arguments 26 lines
  • read_share unknown 1h ago

    Fetch the raw markdown of a docs-md.com share. Accepts the share id or any docs-md.com share URL. Use it when someone gives you a docs-md.com link, for example a handoff written by another agent.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Share id (e.g. calm-river-Ab12C) or a docs-md.com share URL"
    }
  }
}
    arguments 12 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 ebdb9861d285ae90.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ebdb9861d285ae90/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/ebdb9861d285ae90/badge.svg)](https://brick.blue/agent/ebdb9861d285ae90?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.