# Service status & release channels

Operational status, release channels, rate limits, and known issues for agenticweb.wiki and the wiki.agenticweb/probe MCP server (current version: 1.3.0).

## Current operational status

| Surface | Endpoint | Channel | Status | Notes |
| --- | --- | --- | --- | --- |
| MCP Server (Stable) | https://agenticweb.wiki/mcp | stable (Public Preview) | Operational | Streamable HTTP JSON-RPC 2.0 & stateless A2A 1.0 responder. |
| MCP Server (Preview) | https://agenticweb.wiki/mcp/preview | preview (Insiders) | Operational | Stages new or experimental changes before promotion to /mcp. |
| Domain Readiness Reports | https://agenticweb.wiki/check/<domain>/ | stable | Operational | HTML, Markdown (index.md), JSON (index.json), and SVG badge (/badge/<domain>.svg). |
| Static Dataset & Twin Files | https://agenticweb.wiki/data/ | stable | Operational | 132 standards, SHA-256 manifest, JSON/NDJSON/CSV, and Markdown twins. |

## Release & hotfix policy

- Stable vs. Preview endpoints: /mcp only gains backwards-compatible capabilities. Any change that alters output structure or scoring behaviour is staged on /mcp/preview first.

- Stability tiers: Deterministic read and generation tools (define, get, search, has, changes, stale, template, ask, digest) are beta — we will not rename or remove them or their input parameters without at least 30 days' notice in the [changelog](/changelog/) ([Atom feed](/feed.xml)). Live origin network tools (probe, validate_manifest) are experimental and evolve as third-party web topologies and draft specs change.

- Gradual Cloudflare Worker rollouts: Production Worker updates roll out gradually via Cloudflare Worker Versions (10% canary traffic split followed by 100% promotion) with instant single-command rollback if error rates or latency budgets regressed.

- Unified versioning: Version 1.3.0 is synchronized across the MCP Registry (server.json), [/mcp/server-card](/mcp/server-card), [/.well-known/agent-card.json](/.well-known/agent-card.json), the JSON-RPC initialize handshake, and the [changelog](/changelog/).

## Rate limits & safety guards

- Rate limits: probe and network-fetching validate_manifest calls are limited to 30 requests/minute per client (RateLimit-Policy: 30;w=60, RateLimit-Limit: 30); has is limited to 120 requests/minute per client; any single target origin is probed at most 10 times/minute globally across all callers. Local content validation and dataset lookup tools are unmetered.

- Payload & redirect caps: Request bodies on /mcp are capped at 256 KB; outbound probe fetches cap response bodies at 64 KB, per-path timeouts at 5 seconds (8 seconds total budget), and redirect hops at 3, re-verifying DNS and IPv4/IPv6 SSRF blocklists at every redirect hop.

- Untrusted external content: Outbound probe and validate_manifest responses return structured fields only (never raw page prose) and carry content_trust: "untrusted_external_origin" so calling orchestrators treat third-party strings as untrusted data rather than instructions.

## Known issues & recent incident notes

- 2026-10-25 (Resolved in v1.3.0): Cross-tool coherence audit fixed 20 edge cases across probe and validate_manifest (including multi-manifest MCP endpoint deduplication, WAF-challenged root vs. open robots.txt posture reconciliation, CDN/CAS sister-domain redirects on huggingface.co and cloudflare.com, and KV cache version invalidation). Full details in the [errata log](/errata/) and [changelog](/changelog/).

Last updated 2026-10-25 · Report an issue via [/submit/](/submit/) or [info@belgravialabs.com](mailto:info@belgravialabs.com).