Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Moda 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
Moda's buy-and-sell communities: find a group, check if a contact is really Moda, fix a listing.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http moda-mcp https://www.modacommunities.com/api/public-mcp/v1
# 2 — ask your agent for something these tools do
# find_moda_groups, check_moda_contact, check_facebook_group_link and 8 more
Moda 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 moda-mcp https://www.modacommunities.com/api/public-mcp/v1Reconnect, 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.
11 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.
Use when someone wants to buy, sell or talk about watches, cars, gold or jewelry, sneakers and other items and asks which Moda community fits or how to join. Returns Moda's official groups for the topic as JSON: name, what the group is for, how access works, approximate member count, the Facebook group link, Moda's page for it when one exists, any notice that a group is temporarily down with the g
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | The kind of community. Use all when unsure. |
| query | string | no | Optional words to narrow the list, matched against group names and descriptions. |
Use when someone was contacted by a person, number, email or business claiming to be Moda, or wants to know if one is real before trusting it. This is Moda's own scam check, the same one on modacommunities.com/verify. value: exactly one of an email address, a phone number, a link to a person's Facebook profile, or a business name. Returns JSON with verdict official, not_official or could_not_check
| Parameter | Type | Required | Notes |
|---|---|---|---|
| value | string | yes | One email, phone number, Facebook profile link or business name, as the person gave it. |
Use when someone has a link to a Facebook group or post and wants to know whether that group is an official Moda group. link: the facebook.com/groups/... address or a facebook.com/share/... link. Share links are opened on Moda's servers to find the group they point to. Returns JSON with verdict official, not_official or could_not_check, the group's name when it is official, and a plain sentence to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| link | string | yes | A Facebook group, post or share link. |
Use before someone posts a listing in a Moda group, or when their post was declined, to find words that Moda's automatic filters decline. text: the full listing as it will be posted. group: optional slug of the group it is for; leave it out to check every group. Returns JSON: each filtered word found, the groups whose filter catches it, words hidden with symbols or spacing, and the other common re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The listing text. |
| group | string | no | Optional group slug: tmc (The Moda Club (TMC)), modagoldplus (Moda Gold+), watchtrading (Moda Watch Club), 558871041349029 (Moda Watch Club: 10K & Under), watchbuying (Moda Watch: WTB/ISO), modaforum |
Use when someone gives a watch reference number, such as 126610LN or 5711/1A, and wants to know which watch it is. reference: the reference number as written. Returns JSON: brand, model, case size, material, production years, the nickname buyers use when there is one, and Moda's reference page link when one exists. Moda publishes no prices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reference | string | yes | A watch reference number. |
Use for questions about how Moda works: joining a group, approval times, membership, posting rules, declined posts, bans, the middleman, payments, refunds, reporting a problem or contacting the team. question: the person's question in their own words. Returns JSON with up to three of Moda's published help answers, word for word, each with its link, in Moda's published wording.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The question in plain words. |
Use when someone asks what is new at Moda, whether a Moda group is down, or about a recent launch, event or announcement. count: optional number of posts, 1 to 10 (default 5). Returns JSON: notices for any Moda group that is temporarily down and the group to use meanwhile, then the newest posts from The Feed (modacommunities.com/updates), each with its date, kind, title, a short summary and its li
| Parameter | Type | Required | Notes |
|---|---|---|---|
| count | integer | no | How many posts, 1 to 10. |
Use when someone's listing has words a Moda group's automatic filter declines, or they ask Moda to fix their post. This is the Post Checker's Fix my post, run on Moda's servers. text: the listing as written. group: optional slug of the group it is for; leave it out to fix it for every group at once. Returns JSON: the rewritten listing to copy, each change made (a brand name bent so the filter pass
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The listing text. |
| group | string | no | Optional group slug: tmc (The Moda Club (TMC)), modagoldplus (Moda Gold+), watchtrading (Moda Watch Club), 558871041349029 (Moda Watch Club: 10K & Under), watchbuying (Moda Watch: WTB/ISO), modaforum |
Use when someone asks what a watch or dealer term, abbreviation or nickname means, such as BNIB, LNIB, full set, hesalite, grey market, Hulk or Pepsi. term: the word or phrase as written. Returns JSON from Moda's glossary of about 276 terms: the meaning, an example where there is one, the references a nickname stands for, and the glossary link. Up to three close matches when the term is not exact.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| term | string | yes | The term, abbreviation or nickname. |
Use when someone names a watch rather than giving a reference number, such as Rolex Submariner, Daytona, Batman or Moonwatch, and wants to know the references. name: the brand, model or nickname in plain words. Returns JSON: Moda's reference pages that match, each with brand, model, reference, nickname, production years, a one-line summary and the page link. Moda publishes no prices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | A brand, model or nickname. |
Sends a report or request to Moda's team, the same as the form at modacommunities.com/report: a scam, an impersonator or a fake group; a deal dispute; a member conduct problem or ban appeal; group or chat access; a declined post; membership, advertising or billing; or a question for the team. Moda's team receives it as a case, routed to the right person, and the person gets a case number and a con
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The person's full name. |
| string | yes | The person's email address, where the confirmation and Moda's replies go. | |
| category | string | yes | deal-dispute (Deal & Transaction Disputes), scam-fraud (Scam & Fraud), member-conduct (Member Conduct), account-access (Account & Access), posting-listing (Posting & Listing), membership (Membership), |
| issue_type | string | no | deal-dispute: broken-deal (Broken deal or deal not honored), item-not-described (Item not as described), ghosting (Buyer or seller ghosting), slow-pay (Slow pay), shipping (Late shipping or shipping i |
| request_type | string | no | question (Question), incident (Incident), problem (Problem), feature-request (Feature Request), refund (Refund) |
| related_group | string | no | The Moda group it is about, or Not group specific. |
| description | string | yes | What happened or what the person needs, in their own words, with names, dates and amounts. |
| phone | string | no | Optional phone number. |
| facebook_profile | string | no | Optional: the person's own Facebook profile link or exact profile name. |
| other_party_profile | string | no | Optional: the Facebook profile link of the other person in a dispute or scam. |
| related_post_link | string | no | Optional: a link to the Facebook post or group involved. |
| amount | string | no | Optional: the amount of money involved, for deal disputes and billing. |
| order_number | string | no | Optional: an order or invoice number, for billing. |
| reference_check | string | no | Optional, for deal disputes and scams: whether a reference check was done before the deal. |
| agrees_to_terms | boolean | yes | true when the person has agreed to Moda's Terms and Privacy Policy (and, with a phone number, to calls and texts) for this report. |
- 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 Moda 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 | 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 |
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| find_moda_groups | no tags | |
| check_moda_contact | no tags | |
| check_facebook_group_link | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_listing_words | no tags | |
| look_up_watch_reference | no tags | |
| search_moda_help | no tags | |
| get_moda_news | no tags | |
| fix_my_listing | no tags | |
| explain_watch_term | no tags | |
| find_watch_by_name | no tags | |
| send_moda_report | 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
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.0.
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 Moda 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.