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.

com.tapuzinski/market

REMOTE · WWW.TAPUZINSKI.COM · SCANNED SEP 27

Israel hyperlocal marketplace for second-hand home goods: read-only listing search.

+3 this week 73 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 486 tokens (~162/item across 3 items; 3 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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Install

How do I install the com.tapuzinski/market MCP server?

com.tapuzinski/market is a hosted endpoint at https://www.tapuzinski.com/api/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 · www.tapuzinski.com

# add to Claude Code
claude mcp add --transport http com-tapuzinski-market 'https://www.tapuzinski.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-tapuzinski-market": {
      "url": "https://www.tapuzinski.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-tapuzinski-market": {
      "type": "http",
      "url": "https://www.tapuzinski.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-tapuzinski-market]
url = "https://www.tapuzinski.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tapuzinski-market": {
      "type": "remote",
      "url": "https://www.tapuzinski.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-tapuzinski-market --url 'https://www.tapuzinski.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-tapuzinski-market:
    url: "https://www.tapuzinski.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-tapuzinski-market": {
      "Transport": "http",
      "Url": "https://www.tapuzinski.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-tapuzinski-market -t streamable-http -u 'https://www.tapuzinski.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-tapuzinski-market": {
      "type": "http",
      "url": "https://www.tapuzinski.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
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 27 Sept 2026 · Probed https://www.tapuzinski.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.tapuzinski.com CN=YR1,O=Let's Encrypt,C=US 12 Sept 2026 11 Dec 2026 RSA 2048 SHA256-RSA 6fe8cfbab025b5284da1ba9b4adf958f8f2
SANs: *.tapuzinski.com, tapuzinski.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.tapuzinski.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
tapuzinski.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=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://challenges.cloudflare.com https://telegram.org; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://bxwkaafgbrwdrgalxhky.supabase.co; font-src 'self' data:; connect-src 'self' blob: https://bxwkaafgbrwdrgalxhky.supabase.co wss://bxwkaafgbrwdrgalxhky.supabase.co https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com; frame-ancestors https://web.telegram.org https://webk.telegram.org https://webz.telegram.org; worker-src 'self' blob:; form-action 'self'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(self), camera=(), microphone=(), payment=(), usb=(), 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.tapuzinski.com/api/mcp Verified 200
http (plaintext) http://www.tapuzinski.com/api/mcp HTTPS enforced 308 https://www.tapuzinski.com/api/mcp
MCP tools · 3 exposed · ~400 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_listing ~81

Показать одно объявление Tapuzinski: заголовок, описание, цену, состояние и ссылки на фото. Зови после search_listings, когда человек выбрал вещь и хочет подробностей. Продавца и его контакты не отдаёт: написать можно только из самого приложения.

NameTypeReqDescription
idstringyesUUID объявления из search_listings

No output schema declared.

No examples provided.

list_taxonomy ~54

Перечислить доступные разделы, категории, города и допустимые значения фильтров Tapuzinski. Зови ПЕРЕД search_listings, чтобы подставить правильные слаги города и категории.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_listings ~265

Найти б/у вещи и другие объявления на гиперлокальном маркетплейсе Tapuzinski (Израиль). Зови, когда человек спрашивает, что продаётся рядом с конкретным городом, по категории, до какой-то цены или по свободному описанию вещи. Отдаёт только публичные объявления: без продавца, без контактов и без точного адреса.

NameTypeReqDescription
categorystring–Слаг категории из list_taxonomy
citystring–Слаг города из list_taxonomy, например petahTikva
conditionarray–Состояние вещи
limitinteger––
max_pricenumber–Верхняя граница цены в шекелях; 0 — только «даром»
offsetinteger––
querystring–Свободный текст: «диван», «стиральная машина»
radius_kminteger–Радиус от центра города; по умолчанию 25 км, без города — вся страна
sortstring–По умолчанию distance при названном городе, иначе newest
verticalstring–Раздел из list_taxonomy; без него — все доступные

No output schema declared.

No examples provided.

Common questions

What is the com.tapuzinski/market MCP server?

com.tapuzinski/market is an MCP server listed in the public MCP registry as com.tapuzinski/market. Israel hyperlocal marketplace for second-hand home goods: read-only listing search. This page covers its hosted endpoint (https://www.tapuzinski.com/api/mcp).

Is the com.tapuzinski/market MCP server safe to use?

com.tapuzinski/market 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 com.tapuzinski/market MCP server expose?

com.tapuzinski/market exposes 3 tools: search_listings, get_listing, list_taxonomy. Their descriptions and schemas cost roughly 400 tokens of context every time the server is loaded.

Does the com.tapuzinski/market MCP server require authentication?

No. We connected to com.tapuzinski/market without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.tapuzinski/market MCP server still maintained?

com.tapuzinski/market is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.