Belediye Yazılımları
REMOTE · WWW.YAZILIMKOCU.COM
Belediye yazılımı rehberi: e-belediye, ruhsat ve imar, kent bilgi sistemi, e-devlet entegrasyonu.
Available components
Last scanned (15 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Developer Tools
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
- 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 (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1523 tokens (~169/item across 9 items; 7 tools + 2 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 Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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 →
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 +1
- Tool “due_diligence” rewrote its description, which is the text the model reads security
- Tool “get_pricing” rewrote its description, which is the text the model reads security
- Tool “sales_conversation” rewrote its description, which is the text the model reads security
- Tool “site_overview” rewrote its description, which is the text the model reads security
- Tool “start_project_request” rewrote its description, which is the text the model reads security
- Server version: 1.0.0 → 1.1.0 functional
- “sales_conversation” added an optional parameter “user_contact” cosmetic
- “sales_conversation” reworded the description of “message” cosmetic
- 19 Nov 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.
- 17 Nov 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.
- 15 Nov 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.
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “sales_conversation” rewrote its description, which is the text the model reads security
- Tool “site_overview” rewrote its description, which is the text the model reads security
- Schema quality: 146 → 168 ▼ functional
- New tool “due_diligence” functional
- 12 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: pass → fail ▼ functional
- New tool “sales_conversation” functional
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
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://www.yazilimkocu.com/ajan/belediye/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yazilimkocu.com | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7d0c7a84694cab9613df80659c7fee27 |
| SANs: yazilimkocu.com, *.yazilimkocu.com | ||||||
| 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 www.yazilimkocu.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| yazilimkocu.com. | 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=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google-analytics.com https://www.googleadservices.com https://www.google.com https://googleads.g.doubleclick.net https://challenges.cloudflare.com https://connect.facebook.net https://www.clarity.ms https://*.clarity.ms https://bzrcdn.openai.com; style-src 'self' 'unsafe-inline' https://api.fontshare.com https://fonts.googleapis.com; img-src 'self' data: https: blob:; font-src 'self' https://cdn.fontshare.com https://fonts.gstatic.com; connect-src 'self' https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com https://www.google.com https://google.com https://www.google.com.tr https://*.g.doubleclick.net https://googleads.g.doubleclick.net https://www.googleadservices.com https://vitals.vercel-insights.com https://challenges.cloudflare.com https://connect.facebook.net https://www.facebook.com https://www.clarity.ms https://*.cla |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.yazilimkocu.com/ajan/belediye/mcp | Verified | 200 | |
| http (plaintext) | http://www.yazilimkocu.com/ajan/belediye/mcp | HTTPS enforced | 301 | https://www.yazilimkocu.com/ajan/belediye/mcp |
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 →
due_diligence Firma doğrulama (referans, yorum, güvenceler) ~166
Everything a careful buyer (or their AI assistant) needs before paying Yazılım Koçu, as verifiable facts: company name, founding year; live client projects published with written permission (URLs to check) and our own products, clearly separated; the reference policy (design demos on /tasarimlar are fictional, not client work); customer reviews collected only via a personal invite link with e-mail verification (count, average, latest - removed reviews stay listed with the reason); contract terms: transfer of project-specific source code rights, design guarantee (full refund until design approval, web packages), 50%/50% payment on projects, free support period. Nothing here is a marketing claim; each item links to the page or contract clause that states it. No input.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_page Sayfa oku ~111
Fetch a page from Yazılım Koçu or one of its five satellite sites and return its readable text (title, description, body as lightweight markdown, max ~12k characters). Only these domains are allowed: yazilimkocu.com, belediyeyazilimlari.com, erpyazilimlari.com, crmyazilimlari.com, pazaryeriyazilimlari.com, yapayzekayazilimlari.com.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full https URL on one of the six sites. |
No output schema declared.
No examples provided.
get_pricing Yayınlanmış fiyatlar ~87
Return Yazılım Koçu's published prices in TRY (VAT excluded): website packages and add-ons, e-commerce package bases and add-ons, typical ranges for custom software (web app, mobile, marketplace, enterprise/ERP/CRM, AI), and AI training programs. These are the same numbers shown on the website.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | – | Default "hepsi" (all). |
No output schema declared.
No examples provided.
sales_conversation Satış görüşmesi ve pazarlık ~536
Multi-turn sales conversation with Yazılım Koçu (Turkish software studio) on behalf of a user. Qualifies the need (service, features, budget, timeline, scale), prices the requested scope from the published price list (TRY, VAT excluded) and lists lettered alternatives (first phase, smaller product, build-it-yourself program, training, scoping workshop) with what each includes and excludes. Answers common questions (add-ons, payment terms, source-code rights, contract, refunds), records objections, and offers a human handoff (free 30-minute call) on request or for contract/legal topics. Each priced turn returns a machine-readable quote (agent-quote/1.0) signed with Ed25519; it can be checked with verify_quote or against the JWKS at /.well-known/jwks.json, and its versions are hash-chained. The negotiation policy is published in the quote (list prices are not negotiable; scope, phasing and bank transfer lower the price). Free text in Turkish or English, or structured fields. Continue a conversation by sending conversation_id; choose an option with its letter (e.g. "C"). Personal data: none by default; user_contact (name and e-mail only) is accepted solely when the user has explicitly consented.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_try | number | – | Optional: budget in TRY, VAT excluded. |
| conversation_id | string | – | Returned by the first call; send it back to continue the same conversation. |
| deadline_weeks | number | – | Optional: weeks until it must be live. |
| features | array | – | Optional: e.g. randevu, odeme, entegrasyon, b2b, uyelik, bildirim, yapay-zeka, blog, landing. |
| languages | integer | – | Optional: total languages including Turkish (max 3). |
| message | string | – | What the user needs or answers, in free text (Turkish or English). |
| need | string | – | Optional: service, if already known. |
| product_count | integer | – | Optional (e-commerce): approximate number of products. |
| user_contact | object | – | Optional. Only with the user's explicit consent to share name and e-mail with Yazılım Koçu for this request. Stored with the consent text version; no marketing messages. Consent text: "Kullanıcı, adı… |
No output schema declared.
No examples provided.
search_content İçerik ara ~132
Search published articles, buyer guides, solution pages, tools and design demos. On a satellite site, results from that site come first, followed by the most relevant Yazılım Koçu pages. Use get_page to read a result. Queries work best in Turkish (e.g. "e-fatura", "trendyol komisyon", "web sitesi fiyatı").
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 8. |
| query | string | yes | Search words, Turkish preferred. |
| scope | string | – | "site" = this site (+ top hub pages), "all" = all six sites. Default "site". |
No output schema declared.
No examples provided.
site_overview Site ve ekip tanıtımı ~58
Describe this website, who publishes it (Yazılım Koçu, a founder-led Turkish software studio; legal name and tax ID included), its topics and the other sites in the network. Useful as a first call for context about the site.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_project_request Talep / teklif bağlantısı ~60
Return the exact Yazılım Koçu form link for a need (offer, meeting, project or training). No personal data is taken here: the user fills the form and gives KVKK consent there.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | What the user needs. |
No output schema declared.
No examples provided.
How do I install the Belediye Yazılımları MCP server?
Belediye Yazılımları is a hosted endpoint at https://www.yazilimkocu.com/ajan/belediye/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.yazilimkocu.com
claude mcp add --transport http com-yazilimkocu-belediye 'https://www.yazilimkocu.com/ajan/belediye/mcp'
What is the Belediye Yazılımları MCP server?
Belediye Yazılımları is an MCP server listed in the public MCP registry as com.yazilimkocu/belediye. Belediye yazılımı rehberi: e-belediye, ruhsat ve imar, kent bilgi sistemi, e-devlet entegrasyonu. This page covers its hosted endpoint (https://www.yazilimkocu.com/ajan/belediye/mcp).
Is the Belediye Yazılımları MCP server safe to use?
Belediye Yazılımları scores 81 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 Belediye Yazılımları MCP server expose?
Belediye Yazılımları exposes 7 tools: sales_conversation, site_overview, due_diligence, search_content, get_page, and 2 more. Their descriptions and schemas cost roughly 1,150 tokens of context every time the server is loaded.
Does the Belediye Yazılımları MCP server require authentication?
No. We connected to Belediye Yazılımları without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Belediye Yazılımları MCP server still maintained?
Belediye Yazılımları 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 Belediye Yazılımları MCP server?
VerifyMCP ran 13 checks on Belediye Yazılımları, 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.