Client-side tools
Server-side tools
Accounts & sign-in
Workflow
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
- Shipped means the tool or feature is live and, where it has a page, linked from the roadmap.
- In progress means it is being built now; Planned means it is agreed but not started.
- 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.
