Typestate
REMOTE · MCP.TYPESTATE.COM
A managed backend your AI agent builds: database, sign-in, files, endpoints. You approve each step.
Available components
Last scanned (3 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1781 tokens (~445/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Oct 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 13 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 12 Oct 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 11 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 10 Oct 26 +2
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://mcp.typestate.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=typestate.com | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 67a7e02b8152bf650e2b9ec67705a8d4 |
| SANs: typestate.com, *.typestate.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.typestate.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| typestate.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.typestate.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mcp.typestate.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Protected resource metadata
| Document | https://mcp.typestate.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.typestate.com/mcp |
| Authorisation server | https://platform.typestate.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.typestate.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.typestate.com/mcp | HTTPS enforced | 301 | https://mcp.typestate.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_blueprint Read one Typestate blueprint ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| blueprint | string | yes | The blueprint's slug or name, as list_blueprints answers it. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The whole setup, in English, as Markdown. |
| notice | string | – | Background work that did not end well since your last call. list_runs names each run. |
No examples provided.
get_started Get started with Typestate ~112
What Typestate is, what it costs, and how to connect to it. Call this first if you have met this server for the first time and want to know what it is for. Ask with no `about` and it answers all three parts at once.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | Which part to answer: "what_it_is" for what the platform does, "connecting" for how an agent authenticates, "plans" for what it costs. Omit it to get all three. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The answer, in English, ready to show a person. |
| mcp_endpoint | string | yes | The address this server answers on. |
| notice | string | – | Background work that did not end well since your last call. list_runs names each run. |
| sign_up_url | string | yes | Where a person opens an account. |
| website | string | yes | Where a person reads more about the platform. |
No examples provided.
list_blueprints List the Typestate blueprints ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| purpose | string | – | What the backend is for, in the customer's words. Leave it out to list every blueprint. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The matching blueprints, one paragraph each, in English. |
| notice | string | – | Background work that did not end well since your last call. list_runs names each run. |
| slugs | array | yes | – |
No examples provided.
list_integration_catalog List the Typestate integration catalog ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | – | What the backend needs, or a vendor's name: "payments", "send email", "Slack". Leave it out to list the whole catalog. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The matching integrations, one paragraph each. |
| notice | string | – | Background work that did not end well since your last call. list_runs names each run. |
| slugs | array | yes | – |
No examples provided.
How do I install the Typestate MCP server?
Typestate is a hosted endpoint at https://mcp.typestate.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.typestate.com
claude mcp add --transport http com-typestate-typestate 'https://mcp.typestate.com/mcp'
What is the Typestate MCP server?
Typestate is an MCP server listed in the public MCP registry as com.typestate/typestate. A managed backend your AI agent builds: database, sign-in, files, endpoints. You approve each step. This page covers its hosted endpoint (https://mcp.typestate.com/mcp).
Is the Typestate MCP server safe to use?
Typestate scores 91 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Typestate MCP server expose?
Typestate exposes 4 tools: get_blueprint, get_started, list_blueprints, list_integration_catalog. Their descriptions and schemas cost roughly 461 tokens of context every time the server is loaded.
Does the Typestate MCP server require authentication?
Yes. Typestate asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Typestate MCP server still maintained?
Typestate is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.