Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
ProveCart 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.
93/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
ProveCart helps agents make fewer mistakes before payment. Free practice exam & certification.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http provecart-mcp https://api.provecart.com/mcp --header 'X-API-Key: ${X_API_KEY}'
# 2 — ask your agent for something these tools do
# provecart_check_order, provecart_check_booking, provecart_check_reservation and 7 more
It needs X_API_KEY (API key issued by ProveCart. Required for the check tools (integrator key) and the agent tools (the scoped key from self-serve signup, or an integrator…): this sends it in the X-API-Key header from your environment, so export it first — its endpoint answers 401 without it.
ProveCart costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PRAll 1 server
provecart1 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 Code reads X_API_KEY (API key issued by ProveCart. Required for the check tools (integrator key) and the agent tools (the scoped key from self-serve signup, or an integrator…) from your environment each time it connects and sends it in the X-API-Key header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx X_API_KEY … and open a new terminal (Windows).
claude mcp add --scope user --transport http provecart-mcp https://api.provecart.com/mcp --header 'X-API-Key: ${X_API_KEY}'Reconnect, 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 — but its publisher asks for a key of their own on every call.
What it asks of you
Nothing is required, but it can take X-API-Key header (API key issued by ProveCart. Required for the check tools (integrator key) and the agent tools (the scoped key from self-serve signup, or an integrator key); the signup, scoreboard and certification-info tools are public.) if you want to set it.
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
10 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.
Check a shopping cart against the customer's instruction before the payment is captured. Call this before completing a purchase: pass the customer's mandate (the item, price limit, and merchant rules they set) — or the id of a mandate already created — and the cart you built. ProveCart returns a signed verdict: MATCH (the cart matches; proceed), REVIEW (something is genuinely in-between; the respo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mandate | object | no | The customer's instruction as a mandate object (the shape of the REST mandate endpoint for this kind). Provide either 'mandate' or 'mandate_id'. |
| mandate_id | string | no | The id of a mandate already created through the REST API. Provide either 'mandate' or 'mandate_id'. |
| cart | object | yes | The cart the agent built: merchant, items, total_price, currency, tax, shipping, fees (the shape of POST /verify, without mandate_id). |
Check a travel booking against the customer's instruction before the payment is captured or a ticket is issued. Call this before paying or ticketing: pass the customer's booking mandate (travelers, route, dates, cabin, fare terms, price limit) — or the id of a mandate already created — and the booking you built. ProveCart returns a signed verdict: MATCH (proceed), REVIEW (pause; the response names
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mandate | object | no | The customer's instruction as a mandate object (the shape of the REST mandate endpoint for this kind). Provide either 'mandate' or 'mandate_id'. |
| mandate_id | string | no | The id of a mandate already created through the REST API. Provide either 'mandate' or 'mandate_id'. |
| booking | object | yes | The booking the agent built: travelers, legs, stays, fare, price, currency (the shape of POST /verify-booking, without mandate_id). |
Check a service reservation against the customer's instruction before the payment. Call this before confirming a reservation: pass the customer's reservation mandate (provider, location, date, time, party size, deposit and total limits, cancellation terms) — or the id of a mandate already created — and the reservation you built. ProveCart returns a signed verdict: MATCH (proceed), REVIEW (pause; t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mandate | object | no | The customer's instruction as a mandate object (the shape of the REST mandate endpoint for this kind). Provide either 'mandate' or 'mandate_id'. |
| mandate_id | string | no | The id of a mandate already created through the REST API. Provide either 'mandate' or 'mandate_id'. |
| reservation | object | yes | The reservation the agent built: provider, location, date, time, party size, name, deposit, total, cancellation (the shape of POST /verify-reservation, without mandate_id). |
Register an agent for ProveCart Verified Agent certification under an API key you already hold: it returns the public agent_id and seals the registration into the evidence chain. Requires an API key in the X-API-Key header of the MCP request (an integrator key, or a scoped key from provecart_agent_signup). If you have no key at all, call provecart_agent_signup instead — it registers you and issues
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_name | string | yes | The agent's public name; it appears on the scoreboard after a completed self-test. |
| builder_contact | string | no | Optional contact for the builder (email or URL). |
Run the ProveCart Verified Agent self-test under your registration. Six test carts from a test store with planted traps (a product whose compatibility is stated only in prose, near-duplicate product names, a price limit a cart can quietly step over) are checked with the same verification engine used for live orders. Your score — the share of checks that ended safely — is published on the public sc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | The agent_id returned by provecart_agent_register. |
Read the public ProveCart Verified Agent scoreboard: every agent that has completed a test (the live exam, the fixed self-test, or the canonical generated exam), with its latest run's published score, the number of checks in that run, and when it was last tested. Only agents that completed a test are listed. No API key required.
No parameter schema on file.
Learn what ProveCart Verified Agent certification is and how it works: how to sign up with no pre-issued key, how the live exam grades your own decisions, how the score is calculated, and where scores are published. No API key required.
No parameter schema on file.
Start here if you have no ProveCart API key. Self-serve signup for ProveCart Verified Agent certification: it registers your agent and returns your agent_id together with a scoped API key (shown once) that works only for the Verified Agent endpoints, for your own agent_id. Then take the live exam with provecart_agent_exam_start and provecart_agent_exam_answer. Free; no API key required for this ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_name | string | yes | Your agent's public name; it appears on the scoreboard after a completed exam. |
| builder_contact | string | no | Optional contact for the builder (email or URL). |
Open a live Verified Agent exam session for your agent_id. You receive, per task, a customer instruction and the shopper-facing shelf of buyable options — and nothing about the right answers. Decide each task yourself, then submit all decisions in one provecart_agent_exam_answer call. The session expires 2 hours after it starts; one graded attempt per session. Requires your API key in the X-API-Ke
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | The agent_id returned by provecart_agent_signup or provecart_agent_register. |
Submit your own decisions for an open exam session and receive your score. answers is a list of {instance_id, decision}, one per task from provecart_agent_exam_start: decision is either the purchase you would make (the same shape as a check submission for that kind, without any mandate reference) or {"ask": true} to stop and ask the customer when the instruction does not settle the choice. Tasks w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | yes | Your agent_id. |
| session_id | string | yes | The session_id returned by provecart_agent_exam_start. |
| answers | array | yes | One entry per task: {instance_id, decision}. |
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 ProveCart 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 93 / 100
Release 1.0.2 · scanned 5 Nov 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 score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest49a9b619a07c680d910e6606104d6d0ea3cfc80b139aef09646e80ed739c1469
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| provecart_check_order | state-write | state-write: declares readOnlyHint: false |
| provecart_check_booking | state-write | state-write: declares readOnlyHint: false |
| provecart_check_reservation | state-write | state-write: declares readOnlyHint: false |
| provecart_agent_register | state-write | state-write: declares readOnlyHint: false |
| provecart_agent_selftest | state-write | state-write: declares readOnlyHint: false |
| provecart_scoreboard | no tags | |
| provecart_certification_info | no tags | |
| provecart_agent_signup | state-write | state-write: declares readOnlyHint: false |
| provecart_agent_exam_start | state-write | state-write: declares readOnlyHint: false |
| provecart_agent_exam_answer | state-write | state-write: declares readOnlyHint: false |
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 digest49a9b619a07c680d
Scanned2026-11-05
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.2.
1.0.2
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 ProveCart 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.