Chroma’s official MCP server: vector search and collection management for RAG workflows.
Nothing to run from here
Tmpstate is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
16
tools declared
remote
at its publisher
—
calls last 7d
What it does
Zero-key temporary JSON database for agents: one tool call, no signup, no OAuth, no API keys.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tmpstate-mcp https://tmpstate.dev/mcp
# 2 — ask your agent for something these tools do
# create_database, database_status, list_documents and 13 more
Tmpstate costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TMAll 1 server
tmpstate1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http tmpstate-mcp https://tmpstate.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| idempotency_key | string | no | Stable retry key. Reusing it from the same client returns the same database. |
Usage, limits, tier and expiry for a database (GET $DB/__meta equivalent).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
| collection | string | yes | Collection name (created implicitly on first write). |
| limit | integer | no | — |
| cursor | string | no | next_cursor from the previous page. |
Read one document by id. The stored fields are under .data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
| collection | string | yes | Collection name (created implicitly on first write). |
| id | string | yes | Document id (doc_...). |
Insert a JSON object into a collection (collections are created implicitly). Counts against the write and document quotas.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
| collection | string | yes | Collection name (created implicitly on first write). |
| data | object | yes | The document: a JSON object. |
Shallow-merge a patch into a document (top-level keys overwrite; keys are never deleted). Counts against the write quota.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
| collection | string | yes | Collection name (created implicitly on first write). |
| id | string | yes | Document id (doc_...). |
| patch | object | yes | Top-level fields to merge. |
Delete one document. Never blocked by quotas; frees a document slot. Emptying a whole collection? Use delete_collection instead of looping this.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
| collection | string | yes | Collection name (created implicitly on first write). |
| id | string | yes | Document id (doc_...). |
Delete every document in a collection at once (useful to re-seed). Irreversible. To destroy the entire database, use delete_database instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
| collection | string | yes | Collection name (created implicitly on first write). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
| confirm | string | no | Pass "true" only after the user has seen that deletion is immediate and irreversible and approved. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
| plan | string | no | — |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pro_token | string | no | Pro account token (pt_...). Optional if the MCP connection already sends Authorization: Bearer pt_... |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pro_token | string | no | Pro account token (pt_...). Optional if the MCP connection already sends Authorization: Bearer pt_... |
| accept_overage_usd | string | no | Explicit overage consent, e.g. "1.50", only after the user approved. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pro_token | string | no | Pro account token (pt_...). Optional if the MCP connection already sends Authorization: Bearer pt_... |
| db | string | yes | The database URL returned at creation (or its bare s-... capability). |
| accept_overage_usd | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pro_token | string | no | Pro account token (pt_...). Optional if the MCP connection already sends Authorization: Bearer pt_... |
| confirm | string | no | Pass "cancel" only after the user has seen the consequences and approved. |
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; i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | yes | What was missing, confusing, or slow - or what worked well. Plain text, one short message. |
| category | string | no | Optional bucket for triage. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tmpstate or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest2ad6a3783698cd0e0f9da131bfedeb1ab233f2d434e6d2c2d240b4f203c0431c
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| create_database | no tags | |
| database_status | no tags | |
| list_documents | no tags | |
| get_document | no tags | |
| create_document | no tags | |
| update_document | no tags | |
| delete_document | no tags | |
| delete_collection | no tags | |
| delete_database | no tags | |
| extend_database | no tags | |
| pro_checkout | no tags | |
| pro_list_databases | no tags | |
| pro_create_database | no tags | |
| pro_attach_database | no tags | |
| pro_cancel | no tags | |
| send_feedback | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest2ad6a3783698cd0e
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Tmpstate can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.