# Typestate (remote · mcp.typestate.com)

A managed backend your AI agent builds: database, sign-in, files, endpoints. You approve each step.

- Trust score: 91/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `mcp.typestate.com`: 91/100 (this document), [markdown](https://verifymcp.io/servers/com-typestate-typestate/mcp.md), [page](https://verifymcp.io/servers/com-typestate-typestate/mcp)

## Channel facts

- Endpoint: `https://mcp.typestate.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-typestate-typestate 'https://mcp.typestate.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-typestate-typestate": {
      "url": "https://mcp.typestate.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-typestate-typestate": {
      "type": "http",
      "url": "https://mcp.typestate.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-typestate-typestate]
url = "https://mcp.typestate.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-typestate-typestate": {
      "type": "remote",
      "url": "https://mcp.typestate.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-typestate-typestate --url 'https://mcp.typestate.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-typestate-typestate:
    url: "https://mcp.typestate.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-typestate-typestate": {
      "Transport": "http",
      "Url": "https://mcp.typestate.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-typestate-typestate -t streamable-http -u 'https://mcp.typestate.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-typestate-typestate": {
      "type": "http",
      "url": "https://mcp.typestate.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 91, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-16 (score 91, +1)

- [security] Stability: 0.97 → pass
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-15 (score 90, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-14 (score 90, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-13 (score 89, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-12 (score 89, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-11 (score 88, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-10 (score 88, +2)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (4)

### `get_blueprint` (~103 tokens)

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.

Input parameters:

- `blueprint` (string, required): The blueprint's slug or name, as list_blueprints answers it.

Output parameters:

- `answer` (string): 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.

### `get_started` (~112 tokens)

Get started with Typestate

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.

Input parameters:

- `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.

Output parameters:

- `answer` (string): The answer, in English, ready to show a person.
- `mcp_endpoint` (string): 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): Where a person opens an account.
- `website` (string): Where a person reads more about the platform.

### `list_blueprints` (~120 tokens)

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.

Input parameters:

- `purpose` (string): What the backend is for, in the customer's words. Leave it out to list every blueprint.

Output parameters:

- `answer` (string): 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)

### `list_integration_catalog` (~126 tokens)

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.

Input parameters:

- `need` (string): What the backend needs, or a vendor's name: "payments", "send email", "Slack". Leave it out to list the whole catalog.

Output parameters:

- `answer` (string): 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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-typestate-typestate/mcp#diagnostics

## Score history

- 2026-10-17: 91
- 2026-10-16: 91
- 2026-10-15: 90
- 2026-10-14: 90
- 2026-10-13: 89
- 2026-10-12: 89
- 2026-10-11: 88
- 2026-10-10: 88
- 2026-10-07: 86
- 2026-10-05: 86
- 2026-10-04: 74
- 2026-10-03: 84
- 2026-10-02: 84
- 2026-10-01: 84
- 2026-09-30: 83
- 2026-09-29: 83
- 2026-09-28: 82
- 2026-09-27: 82
- 2026-09-26: 81
- 2026-09-25: 81
- 2026-09-24: 81
- 2026-09-23: 80
- 2026-09-22: 80
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 38

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.typestate.com/mcp
- Website: https://typestate.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-typestate-typestate/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-typestate-typestate/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-typestate-typestate/mcp