_ registry / mcp streamable-http · checked 58m ago

devdocs10

https://devdocs10.com

Registry code: 41a2a5658f0e8dd1

api record

DevDocs10 (devdocs10.com) has beginner-to-professional guides for Swift, JavaScript, CSS and HTML, with tested code examples. Use search_docs to find articles, then get_doc to read one as Markdown.

endpoint
https://devdocs10.com/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 devdocs10 live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is devdocs10 free to use?
Yes — the hub reached it with no key and no payment.
What tools does devdocs10 have?
3 tools: get_doc, list_docs, search_docs.
Is devdocs10 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
100%

90 days 100%· all time 100%

latency
194ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 3 tools
2 open 1 never probed 2 of 3 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_docs open 58m ago

    List DevDocs10 articles grouped by topic. Without a section, lists the sections and their topic groups.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "section": {
      "enum": [
        "swift",
        "javascript",
        "css",
        "html"
      ],
      "type": "string"
    }
  }
}
    arguments 14 lines
  • search_docs open 58m ago

    Search DevDocs10 guides (Swift, JavaScript, CSS, HTML) by keywords. Returns the best-matching articles with their paths; read one with get_doc.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Max results (default 8)"
    },
    "query": {
      "type": "string",
      "description": "What to look for, e.g. \"swift actors\" or \"css container queries\""
    },
    "section": {
      "enum": [
        "swift",
        "javascript",
        "css",
        "html"
      ],
      "type": "string",
      "description": "Optional: limit to one language"
    }
  }
}
    arguments 28 lines
  • get_doc unknown 58m ago

    Get a DevDocs10 article as Markdown, including tested example output and browser support where available.

    mcp-tool

    {
  "type": "object",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "Article path from search_docs, e.g. \"swift/swift-structs\", \"/articles/swift/swift-structs\", or a full devdocs10.com 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 41a2a5658f0e8dd1.

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

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.