MCP product

📄Landing page & docsMCP landing page and docs with ready-to-paste setup for Claude Desktop and other clients.Shipped

MCP server

MCP server roadmap: what is live today and what ships next, grouped by rollout stage.

0Shipped1Foundation2Network3Web & SEO4Compute & protocol

Already shipped

Shipped
🧰Live MCP tools (12)dns_lookup, ip_lookup, qr_generate, list_versions, download_dev_server, proxy_image, ssl_check, http_check, hash, simulate_http_error, markdown_to_html and generate_agent.Shipped
🤖generate_agentAgent config generator: Claude Code subagent + SKILL.md, or AGENTS.md + .codex/config.toml, from a structured spec (20 req/min, no LLM).Shipped
🔐OAuth 2.1 for connectorsClaude and ChatGPT connectors: Dynamic Client Registration, PKCE S256, RFC 8707 resource binding, redirect allowlist.Shipped
🏷️Tool annotationsRead-only and destructive hints published on every tool.Shipped
📐Real outputSchemaEach tool carries a real JSON Schema for its output.Shipped

Foundation

Foundation
🧭Normalization layerOne domain/url/ip normalizer shared by web, REST and MCP.Shipped
⚠️Unified error formatcode + message + hint, returned with isError instead of HTTP 500.Shipped
🛡️SSRF-safe HTTP clientOne shared outbound client with private-range blocking.Shipped
🗃️Response cachePostgres table with a 60–300s TTL (no Redis for now).Shipped

Network

Network
🔒ssl_checkCertificate chain, expiry and supported protocols.Shipped
📡http_checkStatus, headers, redirects and timing for a URL.Shipped
🧨simulate_http_errorReady-to-call URLs that answer a chosen HTTP error (status, delay, provider body, 429 headers, dropped/hung connection).Shipped
🌐dns_propagationCompare a record across public resolvers.Planned
✉️email_dns_checkSPF, DKIM and DMARC for a domain.Planned
📇whoisRegistrar, dates and nameservers over RDAP.Planned
🚪port_checkUp to 10 ports, no private ranges.Deferred

Web & SEO

Web & SEO
🔖page_metaTitle, description, canonical and Open Graph tags. Free.Planned
📈seo_auditOn-page SEO checks with a pass/fail summary. Free.Planned
🖼️og_previewLink preview built from Open Graph data. Free.Planned
📸screenshotRendered page image. Pro.Planned
🔆lighthousePerformance and best-practice scores. Pro.Planned
🔗broken_linksCrawl a page and list failing links. Pro.Planned
✂️shorten_urlShort link via Kurzo.Planned

Exact computation

Compute & protocol
🧮hashMD5, SHA-1, SHA-256 and SHA-512 over text.Shipped
📝markdown_to_htmlRender GitHub-flavored Markdown to sanitised HTML (60 req/min, no LLM).Shipped
⏰cron_explainCron expression to plain text plus the next runs.Planned
🔍regex_testMatch and capture against a pattern.Planned
🔑jwt_decodeDecode header and payload.Planned
🔄diffLine-level differences between two texts.Planned
📦json_validateValidate JSON with exact error positions.Planned

hash now ships as an MCP tool. Planned as MCP tools: cron, regex, JWT, diff and JSON validation. The browser versions of hash, cron, regex, JWT and diff already ship. Not planned: uuid and color — the model can do those itself. hash ships at a lower priority than the other compute tools: an agent that can run code should hash locally.

MCP protocol features

Compute & protocol
🧱structuredContentReturn typed structuredContent next to the text result.Planned
🏷️idempotentHint & friendsidempotentHint and the remaining safety hints on every tool.Planned
📚Resourcesarttron://versions/latest/changelog and arttron://docs/tools.Planned
💬3 promptsReady-made prompts for common workflows.Planned
⏳Progress notificationsLong-running calls report progress.Planned
🩺domain_healthComposite tool: DNS, SSL and HTTP in one call.Planned
📊Quota in _metaRemaining calls returned in _meta.Planned

What this roadmap tracks

This page maps every tool in the sandbox to its current state: what ships today, what is planned and what is deferred. The General tab lists the browser and server tools, the API tab covers keys and quotas, and the MCP tab groups the server rollout by stage, so a single page works as a status board.

The MCP server rollout is the clearest example. Stage 0 (Shipped) is done: twelve live tools, OAuth 2.1 for connectors, tool annotations and a real outputSchema on every tool. Stage 1 (Foundation) is also done — the shared normalizer, the unified error format, the SSRF-safe client and the response cache. Stage 2 is part-shipped: ssl_check and http_check are live, while dns_propagation, email_dns_check and whois are planned and port_check is deferred.

How to read the status badges

  1. Shipped means the tool or feature is live and, where it has a page, linked from the roadmap.
  2. In progress means it is being built now; Planned means it is agreed but not started.
  3. Deferred means it is deliberately parked, usually for safety or cost reasons.

Frequently asked questions about the roadmap

Is the roadmap a promise of dates?

No. It tracks status and rollout order, not deadlines; an item can move between Planned, In progress and Shipped as work lands.

Which items have already shipped?

The twelve MCP tools, OAuth 2.1 connectors, tool annotations and output schemas (stage 0), plus the normalizer, error format, SSRF-safe client and response cache (stage 1).

Why are some tools deferred?

Items such as port_check are parked on purpose: a port scanner needs strict abuse and private-range controls before it can ship safely.

Back to home