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
Wever Labs Agent Products 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.
27
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Agent commerce: 27 tools, 10 production services, signed authority, planning, Base USDC x402.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http wever-labs-agent-products-mcp https://weverlabs.com/mcp
# 2 — ask your agent for something these tools do
# wever_delegated-authority, wever_agent-paid-workflow, wever_unified-agent-checkout and 24 more
Wever Labs Agent Products costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
COAll 1 server
CodeWever1 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 wever-labs-agent-products-mcp https://weverlabs.com/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
27 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.
Issue signed mandates and operator-approved action grants, then let credentialed agents consume them to create immutable work-order records. Records do not perform work, deliver results or authorize payment. Operating boundary: Operators issue mandates and approve each exact action grant with an issuance idempotency key. Only the bound credentialed agent may consume a grant; each action grant atom
No parameter schema on file.
Prepare an ordered sequence of supported planning and computation steps with explicit required fields. No step is executed, no quote obtained, and no payment, authority or delivery is performed. Operating boundary: Prepared computation on caller-supplied data only. No authority, payment, execution, proof verification, delivery or persistence. Existing credentials and signed grants remain required
No parameter schema on file.
Itemize and total caller-supplied USD estimates for supported computations. This is not a provider quote, checkout session, payment request or authority grant. Operating boundary: Prepared computation on caller-supplied data only. No authority, payment, execution, proof verification, delivery or persistence. Existing credentials and signed grants remain required for any separate action. POST /api/
No parameter schema on file.
Paid URL: 1.00 USDC on Base; 10 signed-wallet free calls shared over rolling 30 days. Free computation: /api/mcp or /api/service-resolver. Read the backend 402 body for x402 terms. Compare explicit submitted evidence labels and return exact matched and missing items. This does not read or verify document contents. Operating boundary: The computation uses supplied data only and performs no provider
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: builds a receipt-passport envelope from supplied fields and a locally generated sample run. It does not retrieve or verify completed work or supplied proof. Generated receipt, verification and handoff fields are not evidence of production execution. Create a short, portable proof object for a completed rail run. Agents use it to verify receipt state wi
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: renders a generated example return package and receipt status using supplied or generated identifiers. It does not retrieve a stored package or establish that work completed. Read a rail return package in a clean shape. Agents get JSON. Humans get the same facts in a page that shows what was checked, what is missing, and what proof was issued. Operatin
No parameter schema on file.
Evaluate explicit caller-reported scope, budget, usage, expiry and per-action fee limits. Returns a would-allow or would-deny preview; creates no authority and verifies no account balance. Operating boundary: Prepared computation on caller-supplied data only. No authority, payment, execution, proof verification, delivery or persistence. Existing credentials and signed grants remain required for an
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: checks whether a callback URL starts with HTTPS and returns an example health response. It does not contact the receiver or verify an acknowledgment, availability or delivery. Check whether a callback receiver is alive, accepts proof payloads, and returns an acknowledgment shape an agent can trust. Operating boundary: Validates callback receivers befor
No parameter schema on file.
Validate a task against a supported computation and prepare its fixed POST request. Semantic validation uses a local deterministic dry run. No request is submitted, worker assigned or result delivered. Operating boundary: Prepared computation on caller-supplied data only. No authority, payment, execution, proof verification, delivery or persistence. Existing credentials and signed grants remain re
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: compares caller-supplied budget, requested fee and allowed rails. Its allow/deny result is a sample policy preview, not validated authority. It does not load an allowance, enforce remaining runs or callbacks, or persist a budget change. Return allow or deny decisions before an agent exceeds permitted runs, fees, rails, or callback destinations. Operati
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: prepares an SLA policy template from supplied values or defaults. It does not record an agreement, monitor a service, schedule retries or enforce a response deadline. Create an operational promise around a rail run: response expectation, callback requirement, retry count, proof requirements, and failure behavior. Operating boundary: Records the operati
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: returns supplied or default example statistics and calculates a sample callback rate. It does not read operational records or verify reputation. Default counts and generated last-seen timestamps are not observations of agent activity. Show proof-based trust signals for an agent or provider: completed runs, verified receipts, callback success, denied at
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: classifies payment-reference text and checks for simple unsupported or expired substrings. It does not verify payment, ownership, expiry or a signed mandate. A usable-reference result grants no authority to run or spend. Take a payment reference and return what an agent can safely do with it: verified, pending, approved, allowed rail, amount, expiratio
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: builds an example x402 challenge and binding hash from a supplied or default payment header. It does not verify a payment, prevent replay, settle funds or authorize resource access. Its unlock state is simulated. Accept x402-style optional authority references, bind them to a requested rail, and return unlock, receipt, and proof fields. Operating bound
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: parses mandate-reference text and hashes a binding to a generated sample receipt. It does not verify an AP2 signature, principal, merchant, budget or expiry, and it grants no payment or execution authority. Accept AP2-style mandate references, check bounded authority, and bind the mandate to rail run receipt proof. Operating boundary: Accepts AP2-style
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: assembles a handoff envelope and hash from supplied data, with sample package and receipt identifiers when omitted. It does not verify the referenced proof, deliver the handoff or authorize the receiving agent. Package completed work so another agent can pick it up: task summary, return package, exception object, receipt passport, callback target, and
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: generates five example proof-event categories with new identifiers and timestamps. It does not read or write an inbox. Its completed, recorded and acknowledged states are sample events, not operational evidence. Read a single view of completed runs, receipts, callback events, exceptions, handoffs, and status events. Operating boundary: Shows proof even
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: generates an example rail package, receipt and transcript locally. No external rail work runs. Its passed state and repeatability score describe generated sample output and are not measured production results. Test PacketOps and DiligenceOps with sample data, then start a agent run with the same rail shape. Operating boundary: Lets agents test rail sha
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: previews a release decision from truthy supplied proof labels and an exception flag, with a generated sample receipt reference. It does not verify evidence, reserve or release funds, or create an enforceable escrow. Create a pending completion authority record that releases only when the required proof package exists. Operating boundary: Creates pay-wh
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: prepares an example invoice-reference object for review. Its queued label does not represent a real queue entry. It does not create a stored invoice, send a bill, collect payment or record an operator decision. Create an invoice-style reference for a rail run when instant checkout is not the right payment flow. Operating boundary: Creates invoice-style
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: previews a permission decision using caller-supplied allowed actions and a fixed list of consequential actions. It does not authenticate a principal, read a ledger, persist permissions or grant execution authority. Track what an agent is allowed to do, what requires approval, what changed, and what must be denied before action. Operating boundary: Reco
No parameter schema on file.
Paid URL: 0.10 USDC on Base; 10 signed-wallet free calls shared over rolling 30 days. Free computation: /api/mcp or /api/service-resolver. Read the backend 402 body for x402 terms. Prepare a validated DiligenceOps task for a specific Connect recipient. Submission, recipient permission and execution remain separate steps. Operating boundary: The computation uses supplied data only and performs no p
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: builds a decision-packet template with fixed rationale and ranks options in submitted order, recommending the first option. It does not evaluate the supplied constraints or establish which option is best. Turn messy options into a decision packet with pros, cons, risks, unknowns, constraints, recommendation, and human decision point. Operating boundary
No parameter schema on file.
Unavailable historical backend. Sandbox/demo: classifies supplied filenames using invoice and contract substrings and flags names containing copy. This bounded filename heuristic does not inspect file contents, verify duplicate content, move or delete files, or perform the cleanup implied by its generated receipt identifier. Classify files, extract document metadata, detect duplicates, suggest des
No parameter schema on file.
Paid URL: 0.10 USDC on Base; 10 signed-wallet free calls shared over rolling 30 days. Free computation: /api/mcp or /api/service-resolver. Read the backend 402 body for x402 terms. Inventory submitted MCP tool declarations and flag missing or consequential annotations. This does not connect to a server or grant authority. Operating boundary: The computation uses supplied data only and performs no
No parameter schema on file.
Paid URL: 0.25 USDC on Base; 10 signed-wallet free calls shared over rolling 30 days. Free computation: /api/mcp or /api/service-resolver. Read the backend 402 body for x402 terms. Summarize supplied service health and queue observations into deterministic priorities. No private records are fetched and no activity is invented. Operating boundary: The computation uses supplied data only and perform
No parameter schema on file.
Prepare a reference envelope and deterministic source/destination binding digest. References and supplied hashes remain unverified. No destination is contacted, no acknowledgment is obtained, and nothing is delivered or persisted. Operating boundary: Prepared computation on caller-supplied data only. No authority, payment, execution, proof verification, delivery or persistence. Existing credential
No parameter schema on file.
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 Wever Labs Agent Products 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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 0.4.0.
0.4.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 Wever Labs Agent Products 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.