Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Authorization not required, issuer https://platform.typestate.com
Changed the definition of "get_started"
⟨64 unchanged words⟩ "string"}},"required":["answer","mcp_endpointwebsite","sign_up_urlmcp_endpoint","websitesign_up_url"],"type":"object"}
Changed the definition of "get_blueprint", "get_started", "list_blueprints" and 1 more
⟨7 unchanged words⟩ English, as Markdown.","type":"string"},"notice":{"description":"Background work that did not end well since your last call. list_runs names each run.","type":"string"}},"required":["answer"],"type":"object"}
⟨20 unchanged words⟩ answers on.","type":"string"},"notice":{"description":"Background work that did not end well since your last call. list_runs names each run.","type":"string"},"sign_up_url":{"description":"Where a person opens ⟨23 unchanged words⟩
Authorization not required, issuer https://platform.typestate.com
Authorization not required, issuer https://platform.typestate.com
Certificate changed, valid to 2026-12-27
Authorization not required, issuer https://platform.typestate.com
Added "get_blueprint", "list_blueprints" and "list_integration_catalog" (1 tools before, 4 now)
Read one Typestate blueprint — One blueprint's whole setup in English: every action's definition in full, the record types, web endpoints, schedules, sign-in, payments and MCP server it declares, what it cannot do, and what the person does after it starts. Read it before start_from_blueprint, and tell the person which rule they will most likely want to change.
List the Typestate blueprints — The blueprints: whole backends for a named kind of business, each a set of English definitions proven on this platform. Ask with the purpose in the customer's words, such as "salon appointments with a deposit", before you define the first entity of a new backend. A blueprint that fits is started with start_from_blueprint, and every definition in it is the customer's own to change afterwards.
List the Typestate integration catalog — The integration catalog: the systems a Typestate backend works with, made and checked by Typestate. A built-in one is turned on with one setting tool, which the answer names. A declared one was called against the real vendor on the date the answer gives, and apply_integration copies it into a service. Ask before you write a declaration yourself with define_integration.
Authorization not required, issuer https://platform.typestate.com
Authorization not required, issuer https://platform.typestate.com
Authorization not required, issuer https://platform.typestate.com
Authorization not required, issuer https://platform.typestate.com
Authorization not required, issuer https://platform.typestate.com
Unknown → Live
Certificate recorded, valid to 2026-10-29
Authorization not required, issuer https://platform.typestate.com
First tool surface recorded: 1 tool (server version 0.1.0)
https://mcp.typestate.com/mcp (mcp_streamable_http) — from mcp_registry, with the record
Showing the latest 18 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed
⟨9 unchanged words⟩ in English.","type":"string"},"notice":{"description":"Background work that did not end well since your last call. list_runs names each run.","type":"string"},"slugs":{"items":{"type":"string" ⟨7 unchanged words⟩
⟨7 unchanged words⟩ paragraph each.","type":"string"},"notice":{"description":"Background work that did not end well since your last call. list_runs names each run.","type":"string"},"slugs":{"items":{"type":"string" ⟨7 unchanged words⟩