TmpState MCP server

• Registry namedev.tmpstate/tmpstateverified in the MCP registry

The registry name sits under tmpstate.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools16
• Server calls itselftmpstate
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 145 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer175 ms
• Space in an agent's context≈ 2,681 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsB · 80 of 100
• Typed results0 of 16 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 3 of 16
• Not saying whether it only reads or can destroy: 16 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• create_database

  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…

• database_status

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

• list_documents

  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.

• get_document

  Read one document by id. The stored fields are under .data.

• create_document

  Insert a JSON object into a collection (collections are created implicitly). Counts against the write and document quotas.

• update_document

  Shallow-merge a patch into a document (top-level keys overwrite; keys are never deleted). Counts against the write quota.

• delete_document

  Delete one document. Never blocked by quotas; frees a document slot. Emptying a whole collection? Use delete_collection instead of looping this.

• delete_collection

  Delete every document in a collection at once (useful to re-seed). Irreversible. To destroy the entire database, use delete_database instead.

• 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. Irreversible: unlike expiry there is no restore window. Works on expired (frozen) databases too and…

• extend_database

  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)…

• pro_checkout

  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_list_databases

  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.

• pro_create_database

  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…

• pro_attach_database

  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_cancel

  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…

• send_feedback

  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…