Add 404.directory MCP server

[MM-sheng]

Summary

Adds 404.directory, a public remote Streamable HTTP MCP server for:

• one-call official OpenAI, Microsoft Learn, AWS, and Cloudflare documentation search
• capability-based tool discovery and machine-readable trust profiles
• public deployment verification
• controlled invocation of provider-verified, read-only MCP tools

Remote endpoint: https://404.directory/mcp
Repository: https://github.com/MM-sheng/404-directory
Official MCP Registry: io.github.MM-sheng/404-directory v0.8.1
Installable Agent Skill: https://www.skills.sh/mm-sheng/404-directory/use-404-directory

Validation

• python validate.py — passed (207 files)
• Production MCP initialization and tools/list verified
• Six representative tools include their current live input schemas
• No authentication or API key is required

[MM-sheng]

Release evidence update (2026-08-23 UTC): 404.directory is now v0.9.2 in production, on public npm, and in the Official MCP Registry. A clean public-package acceptance run completed MCP initialize, listed exactly 12 tools, and returned a non-error structured result from search_tools; a separate production smoke also passed verify_web, search_official_docs, and search_tools. No account or API key is required.

• Release: https://github.com/MM-sheng/404-directory/releases/tag/v0.9.2
• npm: https://www.npmjs.com/package/@mmvv1638/404-directory-mcp/v/0.9.2
• Install: https://404.directory/connect

[madeburo]

hi @MM-sheng
the registry entry is already materially out of date:

• The YAML declares version 0.8.2, while the current service reports 0.10.3.

• The entry documents 6 tools, while the current service exposes 16, including the risk-evaluation, recommendation, capability-graph, and server-inspection tools.

• updated_at and the descriptions/schemas should be refreshed from the current deployment.

There is also a registry-level issue: this is a remote-only server, but the connection URL is currently embedded only in the description. The registry does not yet expose a first-class machine-readable remote endpoint field, so consumers cannot reliably discover and connect to https://404.directory/mcp

Please rebase the PR and update the version, timestamp, tool inventory, and schemas to match the current deployment. We should also resolve the explicit remote-endpoint representation before merging this entry.