Developer Tools
webspecification.com
Provides full-text search across all specification pages and lists available topics.
ENDPOINT 1
https://mcp.webspecification.com/mcp
MCP server metadata
- Name
- specification-website
- Version
- 0.2.0
Read-only MCP server for Web Specification Studio at https://webspecification.com. Use `search` for free-text queries, `list_topics` for filtered lists, `get_topic` to fetch a single page as Markdown, and `get_checklist` for audit-style output. Spec items have one of four statuses: `required` (platform contract breaks without it), `recommended` (modern site should do it), `optional` (context-dependent), `avoid` (outdated or harmful). The `list_topics` and `get_checklist` tools return ALL statuses by default — pass `status` to filter. The `audit_url` prompt is the exception: with no `focus`, it defaults to `required`-only.
Known tools 6
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.specification-website]
url = "https://mcp.webspecification.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"specification-website": {
"type": "http",
"url": "https://mcp.webspecification.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: specification-website
Remote MCP URL: https://mcp.webspecification.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"specification-website": {
"url": "https://mcp.webspecification.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"specification-website": {
"type": "http",
"url": "https://mcp.webspecification.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "specification-website",
"transport": "streamable-http",
"url": "https://mcp.webspecification.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.