whatwg-spec-mcp

endpoint

https://whatwg-spec-mcp.jasnell.workers.dev/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 whatwg-spec-mcp live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is whatwg-spec-mcp free to use?

Yes — the hub reached it with no key and no payment.

What tools does whatwg-spec-mcp have?

7 tools: search_standard, search_spec_content, get_standard_toc, get_standard_section, search_issues, search_all_standards, list_standards.

Is whatwg-spec-mcp 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.

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_standards reads open 8h ago

  List all WHATWG living standards with their name, description, and URL. Optionally filter by a search term. Examples: - list_standards() — list all 22 standards - list_standards(search="networking") — find networking-related standards - list_standards(search="stream") — find the Streams Standard

  mcp-tool

  1234567891011

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "search": {
        "type": "string",
        "description": "Optional search term to filter standards by name or description."
      }
    },
    "additionalProperties": false
  }

  arguments 11 lines copy
• search_standard reads unknown 16h ago

  Search within a specific WHATWG standard for sections by title, ID, section number, or concept. Returns matching section titles, IDs, and URLs. If you don't know which standard to search, use `search_all_standards` instead. Examples: - search_standard(standard="fetch", query="Request") — find Request-related sections in Fetch - search_standard(standard="dom", query="EventTarget") — find EventTarget in DOM - search_standard(standard="html", query="canvas") — find canvas sections in HTML - search_standard(standard="url", query="4.4") — find section 4.4 in URL Standard

  mcp-tool

  123456789101112131415161718192021222324

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "standard",
      "query"
    ],
    "properties": {
      "limit": {
        "type": "number",
        "default": 15,
        "description": "Maximum number of results to return (default 15)."
      },
      "query": {
        "type": "string",
        "description": "Search query — a section title, ID, concept, or section number (e.g. \"Request\", \"concept-request\", \"4.1\")."
      },
      "standard": {
        "type": "string",
        "description": "Standard name (e.g. \"fetch\", \"dom\", \"html\", \"url\", \"streams\"). Use list_standards to see all available standards."
      }
    },
    "additionalProperties": false
  }

  arguments 24 lines copy
• search_spec_content reads unknown 16h ago

  Full-text search within a WHATWG standard's content. Unlike search_standard which only matches section headings, this searches the actual body text of the spec. Useful for finding where a specific term, algorithm name, or concept is discussed. Note: For the HTML Standard, only a representative subset of pages is searched to keep response times reasonable. Examples: - search_spec_content(standard="html", query="structuredClone") - search_spec_content(standard="fetch", query="CORS") - search_spec_content(standard="dom", query="composedPath")

  mcp-tool

  123456789101112131415161718192021222324

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "standard",
      "query"
    ],
    "properties": {
      "limit": {
        "type": "number",
        "default": 10,
        "description": "Maximum number of matching excerpts to return (default 10)."
      },
      "query": {
        "type": "string",
        "description": "Search term to find in the spec body text."
      },
      "standard": {
        "type": "string",
        "description": "Standard name (e.g. \"fetch\", \"dom\", \"html\", \"url\", \"streams\")."
      }
    },
    "additionalProperties": false
  }

  arguments 24 lines copy
• get_standard_toc reads unknown 12h ago

  Fetch the table of contents for a specific WHATWG standard, listing all sections with their numbers, titles, and IDs. Useful for browsing the structure of a standard before reading specific sections. Examples: - get_standard_toc(standard="fetch") — browse the Fetch Standard structure - get_standard_toc(standard="dom") — browse the DOM Standard structure - get_standard_toc(standard="html", max_depth=2) — top-level HTML Standard sections only

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "standard"
    ],
    "properties": {
      "standard": {
        "type": "string",
        "description": "Standard name (e.g. \"fetch\", \"dom\", \"html\", \"url\", \"streams\"). Use list_standards to see all available standards."
      },
      "max_depth": {
        "type": "number",
        "description": "Maximum section depth to include (e.g. 2 = only top-level and one level of subsections). Useful for large standards like HTML. If omitted, all sections are included."
      }
    },
    "additionalProperties": false
  }

  arguments 18 lines copy
• get_standard_section reads unknown 16h ago

  Fetch the full content of a specific section from a WHATWG standard. Returns the section text converted to simplified markdown with headings, algorithm steps, and cross-references preserved. Use search_standard first to find the correct section ID. Examples: - get_standard_section(standard="fetch", section_id="requests") — Fetch Standard Requests section - get_standard_section(standard="dom", section_id="interface-eventtarget") — EventTarget interface - get_standard_section(standard="html", section_id="the-canvas-element") — canvas element spec

  mcp-tool

  1234567891011121314151617181920212223

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "standard",
      "section_id"
    ],
    "properties": {
      "standard": {
        "type": "string",
        "description": "Standard name (e.g. \"fetch\", \"dom\", \"html\", \"url\", \"streams\")."
      },
      "max_length": {
        "type": "number",
        "description": "Maximum character length for the returned content. If the section is longer, it will be truncated with a note. Useful for very large sections."
      },
      "section_id": {
        "type": "string",
        "description": "The section ID (e.g. \"concept-request\", \"dom-url\", \"the-html-element\"). Use search_standard to discover valid section IDs."
      }
    },
    "additionalProperties": false
  }

  arguments 23 lines copy
• search_issues reads unknown 8h ago

  Search open and closed GitHub issues and pull requests across WHATWG specification repositories. Useful for finding discussions, bug reports, feature requests, and in-progress spec changes. Examples: - search_issues(query="fetch abort") — find abort-related issues across all WHATWG repos - search_issues(query="URL parsing", standard="url") — search in the URL Standard repo - search_issues(query="ReadableStream", type="pr") — find PRs about ReadableStream

  mcp-tool

  123456789101112131415161718192021222324252627282930313233

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "type": {
        "enum": [
          "issue",
          "pr",
          "both"
        ],
        "type": "string",
        "default": "both",
        "description": "Filter by type: \"issue\" for issues only, \"pr\" for pull requests only, \"both\" for both (default)."
      },
      "limit": {
        "type": "number",
        "default": 15,
        "description": "Maximum number of results to return (default 15)."
      },
      "query": {
        "type": "string",
        "description": "Search term (e.g. \"fetch abort\", \"service worker\", \"URL parsing\")."
      },
      "standard": {
        "type": "string",
        "description": "Optional: limit search to a specific standard's repo (e.g. \"fetch\", \"dom\", \"html\")."
      }
    },
    "additionalProperties": false
  }

  arguments 33 lines copy
• search_all_standards reads unknown 8h ago

  Search for sections across ALL WHATWG standards at once. Useful when you don't know which standard defines a particular concept or API. For example: "structuredClone", "AbortSignal", "EventTarget", "ReadableStream". Returns matching sections with the standard they belong to. Use `search_standard` instead if you already know which standard to search.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "type": "number",
        "default": 15,
        "description": "Maximum number of results to return (default 15)."
      },
      "query": {
        "type": "string",
        "description": "Search query — an API name, concept, section title, or ID (e.g. \"structuredClone\", \"AbortSignal\", \"URL parsing\", \"CORS\")."
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy

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

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.