dev.tmpstate/tmpstate
dev.tmpstate/tmpstate · v1.0.0
Zero-key temporary JSON database for agents: one tool call, no signup, no OAuth, no API keys.
MCPremoteno credentialsDatabasesDocuments & PDF
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 16 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 81/100
What it does: 16 tools · 2 read, 8 write (incl. delete/pay) · Databases, Documents & PDF
No tool could be tested safely. Only read-only tools that need no input are called.
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +8
- Read/write annotations: 0
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://tmpstate.dev/mcpTools
16 tools listed at last check
create_databaseCreate 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 creatindatabase_statusUsage, limits, tier and expiry for a database (GET $DB/__meta equivalent).list_documentsList 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_documentRead one document by id. The stored fields are under .data.create_documentInsert a JSON object into a collection (collections are created implicitly). Counts against the write and document quotas.update_documentShallow-merge a patch into a document (top-level keys overwrite; keys are never deleted). Counts against the write quota.delete_documentDelete one document. Never blocked by quotas; frees a document slot. Emptying a whole collection? Use delete_collection instead of looping this.delete_collectionDelete 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. Irreversible: unlike expiry there is no restore window. Works on expired (frozen) databases too and consumes no quota. Call without confirm first: the response stextend_databaseWithout 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 havepro_checkoutMint 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_databasesList 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_databaseCreate 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.pro_attach_databaseAttach 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_cancelCancel 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.send_feedbackOptional 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 extr
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/dev.tmpstate/tmpstate)