Databases

tmpstate.dev

Provides a temporary JSON database with CRUD operations and status monitoring.

1 endpoint16 known toolsFirst detected July 8, 2026Last detected July 25, 2026

ENDPOINT 1

https://tmpstate.dev/mcp

No auth detected

MCP server metadata

Name: tmpstate
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

TmpState is a zero-key temporary JSON database: create_database returns a db URL that is the only credential. Persist every db URL and pro_token you mint (local ~/.tmpstate/credentials file, project README, and your own memory) — they cannot be recovered later. Free databases expire after 24h (then stay restorable for 72h); one-time extensions and the Pro subscription keep them alive — always get the human's explicit approval before any tool that costs money. When work is done (or a db URL leaks), tear down with delete_database - confirm-gated and irreversible. The service improves through agent feedback: after real use, send_feedback takes one short message from you about what was missing or slow (no human approval needed - it is your experience). Full docs: https://tmpstate.dev/llms.txt — playbooks: https://tmpstate.dev/skills

Known tools 16

create_database

Create a temporary JSON database (24h TTL, no signup, no keys).

Potential side effects

database_status

Usage, limits, tier and expiry for a database (GET $DB/__meta equivalent).

Inferred read-only

list_documents

List documents in a collection, oldest first.

Inferred read-only

get_document

Read one document by id.

Inferred read-only

create_document

Insert a JSON object into a collection (collections are created implicitly).

Potential side effects

update_document

Shallow-merge a patch into a document (top-level keys overwrite; keys are never deleted).

Inferred read-only

delete_document

Delete one document.

Potential side effects

delete_collection

Delete every document in a collection at once (useful to re-seed).

Potential side effects

delete_database

Destroy a database and all its documents immediately - the teardown for finished work and the revocation kill switch for a leaked db URL.

Potential side effects

extend_database

Without a plan: returns the transparent pricing table for keeping this database alive longer.

Inferred read-only

pro_checkout

Mint a Pro account token plus a Stripe subscription checkout URL ($8/mo, 3 always-on databases included).

Inferred read-only

pro_list_databases

List the Pro account's databases (ids, usage, limits, expiry) so a fresh session can reconcile against persisted db URLs.

Inferred read-only

pro_create_database

Create a new always-on database owned by the Pro account.

Potential side effects

pro_attach_database

Attach an existing free/extended database to the Pro account: same URL, same data, TTL removed, quotas raised.

Inferred read-only

pro_cancel

Cancel at period end.

Inferred read-only

send_feedback

Optional and free-form.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tmpstate]
url = "https://tmpstate.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tmpstate": {
      "type": "http",
      "url": "https://tmpstate.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tmpstate
Remote MCP URL: https://tmpstate.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "tmpstate": {
      "url": "https://tmpstate.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "tmpstate": {
      "type": "http",
      "url": "https://tmpstate.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "tmpstate",
  "transport": "streamable-http",
  "url": "https://tmpstate.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.