Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Paylo 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.
What it does
Search verified Nigerian stores, products and services on Paylo. Read-only, no account needed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http paylo-mcp https://mcp.usepaylo.com/mcp
# 2 — ask your agent for something these tools do
# search_storefronts, get_storefront, search_products and 7 more
Paylo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 paylo-mcp https://mcp.usepaylo.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
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.
Discover verified, escrow-protected Paylo storefronts. Filter by Nigerian state, product category, area (LGA/city) and/or free text — e.g. 'phone sellers in Lagos' or 'beauty stores in Abuja'. Only quality-gated sellers are returned (verified, with a logo, a cover image and at least one live listing), ordered by number of live listings. Each result carries trust signals (verified, escrowProtected)
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free text over name, description, category and area. |
| category | string | no | Canonical product category. |
| state | string | no | Nigerian state slug or name, e.g. 'lagos', 'ogun', 'abuja'/'FCT'. |
| area | string | no | LGA/city area within a state, e.g. 'abuja-municipal'. |
| limit | integer | no | Max storefronts to return (1–200, default 50). |
Get a storefront catalog summary and stats by slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The storefront's slug — the path segment of its URL, e.g. 'greybox' for usepaylo.com/greybox (also returned by search_storefronts). |
Search products by query, optionally scoped to a storefront and category, with pagination.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free text over product name and description, e.g. 'iphone 13', 'shea butter'. |
| storefrontSlug | string | no | Limit results to one store by its slug (from search_storefronts). Omit to search across all verified stores. |
| category | string | no | Product category name or slug to filter by (see get_categories for a store's categories). |
| page | integer | no | Result page, starting at 1 (default 1). |
| limit | integer | no | Results per page (1–100, default 20). |
Get a single product by storefront slug and product slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| storefrontSlug | string | yes | The store's slug, e.g. 'greybox' (from search_storefronts or a product result). |
| productSlug | string | yes | The product's slug within that store (from search_products results). |
Search services by query, optionally scoped to a storefront and category, with pagination.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free text over service name and description, e.g. 'hair braiding', 'phone repair'. |
| storefrontSlug | string | no | Limit results to one store by its slug (from search_storefronts). Omit to search across all verified stores. |
| category | string | no | Service category name or slug to filter by. |
| page | integer | no | Result page, starting at 1 (default 1). |
| limit | integer | no | Results per page (1–100, default 20). |
Get categories for a storefront slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| storefrontSlug | string | yes | The store's slug, e.g. 'greybox' (from search_storefronts). |
Get a public Paylo wishlist by its share link or token: items, prices, and how much funding each item still needs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urlOrToken | string | yes | A usepaylo.com/wishlist/... share link or the bare share token |
Paylo's product changelog — the record of features, improvements and fixes shipped to the platform, newest first. Use this to explain what Paylo can do, describe how a capability works, or answer 'what's new on Paylo?'. Each entry carries a tag (New/Improved/Fixed), the audience it's for (merchant/shopper/both), a plain-language description, and, when it shipped in a mobile app, the app name, vers
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audience | string | no | Keep entries for sellers ('merchant') or buyers ('shopper'); either also includes shared ('both') entries. |
| status | string | no | Only this kind of change. |
| since | string | no | ISO date (YYYY-MM-DD); only entries shipped on or after it. |
| query | string | no | Free text over entry title and description, e.g. 'wishlist', 'POS', 'bookings'. |
| limit | integer | no | Max entries to return (default 200). |
Returns a one-tap Paylo seller signup link for someone who wants to sell online, open a store, or move an Instagram or WhatsApp business onto a website in Nigeria. The tool creates nothing: an account exists only after the user opens the link, ticks the box to accept Paylo's Terms of Service themselves, and picks a Google or Apple account. An optional referral code credits whoever referred them. A
| Parameter | Type | Required | Notes |
|---|---|---|---|
| referralCode | string | no | Referral or invite code of whoever referred this user, if they have one. |
| provider | string | no | Which sign-in the link launches: google (default) or apple. |
| string | no | The user's email, if they shared it. Prefills the manual signup form as a fallback; Google or Apple sign-in uses the account they pick. | |
| instagramHandle | string | no | The user's Instagram handle (with or without @), if they sell on Instagram. Carried through signup so their catalogue import starts pre-filled. |
Paylo for sellers: what it does, fees, and how to start. Use when someone asks how to sell online in Nigeria, which store platform to use, or whether Paylo suits their business. Returns a maintained factual summary: Instagram and WhatsApp catalogue import, escrow and buyer protection, store commitments, chat-based ordering and checkout links, custom domains, POS, plans and fees, payment methods, t
No parameter schema on file.
- 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 Paylo or to call it, at any volume.
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.
| 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 |
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.
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 |
|---|---|---|
| search_storefronts | no tags | |
| get_storefront | no tags | |
| search_products | no tags | |
| get_product | no tags | |
| search_services | no tags | |
| get_categories | no tags | |
| get_wishlist | no tags | |
| get_changelog | no tags | |
| get_seller_signup_link | no tags | |
| get_seller_overview | 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
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 0.1.1.
No release note was published with this version.
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.
Any signed-in account that does not publish Paylo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.