Moda
REMOTE · WWW.MODACOMMUNITIES.COM
Moda's buy-and-sell communities: find a group, check if a contact is really Moda, fix a listing.
Available components
Last scanned (2 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2772 tokens (~252/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.modacommunities.com/api/public-mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.modacommunities.com | CN=YR1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 6c8a2ededc39aef686e881fbfc42ab00654 |
| SANs: www.modacommunities.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.modacommunities.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| modacommunities.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.modacommunities.com/api/public-mcp/v1 | Verified | 200 | |
| http (plaintext) | http://www.modacommunities.com/api/public-mcp/v1 | HTTPS enforced | 308 | https://www.modacommunities.com/api/public-mcp/v1 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_facebook_group_link Check a Facebook group link ~113
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 pass on.
| Name | Type | Req | Description |
|---|---|---|---|
| link | string | yes | A Facebook group, post or share link. |
No output schema declared.
No examples provided.
check_listing_words Check a listing for filtered words ~299
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 reasons a post is declined that no word check can see. An empty list means no filtered words, not a guarantee the post goes up.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | 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… |
| text | string | yes | The listing text. |
No output schema declared.
No examples provided.
check_moda_contact Check a Moda contact ~178
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, what was matched (for example a team member's public name and role), a plain sentence summing up the result, and moda_rules: Moda's published wording on what it never asks for in a message. Facebook group and post links are not checked here.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | One email, phone number, Facebook profile link or business name, as the person gave it. |
No output schema declared.
No examples provided.
explain_watch_term Explain a watch-trade term ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | The term, abbreviation or nickname. |
No output schema declared.
No examples provided.
find_moda_groups Find Moda groups ~185
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 group to use meanwhile, and Moda's official steps for joining. topic: one of watches, cars, jewelry, lifestyle, specialty, premium (memberships by application) or all. query: optional words to narrow the list, such as rolex, golf or sneakers.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional words to narrow the list, matched against group names and descriptions. |
| topic | string | yes | The kind of community. Use all when unsure. |
No output schema declared.
No examples provided.
find_watch_by_name Find a watch by name ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A brand, model or nickname. |
No output schema declared.
No examples provided.
fix_my_listing Fix a listing for a Moda group ~306
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 passes, a word swapped or removed, and why), and any words that stop the post entirely, such as replica terms, where no rewrite is offered.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | 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… |
| text | string | yes | The listing text. |
No output schema declared.
No examples provided.
get_moda_news Get Moda's latest news ~121
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 link.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many posts, 1 to 10. |
No output schema declared.
No examples provided.
look_up_watch_reference Look up a watch reference ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | A watch reference number. |
No output schema declared.
No examples provided.
search_moda_help Search Moda's help answers ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question in plain words. |
No output schema declared.
No examples provided.
send_moda_report Send a report or request to Moda ~939
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 confirmation email. Sending it means the person agrees to Moda's Terms (https://www.modacommunities.com/terms) and Privacy Policy (https://www.modacommunities.com/privacy); when a phone number is included, also to Moda contacting them by phone or text (msg and data rates may apply, reply STOP to opt out). Required: name, email, category, description and agrees_to_terms. Optional: issue_type (from the category's list), request_type, related_group, phone, facebook_profile, other_party_profile, related_post_link, amount, order_number and reference_check. Returns JSON with the case number, or the reason it was not sent.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| amount | string | – | Optional: the amount of money involved, for deal disputes and billing. |
| 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)… |
| description | string | yes | What happened or what the person needs, in their own words, with names, dates and amounts. |
| string | yes | The person's email address, where the confirmation and Moda's replies go. | |
| facebook_profile | string | – | Optional: the person's own Facebook profile link or exact profile name. |
| issue_type | string | – | 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… |
| name | string | yes | The person's full name. |
| order_number | string | – | Optional: an order or invoice number, for billing. |
| other_party_profile | string | – | Optional: the Facebook profile link of the other person in a dispute or scam. |
| phone | string | – | Optional phone number. |
| reference_check | string | – | Optional, for deal disputes and scams: whether a reference check was done before the deal. |
| related_group | string | – | The Moda group it is about, or Not group specific. |
| related_post_link | string | – | Optional: a link to the Facebook post or group involved. |
| request_type | string | – | question (Question), incident (Incident), problem (Problem), feature-request (Feature Request), refund (Refund) |
No output schema declared.
No examples provided.
How do I install the Moda MCP server?
Moda is a hosted endpoint at https://www.modacommunities.com/api/public-mcp/v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.modacommunities.com
claude mcp add --transport http vadimmoda-moda 'https://www.modacommunities.com/api/public-mcp/v1'
What is the Moda MCP server?
Moda is an MCP server listed in the public MCP registry as io.github.VadimModa/moda. Moda's buy-and-sell communities: find a group, check if a contact is really Moda, fix a listing. This page covers its hosted endpoint (https://www.modacommunities.com/api/public-mcp/v1).
Is the Moda MCP server safe to use?
Moda scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Moda MCP server expose?
Moda exposes 11 tools: find_moda_groups, check_moda_contact, check_facebook_group_link, check_listing_words, look_up_watch_reference, and 6 more. Their descriptions and schemas cost roughly 2,562 tokens of context every time the server is loaded.
Does the Moda MCP server require authentication?
No. We connected to Moda without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Moda MCP server still maintained?
Moda is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.