# CRM Yazılımları (remote · www.yazilimkocu.com)

CRM rehberi: satış hattı, WhatsApp ve e-ticaret entegrasyonu, hazır CRM ile özel geliştirme kararı.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.yazilimkocu.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-yazilimkocu-crm/ajan-crm-mcp.md), [page](https://verifymcp.io/servers/com-yazilimkocu-crm/ajan-crm-mcp)

## Channel facts

- Endpoint: `https://www.yazilimkocu.com/ajan/crm/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1518 tokens (~168/item across 9 items; 7 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the CRM Yazılımları MCP server?

CRM Yazılımları is a hosted endpoint at https://www.yazilimkocu.com/ajan/crm/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.

### Claude

```bash
claude mcp add --transport http com-yazilimkocu-crm 'https://www.yazilimkocu.com/ajan/crm/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-yazilimkocu-crm": {
      "url": "https://www.yazilimkocu.com/ajan/crm/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-yazilimkocu-crm": {
      "type": "http",
      "url": "https://www.yazilimkocu.com/ajan/crm/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-yazilimkocu-crm]
url = "https://www.yazilimkocu.com/ajan/crm/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-yazilimkocu-crm": {
      "type": "remote",
      "url": "https://www.yazilimkocu.com/ajan/crm/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-yazilimkocu-crm --url 'https://www.yazilimkocu.com/ajan/crm/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-yazilimkocu-crm:
    url: "https://www.yazilimkocu.com/ajan/crm/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-yazilimkocu-crm": {
      "Transport": "http",
      "Url": "https://www.yazilimkocu.com/ajan/crm/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-yazilimkocu-crm -t streamable-http -u 'https://www.yazilimkocu.com/ajan/crm/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-yazilimkocu-crm": {
      "type": "http",
      "url": "https://www.yazilimkocu.com/ajan/crm/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 81, +1)

- [security] 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
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “sales_conversation” added an optional parameter “user_contact”
- [cosmetic] “sales_conversation” reworded the description of “message”

### 2026-11-19 (score 80, +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.

### 2026-11-17 (score 79, +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.

### 2026-11-15 (score 78, +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.

### 2026-11-13 (score 77, 0)

- [security] 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
- [functional regression] Schema quality: 145 → 168
- [functional] New tool “due_diligence”

### 2026-11-12 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional] New tool “sales_conversation”

### 2026-11-10 (score 77, +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.

### 2026-11-08 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (7)

### `sales_conversation` (~536 tokens)

Satış görüşmesi ve pazarlık

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.

Input parameters:

- `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ı…

### `site_overview` (~58 tokens)

Site ve ekip tanıtımı

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.

### `due_diligence` (~166 tokens)

Firma doğrulama (referans, yorum, güvenceler)

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.

### `search_content` (~132 tokens)

İçerik ara

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ı").

Input parameters:

- `limit` (integer): Default 8.
- `query` (string, required): Search words, Turkish preferred.
- `scope` (string): "site" = this site (+ top hub pages), "all" = all six sites. Default "site".

### `get_page` (~111 tokens)

Sayfa oku

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.

Input parameters:

- `url` (string, required): Full https URL on one of the six sites.

### `get_pricing` (~87 tokens)

Yayınlanmış fiyatlar

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.

Input parameters:

- `service` (string): Default "hepsi" (all).

### `start_project_request` (~60 tokens)

Talep / teklif bağlantısı

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.

Input parameters:

- `need` (string, required): What the user needs.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-yazilimkocu-crm/ajan-crm-mcp#diagnostics

## Score history

- 2026-11-21: 81
- 2026-11-20: 80
- 2026-11-19: 80
- 2026-11-18: 79
- 2026-11-17: 79
- 2026-11-16: 78
- 2026-11-15: 78
- 2026-11-14: 77
- 2026-11-13: 77
- 2026-11-12: 77
- 2026-11-11: 77
- 2026-11-10: 77
- 2026-11-09: 76
- 2026-11-08: 76
- 2026-11-07: 75

## Common questions

### What is the CRM Yazılımları MCP server?

CRM Yazılımları is an MCP server listed in the public MCP registry as com.yazilimkocu/crm. CRM rehberi: satış hattı, WhatsApp ve e-ticaret entegrasyonu, hazır CRM ile özel geliştirme kararı. This page covers its hosted endpoint (https://www.yazilimkocu.com/ajan/crm/mcp).

### Is the CRM Yazılımları MCP server safe to use?

CRM 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 CRM Yazılımları MCP server expose?

CRM 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 CRM Yazılımları MCP server require authentication?

No. We connected to CRM Yazılımları without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CRM Yazılımları MCP server still maintained?

CRM 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 CRM Yazılımları MCP server?

VerifyMCP ran 13 checks on CRM 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.

## Links

- Remote endpoint: https://www.yazilimkocu.com/ajan/crm/mcp
- Website: https://www.crmyazilimlari.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-yazilimkocu-crm/ajan-crm-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-yazilimkocu-crm/ajan-crm-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-yazilimkocu-crm/ajan-crm-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-yazilimkocu-crm/ajan-crm-mcp
