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.

Usta-Bul

REMOTE · USTA-BUL.COM

Türkiye'de usta ve firma bulma: kategori, il ve ilçeye göre arama, profil, puan ve yorumlar.

Available components

+3 this week 77 Trust /100

Last scanned (17 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security83
  • 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 975 tokens (~162/item across 6 items; 6 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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
    • The server rewrote its instructions, which are the text every model session reads security
  • 20 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 18 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 70% → 87% ▲ functional
    • New tool “talep_olustur” functional
    • New tool “talep_onayla” functional
  • 16 Nov 26 +1

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

  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 14 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
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://usta-bul.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usta-bul.com CN=YE1,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA384 6eceaebebb81c21907eaeee2ded68e82aa9
SANs: *.usta-bul.com, usta-bul.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of usta-bul.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
usta-bul.com. DS published 2371 13 Verified
usta-bul.com. Verified address RRset verified with the apex keys
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=15552000
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(self)

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://usta-bul.com/mcp Verified 200
http (plaintext) http://usta-bul.com/mcp HTTPS enforced 301 https://usta-bul.com/mcp
MCP tools · 6 exposed · ~887 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
kategoriler ~25

Tüm hizmet kategorilerini ve her birindeki aktif usta sayısını listeler.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

konumlar ~45

İlleri listeler; il verilirse o ilin ilçelerini ve usta sayılarını döner.

NameTypeReqDescription
ilstring–İl slug (ör. "bursa")

No output schema declared.

No examples provided.

talep_olustur ~425

Kullanıcı adına Usta-Bul'a iş talebi bırakır: bölgedeki uygun ustalar talebi görür, kullanıcıyı arar ya da teklif verir. Kullanıcının açık onayıyla çağırın (kullanici_onayi: true). Kullanıcının cep telefonuna 6 haneli doğrulama kodu gönderilir; kodu kullanıcıya sorup talep_onayla aracına talep_id ile birlikte verin. Telefon ve ad yalnız ustalarla paylaşılır.

NameTypeReqDescription
aciklamastringyesYapılacak iş: ne, ne kadar, varsa ölçü/marka. Telefon, adres, bağlantı yazmayın.
adstringyesKullanıcının adı
butcestring–Bütçe aralığı (isteğe bağlı)
hatirlatboolean–Dönemsel işlerde (kombi bakımı, klima, böcek ilaçlama…) zamanı gelince tek SMS ile hatırlatılsın mı
ilstringyesİl (ör. "Bursa")
ilcestring–İlçe (isteğe bağlı, ör. "Nilüfer")
kategoristringyesHizmet adı ya da kodu (ör. "Kombi Servisi"). Emin değilseniz önce kategoriler aracını kullanın.
kullanici_onayibooleanyesKullanıcı, bilgilerinin ustalarla paylaşılmasını ve SMS gönderilmesini açıkça onayladı mı (zorunlu: true)
teklif_toplaboolean–true: numara gizli kalır, ustalar yalnız fiyat teklifi verir. false (varsayılan): ustalar arayabilir.
telefonstringyesKullanıcının Türkiye cep telefonu (5XX XXX XX XX)
zamanstring–Ne zaman: acil=Acil (bugün), bu-hafta=Bu hafta, bu-ay=Bu ay içinde, esnek=Zaman esnek

No output schema declared.

No examples provided.

talep_onayla ~100

talep_olustur sonrası kullanıcının telefonuna gelen 6 haneli kodu doğrular ve talebi kaydeder. Talep kodu ve takip bağlantısı döner (takip bağlantısı ayrıca SMS ile gider).

NameTypeReqDescription
kodstringyesKullanıcının telefonuna gelen 6 haneli kod
talep_idstringyestalep_olustur yanıtındaki talep_id

No output schema declared.

No examples provided.

usta_ara ~229

Türkiye'de hizmet veren usta ve firmaları kategori, il, ilçe ve filtrelere göre arar. Sonuçlar puan, yorum sayısı, onay ve 'şu an ulaşılabilir' bilgisiyle döner. Telefon verilmez; kullanıcıyı sonucun url adresine yönlendirin.

NameTypeReqDescription
en_az_puannumber––
ilstring–İl adı veya slug (ör. "Bursa")
ilcestring–İlçe adı veya slug (ör. "Nilüfer"); il ile birlikte verin
kategoristring–Hizmet kategorisi adı veya slug (ör. "Elektrikçi", "kombi-servisi")
metinstring–Serbest arama (ör. "petek temizliği")
onayliboolean–Yalnızca ekibimizce onaylanmış hesaplar
sayfainteger––
su_an_acikboolean–Yalnızca şu an çalışma saatinde olanlar

No output schema declared.

No examples provided.

usta_detay ~63

Bir usta veya firmanın herkese açık profilini (hizmetler, tanıtım, puan, son yorumlar) getirir. slug, arama sonucundaki url adresinin son parçasıdır.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Usta-Bul MCP server?

Usta-Bul is a hosted endpoint at https://usta-bul.com/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 · usta-bul.com

# add to Claude Code
claude mcp add --transport http com-usta-bul-usta-bul 'https://usta-bul.com/mcp'
Common questions

What is the Usta-Bul MCP server?

Usta-Bul is an MCP server listed in the public MCP registry as com.usta-bul/usta-bul. Türkiye'de usta ve firma bulma: kategori, il ve ilçeye göre arama, profil, puan ve yorumlar. This page covers its hosted endpoint (https://usta-bul.com/mcp).

Is the Usta-Bul MCP server safe to use?

Usta-Bul scores 77 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 Usta-Bul MCP server expose?

Usta-Bul exposes 6 tools: usta_ara, usta_detay, kategoriler, konumlar, talep_olustur, talep_onayla. Their descriptions and schemas cost roughly 887 tokens of context every time the server is loaded.

Does the Usta-Bul MCP server require authentication?

No. We connected to Usta-Bul without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Usta-Bul MCP server still maintained?

Usta-Bul 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 Usta-Bul MCP server?

VerifyMCP ran 13 checks on Usta-Bul, 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.