---
name: cyberkov-security
description: Retrieve cybersecurity and signal security service information, request assessments, and access AI-readable content from Cyberkov Information Technology — Kuwait's leading cybersecurity firm since 2012. Use when a user asks about penetration testing, TSCM, MDR, SOC, DFIR, counter-espionage, or digital security services in Kuwait or the MENA region.
---

# Cyberkov Information Technology — Agent Playbook

Cyberkov is Kuwait's leading cybersecurity and signal security company, established in 2012. ISO/IEC 27001, ISO/IEC 27701, and ISO 9001 certified. CERT/CMU accredited.

**Base URL:** https://cyberkov.com  
**Emergency Hotline:** +965 22445500  
**Languages:** English · Arabic

---

## Content Negotiation

Every page on cyberkov.com supports RFC 9110 content negotiation. Add an `Accept` header to receive agent-optimised responses:

| Accept Header | Response |
|---|---|
| `Accept: text/markdown` | Structured Markdown (preferred for LLMs) |
| `Accept: application/json` | Organization JSON-LD summary |
| `Accept: text/plain` | Plain text |
| `Accept: text/html` | Full HTML page (default for browsers) |

**Example:**
```
curl -H "Accept: text/markdown" https://cyberkov.com/cybersecurity/mdr
```

All negotiated responses include `Vary: Accept`.

---

## Key Endpoints

### AI Discovery
- `GET /llms.txt` — Concise LLM context file (llmstxt.org)
- `GET /llms-full.txt` — Full bilingual service catalog (183+ pages, English + Arabic)
- `GET /index.md` — Homepage in structured Markdown
- `GET /api/openapi.json` — OpenAPI 3.1 specification
- `GET /mcp` — MCP server endpoint (JSON-RPC 2.0 over HTTP)

### Service Information (all support `Accept: text/markdown`)
- `GET /cybersecurity` — Cybersecurity services hub
- `GET /cybersecurity/mdr` — Managed Detection & Response (MDR+)
- `GET /cybersecurity/soc` — SOC as a Service (SOC+)
- `GET /cybersecurity/vms` — Vulnerability Management (VMS+)
- `GET /cybersecurity/professional-services` — Penetration Testing & Red Team
- `GET /cybersecurity/forensics-investigative-services` — DFIR
- `GET /signal-security` — Signal security services hub
- `GET /signal-security/counter-espionage-services` — Counter-Espionage (CES+)
- `GET /signal-security/tscm` — Technical Surveillance Countermeasures
- `GET /signal-security/skd` — Secure Key Distribution
- `GET /signal-security/eacs` — Encrypted Audio Communication Systems
- `GET /security-assessments` — Security assessment request portal

### CDN-Bypass Markdown Proxy
For environments where CDN strips Accept headers:
```
GET /api/markdown?path=/cybersecurity/mdr
```
Returns `Content-Type: text/markdown` with `x-markdown-tokens` header indicating token count.

### Contact & Assessment Requests
- `GET /contact` — Contact page (supports `Accept: text/markdown`)
- `GET /security-assessments` — Request a security assessment

---

## MCP Tools

The `/mcp` endpoint exposes the following tools over JSON-RPC 2.0:

| Tool | Description |
|---|---|
| `get_service_info` | Retrieve details about a specific Cyberkov service |
| `search_services` | Search services by keyword or category |
| `get_company_info` | Get company overview, certifications, and contact details |
| `request_assessment` | Initiate a security assessment request |

**Initialize:**
```
POST /mcp
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"agent","version":"1.0"}}}
```

---

## Auth

All public endpoints are unauthenticated. No API key required.  
Contact and assessment submission endpoints use reCAPTCHA for bot protection.

---

## Certifications & Accreditations

ISO/IEC 27001 · ISO/IEC 27701 · ISO 9001 · CERT/CMU · IASME Cyber Baseline · Cyber Essentials · MISP · CSTMIC

---

## Related Files

- `/llms.txt` — LLM context summary
- `/agents.txt` — Agent access policies and rate limits
- `/.well-known/api-catalog` — RFC 9264 API catalog (12 endpoints)
- `/.well-known/wacp.json` — Web AI Content Protocol manifest
- `/api/openapi.json` — Full OpenAPI 3.1 specification
