Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Somon.tj classifieds

REMOTE · MCP.SOMON.TJ

Search classified listings on Somon.tj (Tajikistan) and open listing details.

Available components

73 Trust /100

Last scanned (18 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 522 tokens (~104/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 76% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 73

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.somon.tj/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=somon.tj CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 7f4e7479f5094d0b0e1617090352a0c2
SANs: somon.tj, *.somon.tj
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.somon.tj. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tj. No DS 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=2592000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.somon.tj/mcp Verified 200
http (plaintext) http://mcp.somon.tj/mcp HTTPS enforced 301 https://mcp.somon.tj/mcp
MCP tools · 5 exposed · ~388 tokens

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 →

Tool Tokens
get_advert ~64

Listing details: description, attributes, photos, seller. No contacts: use reveal_contact.

NameTypeReqDescription
advert_idstringyesadvert_id from search_adverts, or a listing url.
language––Language of listing texts: one of ru, tg. Default ru.
NameTypeReqDescription
advert_idstringyesPass to reveal_contact as is.
attributesarray––
category_patharray––
contact_channelsarray–Channels the seller accepts; call reveal_contact to get them.
descriptionstring––
location–––
photosarray––
price–––
price_note–––
published–––
seller–yes–
titlestringyes–
urlstringyes–

No examples provided.

get_category_filters ~59

Filters available in a category (brand, model, year, storage...) for search_adverts.attributes.

NameTypeReqDescription
category_idintegeryesCategory from list_categories.
language––Language of listing texts: one of ru, tg. Default ru.
NameTypeReqDescription
category_idintegeryes–
filtersarrayyes–

No examples provided.

list_categories ~55

Marketplace categories, one level at a time. Use category_id in search_adverts.

NameTypeReqDescription
language––Language of listing texts: one of ru, tg. Default ru.
parent_id––Omit for top-level categories.
NameTypeReqDescription
categoriesarrayyes–
parent_id–yes–

No examples provided.

reveal_contact ~47

Seller's phone, WhatsApp or chat link. Call only when the user asks to contact the seller.

NameTypeReqDescription
advert_idstringyesadvert_id from search_adverts or get_advert.
NameTypeReqDescription
availablebooleanyes–
chat_url–––
message–––
phone–––
urlstringyesListing page on the marketplace site.
whatsapp_url–––

No examples provided.

search_adverts ~163

Search listings on the marketplace. Results never include seller contacts.

NameTypeReqDescription
attributes––Category filters from get_category_filters: {key: value} for select, {key: [values]} for multiselect, {key + '_min' / key + '_max': number} for range.
category_id––Category from list_categories.
language––Language of listing texts: one of ru, tg. Default ru.
limitinteger––
location––City or district name.
ordering–––
page_token––next_page_token of the previous result, same filters.
price_max–––
price_min–––
query––Free-text search, e.g. 'iphone 15 128gb'.
NameTypeReqDescription
advertsarrayyes–
location––Location the search was narrowed to.
next_page_token––Pass to search_adverts for more results.
pageintegeryes–
total––Matching listings, may be capped by the site.

No examples provided.

Install

How do I install the Somon.tj classifieds MCP server?

Somon.tj classifieds is a hosted endpoint at https://mcp.somon.tj/mcp, 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 · mcp.somon.tj

# add to Claude Code
claude mcp add --transport http tj-somon-listings 'https://mcp.somon.tj/mcp'
Common questions

What is the Somon.tj classifieds MCP server?

Somon.tj classifieds is an MCP server listed in the public MCP registry as tj.somon/listings. Search classified listings on Somon.tj (Tajikistan) and open listing details. This page covers its hosted endpoint (https://mcp.somon.tj/mcp).

Is the Somon.tj classifieds MCP server safe to use?

Somon.tj classifieds scores 73 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 Somon.tj classifieds MCP server expose?

Somon.tj classifieds exposes 5 tools: search_adverts, get_advert, reveal_contact, list_categories, get_category_filters. Their descriptions and schemas cost roughly 388 tokens of context every time the server is loaded.

Does the Somon.tj classifieds MCP server require authentication?

No. We connected to Somon.tj classifieds without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Somon.tj classifieds MCP server still maintained?

Somon.tj classifieds is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Somon.tj classifieds MCP server?

VerifyMCP ran 13 checks on Somon.tj classifieds, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.