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
Lucerna Noetica 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.
16
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Agent-native commerce: real quotes, reversible holds, and a whole business you own.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http lucerna-noetica-mcp https://platform.lucernanoetica.com/v1/mcp
# 2 — ask your agent for something these tools do
# platform_catalog, escrow_shapes, market_walk and 13 more
Lucerna Noetica costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LUAll 1 server
lucernanoetica1 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 lucerna-noetica-mcp https://platform.lucernanoetica.com/v1/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.
WHAT THIS PLATFORM ITSELF SELLS — its own add-ons and subscription lines, NOT the goods in its market. Call this when someone asks what the platform offers, what it costs, what plans or add-ons or extensions exist, whether there is a subscription, or what a shop can add to itself — agent memory, video generation, mailboxes, customer accounts, turning the platform fee off. THIS IS A DIFFERENT QUEST
No parameter schema on file.
How money can be arranged here, matched to what the owner or their customer actually said. Two registers: the DEPOSIT LADDER (what happens when someone cancels — sealed onto an escrow hold at open and enforced by the arbiter against that recorded copy, never a later edit) and the HOLD SHAPE (how the money sits when there is no appointment). Pass describe with their own words and you get the shap
| Parameter | Type | Required | Notes |
|---|---|---|---|
| describe | string | no | what they said, in their own words — 'weddings, give them a week', 'a bond they get back', 'pay whoever wins'. Omit for the whole catalog. |
Walk the market as a place. Call it with NOTHING to stand at the gate and see which quarters exist — categories, storefronts, tags, kinds, sizes in stock and the price band across every listed shop, each with how many shops and items are in it. Then pass any of category/store/tag/kind/size/format/price_min_cents/price_max_cents to walk into a row: the surviving shops come back with
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | walk one category, e.g. 'T-Shirts' — from the gate's quarters |
| store | string | no | walk one storefront within the shops, e.g. 'Merch' |
| tag | string | no | narrow by a flat tag, e.g. 'heavyweight' |
| kind | string | no | narrow by kind: physical, digital or service |
| size | string | no | narrow by size — a word or a code, 'large' and 'L' are the same question |
| format | string | no | narrow by file format, e.g. 'obj', '3mf', 'stl' — matched only against the format PROVED by reading the file, never a filename or a tag |
| price_min_cents | number | no | cheapest acceptable price, in minor units |
| price_max_cents | number | no | dearest acceptable price, in minor units |
| in_stock | boolean | no | default true — pass false to include sold-out rows in the walk |
| from | string | no | instead of predicates: a shop slug, to see who else trades on its row |
Find shops in the Lucerna market by what they do, what they say about themselves, AND WHAT THEY ACTUALLY STOCK. Use this when you know what you are shopping for but not which shop — 'a barber in Denver', 'heavyweight black tee'. Words are matched against each shop's own prose and against its live shelf — titles, descriptions, categories, tags and variant labels — so you can search for the PRODUCT
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | words to match against a shop's name, tagline, description, mission and location AND the words on its live shelf (titles, descriptions, categories, tags, variant labels) — every word must appear somew |
| can | array | no | require ALL of these capabilities: bookings (takes appointments), shop (sells goods), quote (quotes custom work by walking a concierge), tips |
| limit | integer | no | how many shops to return (default 24, max 100) |
| offset | integer | no | skip this many — page with total from the answer |
FILE A TICKET on Lucerna itself — the platform's own homework list. Three things put you here: a verb that does not exist (missing), a door that answered and its answer is not true (wrong), or a door that worked and the RESULT was bad — a page that built ugly, an answer that was thin, a refusal that named a way out this caller does not have (poor). The third one matters as much as the other
| Parameter | Type | Required | Notes |
|---|---|---|---|
| want | string | yes | one sentence: what you were trying to do that this platform could not do, or did badly |
| kind | string | no | missing — no such verb, nothing to call. wrong — a door answered and the answer is not true. poor — it worked and the result was bad. Leave it off rather than guessing. |
| expected | string | no | the acceptance line: what a correct answer would have looked like, concrete enough to check — e.g. 'the owner names a percentage and the shop’s cut on each seller sale becomes that number' |
| answered | string | no | what the door actually said, quoted short — the refusal text, the wrong value, or the thin result that was not good enough. The most useful field here. |
| surface | string | no | the tool or verb you tried, if you know it — e.g. front.set, checkout_intent. verb works as a name for this too |
| verb | string | no | the same thing as surface, by the word you probably reached for first |
| shop | string | no | the shop you were working on, if there was one |
WHERE YOUR TICKET GOT TO. Call it with the pg_… id report_gap handed you and you get that ticket's state, what we shipped, THE TEST YOU CAN RUN to check us, and the whole conversation on it. Three states and the middle one is the point: open — on the list, nobody has claimed a fix. pending — we shipped something we believe closes it and we are waiting for YOU to run the verify line and s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | no | your ticket id from report_gap, pg_…. Leave it off for the roadmap of what is being worked on. |
| limit | integer | no | roadmap only: how many rows (default 40, max 200) |
ANSWER ON YOUR TICKET — and, when it is pending, CLOSE IT OR SEND IT BACK. verdict: "fixed" means you ran the verify line from gap_check and it works: the ticket closes stamped as confirmed by the reporter. verdict: "still_broken" means you ran it and it does not: the ticket goes straight back onto the queue, red, with your sentence as the reason it bounced — no re-filing, and that line is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | the ticket id, pg_… |
| message | string | no | what you want to say — for still_broken, what is still wrong when you run the test |
| verdict | string | no | only on a pending ticket: fixed closes it, still_broken returns it to the queue. Leave it off to add to the thread without deciding. |
What a Lucerna shop is: its name, what it can actually do (bookings, a shop, tips, a concierge…), and the public doors a visitor or an agent can open. Use market_search first if you do not already know the shop's slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop | string | yes | the shop's slug, e.g. 'turf-and-co' |
The shop's concierge as a document: the questions it asks, the catalog it prices against, the formula, and how it ends. Read this to know what a walk will ask before you start one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop | string | yes | the shop's slug |
Ask a shop's brain a question in plain words — 'is this turf good for dogs', 'does the relaxed tee run small', 'do you have it in stock'. Answers come ONLY from the shop's own ratified spec sheet (every row cited to its source document) plus a LIVE read of the shop's stock and services at answer time (goods rows carry ids, variants, a preview image link you can show the person, the owner's own des
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop | string | yes | the shop's slug |
| question | string | yes | the question, plain words — one subject per ask beats a compound question |
What it costs to ship an order, and the token that lets you buy it. REQUIRED before checkout_intent on anything physical: an escrow hold is struck at an exact amount and cannot be topped up afterwards, so the postage has to be inside it. Pass the same items and the same ship_to you will check out with, and you get the carrier services this shop can actually sell to that address, each with a pr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop | string | yes | the shop's slug |
| items | array | yes | the same lines you will check out with — the bag decides the box |
| ship_to | object | yes | where it is going — the SAME object you will hand checkout_intent |
| buyer_email | string | yes | the buyer's REAL email — the same one checkout_intent will carry |
WHAT BECOMES OF THE MONEY, so you can tell your human before they agree: it sits in an on-chain escrow that stays THEIRS, and it reaches the shop only when the buyer themselves acts on the link in their own mail — this platform cannot move it, by construction, which is why that link never comes to you. If nobody acts before the window closes (72 hours by default), the hold goes home to the buyer o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop | string | yes | the shop's slug |
| items | array | yes | what to hold — listing ids from the shop's public shelf (concierge_ask's live.goods rows carry them) |
| buyer_email | string | yes | the buyer's REAL email — the release code lands there, and without it the order can never settle |
| buyer_wallet | string | yes | the wallet this hold REFUNDS to (G + 55 base32) — your own purse when you hold one, and then you fund it yourself; otherwise the buyer's own key |
| ship_to | object | no | shipping address, REQUIRED for anything physical — pass it as an object, not as text |
| rate_token | string | no | the shipping token from shipping_options, for the service you picked. REQUIRED for anything physical: the hold is struck at an exact amount and cannot be topped up, so postage has to be inside it. It |
| because | string | no | one plain sentence naming the brief-line that drove this buy (e.g. 'within the tees ceiling of $40.00') — it rides the order email so your human reads WHY, in their own document's words |
| fund_asset | string | no | what the funding wallet SPENDS: 'xlm' (default), 'usdc' or 'eurc' — the hold itself is always denominated in XLM; a non-XLM choice funds it by path payment from that asset |
Where an order you opened stands, and what each answer MEANS for the money. Funded but not yet acted on = it sits in escrow and is still the buyer's. Completed = the buyer acted from their mail and the shop has been paid. Gone home = the buyer declined and it is back with them. Expired = the window closed untouched and it went back on its own. Read live off the shop's rail: whether the hold is fun
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop | string | yes | the shop's slug |
| order_ref | string | yes | the order reference from checkout_intent, e.g. 'ord_…' |
What a shop sells TIME for, and when it is actually free: its services with their real prices and deposits, plus the openings for one of them on a given day. Read this before booking_intent — the shop's calendar is the authority on what exists.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop | string | yes | the shop's slug |
| service | string | no | a service id from a previous call — with it, openings come back too |
| day | string | no | the day to look at, YYYY-MM-DD (defaults to today; an empty openings means that DAY is closed or full — openings_note in the answer names the next day that has any) |
WHAT BECOMES OF THE MONEY: it sits in an on-chain escrow that stays the buyer's, and it reaches the shop only when the buyer acts on the link in their own mail — this platform cannot move it, by construction. A hold nobody acts on goes home when its window closes. IF THE APPOINTMENT IS CANCELLED, the shop's own cancellation terms decide, and they were SEALED onto this hold when it opened: the free
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop | string | yes | the shop's slug |
| service | string | yes | the service id from booking_offer |
| starts_at | string | yes | the opening you want, ISO — from booking_offer's list |
| buyer_name | string | yes | who the appointment is for |
| buyer_email | string | yes | the buyer's real inbox — the release code lands there, not here |
| buyer_wallet | string | yes | the wallet this deposit REFUNDS to (G + 55 base32) — your own purse when you hold one, and then you fund it yourself; otherwise the buyer's own key |
| note | string | no | anything the shop should know |
| because | string | no | the brief-line that drove this booking — it rides the buyer's mail |
Walk a shop's concierge one turn at a time and get a real quote. Omit walk to start (you get the first question and a walk id); pass walk + answer for each turn. The shop mails the quote at the end, so answer the email question with an address the person you are shopping for actually reads. Deterministic: no model on our side, and the whole conversation is sealed as a receipt the shop owner
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop | string | yes | the shop's slug |
| walk | string | no | the walk id from a previous call — omit to start a new conversation |
| answer | string | no | your answer to the question the last call asked |
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 Lucerna Noetica 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. 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 1.18.2.
1.18.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 Lucerna Noetica 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.