Skip to content

Typestate

by typestate.com · remote · no sign-in to list tools · v0.1.0 · published by com.typestate

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

Read only
CompareRegistry entry

4 tools: 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Only reads 4Claude Code: allow
  • get_blueprintOne 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 …No findings

    Why it is in this group

    • The name "get_blueprint" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Read one Typestate blueprint
  • get_startedWhat Typestate is, what it costs, and how to connect to it.No findings

    Why it is in this group

    • The name "get_started" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Get started with Typestate
  • list_blueprintsThe blueprints: whole backends for a named kind of business, each a set of English definitions proven on this platform.No findings

    Why it is in this group

    • The name "list_blueprints" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List the Typestate blueprints
  • list_integration_catalogThe integration catalog: the systems a Typestate backend works with, made and checked by Typestate.No findings

    Why it is in this group

    • The name "list_integration_catalog" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List the Typestate integration catalog

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__typestate__get_blueprint",
      "mcp__typestate__get_started",
      "mcp__typestate__list_blueprints",
      "mcp__typestate__list_integration_catalog"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as typestate. Review it before you use it.