Typestate MCP server
com.typestate/typestatetypestate.comstreamable-httpv0.1.0Scanned
A managed backend your AI agent builds: database, sign-in, files, endpoints. You approve each step.
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Typestate MCP server can do
The Typestate MCP server is published by typestate.com, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
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. Name a `service` and it also lists what a person must do before Live works for that service (decision 0776).
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:49 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.typestate.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://platform.typestate.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:get_blueprintOnly readsinputSchema
- Changed:get_startedOnly readsinputSchema
- Changed:list_blueprintsOnly readsinputSchema
- Changed:list_integration_catalogOnly readsinputSchema
Tools1 changed.~1 changedView diff
- Changed:get_startedOnly readsdescriptioninputSchema
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/mcpclaude mcp add --transport http typestate https://mcp.typestate.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as typestate. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.typestate/typestate/verify?hash=f75b7ed51479f9cdbe45ee9ce0eab51c86c602ec746841f8126f2d91cce1747a" | jq -e '.changed == false'Pinned hash f75b7ed51479, from Nov 14, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.typestate/typestate/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.typestate/typestate)Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.
Typestate MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Typestate MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Typestate MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Typestate MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Typestate MCP server have?
- 4 tools: 4 read. get_blueprint, get_started, list_blueprints and list_integration_catalog.
Does the Typestate MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Typestate MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Typestate MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.