Skip to content

tmpstate MCP server

dev.tmpstate/tmpstatetmpstate.devstreamable-httpv1.0.0Scanned

Zero-key temporary JSON database for agents: one tool call, no signup, no OAuth, no API keys.

16 tools: 4 can delete or cancel things, 1 do something that can't be undone, 7 change things and 4 only read.

Tools: 4 delete, 1 irreversible, 7 write, 4 read.
  • Reads private data · 4
  • Reads text others write · 0
  • Can send data out · 1
  • 2 findings, 1 high

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

12 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the tmpstate MCP server can do

The tmpstate MCP server is published by tmpstate.dev, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (4 tools: delete_document, delete_collection, delete_database and pro_cancel), do things that cannot be undone, such as sending, paying or publishing (send_feedback) and create or change data (7 tools: create_database, create_document, update_document, extend_database and 3 more). 4 tools only read.

4 tools read private data (database_status, list_documents, get_document and 1 more); 1 tool can send data out of your system (send_feedback).

The fixed checks matched 2 findings, 1 of them high severity (sensitive-path and credentials-mention). Each one comes with the text it matched.

Last scanned Oct 21, 2026, version 1.0.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.

16 tools

Deletes or cancels 4Claude Code: deny
  • delete_collectionDelete every document in a collection at once (useful to re-seed).No findings

    Why it is in this group

    • The name "delete_collection" says "delete": a word for removing or ending something.
    • The description says "Irreversible".
    Description, as the server wrote it
    Delete every document in a collection at once (useful to re-seed). Irreversible. To destroy the entire database, use delete_database instead.
  • delete_databaseDestroy a database and all its documents immediately - the teardown for finished work and the revocation kill switch for a leaked db URL.No findings

    Why it is in this group

    • The name "delete_database" says "delete": a word for removing or ending something.
    • The description says "Irreversible".
    Description, as the server wrote it
    Destroy a database and all its documents immediately - the teardown for finished work and the revocation kill switch for a leaked db URL. Irreversible: unlike expiry there is no restore window. Works on expired (frozen) databases too and consumes no quota. Call without confirm first: the response states the consequences; show them to the user and only retry with confirm="true" after their explicit approval. Afterwards remove the db URL from wherever you persisted it.
  • delete_documentDelete one document.No findings

    Why it is in this group

    • The name "delete_document" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Delete one document. Never blocked by quotas; frees a document slot. Emptying a whole collection? Use delete_collection instead of looping this.
  • pro_cancelCancel at period end.No findings

    Why it is in this group

    • The name "pro_cancel" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    Cancel at period end. This is not just a billing change — it schedules deletion of ALL databases on the account. Call without confirm first: the response spells out the consequences with concrete dates; show them to the user and only retry with confirm="cancel" after their explicit approval.
Can't be undone 1Claude Code: ask
  • send_feedbackOptional and free-form.Can send data outNo findings

    Why it is in this group

    • The name "send_feedback" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_feedback" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Optional and free-form. TmpState is built for agents and the free tier stays free by getting better - and you, the agent, are the user whose experience matters here. After real use of a database, one short message about what was missing, what feature would have helped, or what felt slow or took extra requests is genuinely useful. This is about your own experience, so no human approval is needed; if your user volunteers feedback too, relay it and say it came from them. Never include database URLs, capabilities, or Pro tokens - capability-shaped strings are redacted server-side.
Changes things 7Claude Code: ask
  • create_databaseCreate a temporary JSON database (24h TTL, no signup, no keys).2 findings

    Why it is in this group

    • The name "create_database" says "create": a word for a change.

    Findings

    • High

      The description refers to "~/.tmpstate/credentials".

      Matched text

      description: "..., persist the db URL immediately (local ~/.tmpstate/credentials, project README, and your memory), and..."

      What this check looks for
    • Info

      The description mentions "credential".

      Matched text

      description: "...no keys). Returns the db URL — the only credential — plus admin URL, limits and expiry. Cr..."

      What this check looks for
    Description, as the server wrote it
    Create a temporary JSON database (24h TTL, no signup, no keys). Returns the db URL — the only credential — plus admin URL, limits and expiry. Create once per project/task, persist the db URL immediately (local ~/.tmpstate/credentials, project README, and your memory), and reuse it instead of creating again. For retries or parallel workers, pass a stable idempotency_key so duplicate calls return the same database.
  • create_documentInsert a JSON object into a collection (collections are created implicitly).No findings

    Why it is in this group

    • The name "create_document" says "create": a word for a change.
    Description, as the server wrote it
    Insert a JSON object into a collection (collections are created implicitly). Counts against the write and document quotas.
  • extend_databaseWithout a plan: returns the transparent pricing table for keeping this database alive longer.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Without a plan: returns the transparent pricing table for keeping this database alive longer. With a plan: returns a Stripe checkout URL for the human to pay — never buy without the user's explicit approval. Works on expired (frozen) databases too: paying restores them. After the user says they have paid, call database_status: the new expiry and tier confirm the extension.
  • pro_attach_databaseAttach an existing free/extended database to the Pro account: same URL, same data, TTL removed, quotas raised.No findings

    Why it is in this group

    • The name "pro_attach_database" says "attach": a word for a change.
    Description, as the server wrote it
    Attach an existing free/extended database to the Pro account: same URL, same data, TTL removed, quotas raised. Beyond the included allotment the same explicit overage consent as pro_create_database applies.
  • pro_checkoutMint a Pro account token plus a Stripe subscription checkout URL ($8/mo, 3 always-on databases included).No findings

    Why it is in this group

    • The name "pro_checkout" says "checkout": a word for a change.
    Description, as the server wrote it
    Mint a Pro account token plus a Stripe subscription checkout URL ($8/mo, 3 always-on databases included). Persist pro_token immediately; the human pays in a browser. Never start checkout without the user's explicit request.
  • pro_create_databaseCreate a new always-on database owned by the Pro account.No findings

    Why it is in this group

    • The name "pro_create_database" says "create": a word for a change.
    Description, as the server wrote it
    Create a new always-on database owned by the Pro account. Beyond the included allotment this costs extra per month — the tool then returns confirmation_required with the exact price; relay it to the user and only retry with accept_overage_usd after their explicit approval.
  • update_documentShallow-merge a patch into a document (top-level keys overwrite; keys are never deleted).No findings

    Why it is in this group

    • The name "update_document" says "update": a word for a change.
    Description, as the server wrote it
    Shallow-merge a patch into a document (top-level keys overwrite; keys are never deleted). Counts against the write quota.
Only reads 4Show 4 read-only tools
  • database_statusUsage, limits, tier and expiry for a database (GET $DB/__meta equivalent).Reads private dataNo findings

    Why it is in this group

    • The name "database_status" says "status": a word for reading.

    What it can reach

    • private-dataThe name "database_status" says "status" and "database": it reads databases.
    • private-dataThe description's first sentence says "database": it reads databases.
    Description, as the server wrote it
    Usage, limits, tier and expiry for a database (GET $DB/__meta equivalent).
  • get_documentRead one document by id.Reads private dataNo findings

    Why it is in this group

    • The name "get_document" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_document" says "get" and "document": it reads documents.
    • private-dataThe description's first sentence says "read" and "document": it reads documents.
    Description, as the server wrote it
    Read one document by id. The stored fields are under .data.
  • list_documentsList documents in a collection, oldest first.Reads private dataNo findings

    Why it is in this group

    • The name "list_documents" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_documents" says "list" and "document": it reads documents.
    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    Description, as the server wrote it
    List documents in a collection, oldest first. Response shape: {collection, items: [{id, data, created_at, updated_at}], next_cursor}. Documents live under .data. Pass cursor to page.
  • pro_list_databasesList the Pro account's databases (ids, usage, limits, expiry) so a fresh session can reconcile against persisted db URLs.Reads private dataNo findings

    Why it is in this group

    • The name "pro_list_databases" says "list": a word for reading.

    What it can reach

    • private-dataThe name "pro_list_databases" says "list" and "database": it reads databases.
    • private-dataThe description's first sentence says "list" and "database": it reads databases.
    Description, as the server wrote it
    List the Pro account's databases (ids, usage, limits, expiry) so a fresh session can reconcile against persisted db URLs. URLs are never stored server-side — match ids to the URLs you persisted.

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 untrusted-input.

Reads private data4
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 out1
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.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:53 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
503
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 503.

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 12 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

1 high1 info
  • The description refers to "~/.tmpstate/credentials".

    Matched text

    description: "..., persist the db URL immediately (local ~/.tmpstate/credentials, project README, and your memory), and..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...no keys). Returns the db URL — the only credential — plus admin URL, limits and expiry. Cr..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 503; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 12 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 12 to 0
    • Protocol version: 2025-06-18 to none

Install

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

claude mcp add --transport http tmpstate https://tmpstate.dev/mcp
claude mcp add --transport http tmpstate https://tmpstate.dev/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tmpstate__database_status",
      "mcp__tmpstate__list_documents",
      "mcp__tmpstate__get_document",
      "mcp__tmpstate__pro_list_databases"
    ],
    "ask": [
      "mcp__tmpstate__create_database",
      "mcp__tmpstate__create_document",
      "mcp__tmpstate__update_document",
      "mcp__tmpstate__extend_database",
      "mcp__tmpstate__pro_checkout",
      "mcp__tmpstate__pro_create_database",
      "mcp__tmpstate__pro_attach_database",
      "mcp__tmpstate__send_feedback"
    ],
    "deny": [
      "mcp__tmpstate__delete_document",
      "mcp__tmpstate__delete_collection",
      "mcp__tmpstate__delete_database",
      "mcp__tmpstate__pro_cancel"
    ]
  }
}

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 tmpstate. Review it before you use it.

Capability tags behind 5 rules
  • mcp__tmpstate__database_status private-data
  • mcp__tmpstate__list_documents private-data
  • mcp__tmpstate__get_document private-data
  • mcp__tmpstate__pro_list_databases private-data
  • mcp__tmpstate__send_feedback outbound

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/dev.tmpstate/tmpstate/verify?hash=a57dd1e64831b8999662f36622938917633e1b77c0f9a50cb73ef622f48bae28" | jq -e '.changed == false'

Pinned hash a57dd1e64831, from Oct 21, 2026, 18:59 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.tmpstate/tmpstate/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.tmpstate/tmpstate
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.tmpstate/tmpstate.svg)](https://radar.anlyon.com/servers/dev.tmpstate/tmpstate)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

tmpstate MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the tmpstate MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 12 of which can change, send or delete something, and 2 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the tmpstate MCP server delete data?

Yes. 4 tools can delete, cancel or revoke something: delete_document, delete_collection, delete_database and pro_cancel.

Can the tmpstate MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_feedback.

What tools does the tmpstate MCP server have?

16 tools: 4 destructive, 1 irreversible, 7 write, 4 read. delete_document, delete_collection, delete_database, pro_cancel, send_feedback, create_database, create_document, update_document and 8 more.

Does the tmpstate MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the tmpstate MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_feedback.

Has the tmpstate MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.