WebmasterID logoWebmasterID
Changelog

What shipped, in order

Operator-facing release notes for WebmasterID Core + Agent. Newest first. The current named version is Core v1.8.1.

Read Core v1.8.1 →Connect Claude (MCP)
Releases

Every release that actually shipped

Built incrementally with operator feedback. Review-first AI workflows. No fake roadmap promises here — only work that already landed in production.

Core v1.8.1
CoreAgentMCPBillingOnboardingSecurityUX

Core v1.8.1 — MCP server, workspaces, billing, and operator visibility

The rollup release: a real MCP HTTP server, workspace-scoped multi-tenancy, Stripe-backed billing, full onboarding, and the new operator identity surfaces.

  • Real MCP HTTP server at /api/agent/mcp with workspace-scoped Bearer auth and ten read-only tools.
  • Workspace switcher + operator profile in the dashboard sidebar; copyable user IDs on /settings/account.
  • Stripe billing with three plans (Pro / Agency / Business), signature-verified webhooks, and a customer portal.
  • + 3 more — see the release page
Read release notes →
M55.1
MCPUX

Production-grade /settings/mcp UX

Endpoint-visibility row, three-step quick-start wizard, server-status panel, recent-activity widget, and an in-page verify-connection tester on /settings/mcp.

  • Endpoint-visibility row at the top of /settings/mcp with a one-tap copy button on the full MCP URL.
  • Three-step Quick Start wizard: generate API key → add to Claude → verify. Step 1 ticks green when the workspace already has an active key.
  • Server-status panel — operational / degraded / unconfigured pill, recent success-rate %, last-checked timestamp. Honest 'n/a' when there are no events; no fabricated uptime.
  • + 2 more — see the release page
Read release notes →
M54
MCPAgentSecurity

Real MCP server for WebmasterID Core

Production MCP HTTP endpoint at /api/agent/mcp with ten read-only tools, Bearer auth via the api_keys table, plan gating, audit logging, payload caps, and a per-key rate limit.

  • POST /api/agent/mcp — JSON-RPC 2.0 over HTTP. Methods: initialize, tools/list, tools/call.
  • Ten read-only tools: sites, summary, recent events, bot intelligence, AI referrals, top pages, recommendations, repo mappings, execution sessions, plan status.
  • Workspace-scoped Bearer auth against the api_keys table; revoked keys rejected and audited.
  • + 2 more — see the release page
Read release notes →
M53.3
OnboardingMCPCore

Activation polish + API keys + MCP setup

Welcome email auto-fire, the api_keys infrastructure, /settings/mcp documentation, /getting-started richer post-first-event page, and three Claude/MCP SEO landing pages.

  • Welcome email auto-fires from /api/auth/signup. Delivery failure never blocks signup; production never falls back to logging plaintext tokens.
  • Migration 0017 adds the api_keys table — sha256 hash at rest, six-char prefix, plaintext shown once, workspace-scoped + RBAC-gated.
  • /settings/api-keys ships with one-time plaintext reveal, label + create + revoke flow, audit-log writes.
  • + 3 more — see the release page
Read release notes →

Subscribe via Atom or JSON Feed. Both are generated directly from the typed release registry.

Trust posture

How we ship

A short, honest note on how releases land and what stays out of them.

  • Every entry above corresponds to a real merge into the shipping branch. No dates are invented.
  • MCP access is read-only by default. Write tools, if they ever ship, will land behind their own RBAC permission and a separate audit category.
  • Operator approval remains required for every Agent / Claude change — no autonomous deploy, no auto-merge.
  • Privacy posture is unchanged across releases: no third-party cookies, no fingerprinting, no raw IP storage.
  • We do not claim certifications, SOC2 status, uptime percentages, or customer counts on this page.
Changelog — WebmasterID · WebmasterID