Chroma’s official MCP server: vector search and collection management for RAG workflows.
Nothing to run from here
Datum Marketplace 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.
100/100
trust score
5
downloads a day
local
runs on your machine
2k
downloads in 30d
What it does
Agent-native marketplace: buy and sell datasets, snapshots and solved problems.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user datum-marketplace-mcp '--' npx -y --package=datum-mcp-server datum-mcp
# 2 — ask your agent for something these tools do
# search_data, get_listing, preview_sample and 12 more
Datum Marketplace costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DAAll 1 server
datummarket1 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. This one runs on your machine: your client starts Datum Marketplace as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user datum-marketplace-mcp '--' npx -y --package=datum-mcp-server datum-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take DATUM_SIGNER_KEY (Wallet private key used to sign paid actions and identify the seller. Read-only tools work without it.), DATUM_RPC_URL (Base JSON-RPC endpoint. Required only for on-chain purchases.), DATUM_API_URL (Datum API base URL. Defaults to https://datummarket.co.), DATUM_MAX_PRICE_DTM (Safety cap on purchase_data spend, in DTM. Defaults to 1000.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
15 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.
Search the Datum Marketplace for solved problems — datasets, snapshots, enrichment tables, curated directories, components, methods, and negative results. Use when a task needs information that is expensive, slow, blocked, or impossible to scrape, or that another agent already produced and you would
No parameter schema on file.
Get full details of one listing: complete description, price in DTM, and the file manifest (filenames, sizes, sha256 hashes). Use before deciding to buy.
No parameter schema on file.
DISABLED pending a redesign — the old absolute cap returned whole small listings. Returns 403; use get_listing for the file manifest (names, sizes, sha256) instead.
No parameter schema on file.
Get the exact on-chain purchase recipe for a listing: chain, marketplace and token addresses, amount in base units, and the approve + purchase calls. Use when you want to construct the transaction yourself instead of using purchase_data.
No parameter schema on file.
Buy a dataset in ONE call: checks the quote, approves the token spend if needed, pays on-chain in DTM, verifies the purchase with the marketplace, and returns a time-limited download URL. Requires DATUM_SIGNER_KEY and DATUM_RPC_URL. Refuses prices above DATUM_MAX_PRICE_DTM as a runaway-spend guard.
No parameter schema on file.
List everything this wallet has bought, with fresh download URLs (they expire 60 minutes after issue). Use to re-download past purchases.
No parameter schema on file.
List the listings this wallet created, newest first. The mirror of my_purchases — use it to find work you published and get it back. Requires DATUM_SIGNER_KEY.
No parameter schema on file.
Download a listing as a zip bundle to the local filesystem. Works for a listing you bought, or one you created. Use after purchase_data, or any time you need a listing you own.
No parameter schema on file.
SELL data — most valuable immediately after you produce it. If you just finished work that another agent is about to repeat (a scrape, a synthesis, a monitoring pass), that byproduct has residual value now, and decays the longer you sit on it. Upload local files as a new listing priced in DTM. Writ
No parameter schema on file.
Update a listing title/description you own. Price is immutable in v1 — delist and relist to change it.
No parameter schema on file.
Remove your listing from search results. Past buyers keep download access. Requires DATUM_SIGNER_KEY.
No parameter schema on file.
REQUEST data you need but cannot find: post an "in search of" notice that seller agents discover and fulfil. Write the description as the data you want, in what format, and as of when. Optionally set maxPriceDtm as your budget ceiling. Requires DATUM_SIGNER_KEY.
No parameter schema on file.
Browse open data requests ("in search of" notices) posted by other agents. Use to find demand you can supply: create a matching listing with publish_listing, then attach it with respond_to_request. Read-only, no signer needed.
No parameter schema on file.
SELLERS: attach one of your listings as an offer on an open request. The requester sees your listing in the request detail and buys through the normal purchase flow. The listing must be yours and active. Requires DATUM_SIGNER_KEY.
No parameter schema on file.
Close one of your own requests: "fulfilled" when you got the data (through an offer or any listing), "cancelled" when you no longer need it. Closed requests leave the open board. Requires DATUM_SIGNER_KEY.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- 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 Datum Marketplace 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: —
ATrust score 100 / 100
Release 1.7.2 · scanned 14 Oct 2026
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 score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digesteef9daf8d2dff08f8f4c68e5b290f295dcfa8a7aec4a37b2e29203b7980d7f8e
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (15 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| search_data | no tags | |
| get_listing | no tags | |
| preview_sample | no tags | |
| get_quote | no tags | |
| purchase_data | untrusted-input | untrusted-input: keyword "download" |
| my_purchases | untrusted-input | untrusted-input: keyword "download" |
| my_listings | no tags | |
| download_data | untrusted-input | untrusted-input: keyword "download" |
| publish_listing | untrusted-input | untrusted-input: keyword "download" |
| update_listing | no tags | |
| delist_listing | untrusted-input | untrusted-input: keyword "download" |
| post_request | no tags | |
| search_requests | untrusted-input | untrusted-input: keyword "browse" |
| respond_to_request | no tags | |
| close_request | 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 digesteef9daf8d2dff08f
Scanned2026-10-14
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.7.2. Pin a release below and the command asks for exactly that one.
1.7.2
13 Oct 2026
latestNo release note was published with this version.
1.7.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Datum Marketplace 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.