io.github.ufhouck/chirak-mcp
NPM · CHIRAK-MCP · SCANNED SEP 20
Model Context Protocol (MCP) Server for Chirak Sales & Inventory Assistant
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1377 tokens (~91/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.ufhouck/chirak-mcp server?
io.github.ufhouck/chirak-mcp runs locally as an npm package, launched with npx -y chirak-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · chirak-mcp
claude mcp add ufhouck-chirak-mcp -- npx -y chirak-mcp
{
"mcpServers": {
"ufhouck-chirak-mcp": {
"command": "npx",
"args": [
"-y",
"chirak-mcp"
]
}
}
} {
"servers": {
"ufhouck-chirak-mcp": {
"command": "npx",
"args": [
"-y",
"chirak-mcp"
]
}
}
} codex mcp add ufhouck-chirak-mcp -- npx -y chirak-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ufhouck-chirak-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"chirak-mcp"
],
"enabled": true
}
}
} openclaw mcp add ufhouck-chirak-mcp --command npx --arg -y --arg chirak-mcp
mcp_servers:
ufhouck-chirak-mcp:
command: "npx"
args: ["-y", "chirak-mcp"] {
"McpServers": {
"ufhouck-chirak-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"chirak-mcp"
]
}
}
} assistant mcp add ufhouck-chirak-mcp -t stdio -c npx -a -y chirak-mcp
{
"mcpServers": {
"ufhouck-chirak-mcp": {
"command": "npx",
"args": [
"-y",
"chirak-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 10 Sept 26 56
First indexed and scored.
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 20 Sept 2026 · Analysed npm/chirak-mcp@1.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_customer ~128
Add a new customer to the Chirak store contacts directory.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Customer delivery / billing address. |
| channel | string | – | Primary channel: 'WhatsApp', 'Instagram', 'Mağaza / Telefon', 'Telegram', 'TikTok', 'Diğer'. |
| string | – | Customer email address. | |
| name | string | yes | Customer full name (required). |
| notes | string | – | VIP notes or customer preferences. |
| phone | string | – | Customer phone number. |
| socialHandle | string | – | Social media username (e.g. '@selin'). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
add_product ~243
Add a new product to Chirak inventory. Use this when the user asks to add items, parse wholesale invoices, or register products.
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | string | – | EAN-13, QR, or other barcode string. |
| category | string | – | Product category name (e.g. 'General', 'Giyim', 'Kahve'). |
| costPrice | number | – | Purchase or wholesale cost price (optional, default: 0). |
| currency | string | – | ISO currency code (e.g. 'TRY', 'USD', 'EUR'). |
| minimumStock | number | – | Low stock alert threshold (default: 5). |
| name | string | yes | Full product title/name (required). |
| sellingPrice | number | yes | Retail selling price for the product (e.g. 150.0). |
| sku | string | – | Stock Keeping Unit code (e.g. 'GMLK-01'). |
| stockQuantity | number | – | Initial physical stock quantity (default: 0). |
| unit | string | – | Unit type: 'Adet', 'Kg', 'Gram', 'Kutu', 'Çift', 'Libre', 'Ons'. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
adjust_stock ~120
Adjust physical stock quantity for a product (+/- change) with an audit reason (e.g. 'purchase', 'damage', 'adjustment', 'return'). Automatically records a stock movement.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Product UUID (required). |
| note | string | – | Optional audit note for the stock adjustment. |
| quantityChange | number | yes | Quantity change (e.g. +10 to add stock, -3 for damaged goods). |
| reason | string | – | Reason: 'purchase', 'sale', 'adjustment', 'damage', 'return'. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
cancel_sale ~40
Cancel a sale order and automatically restore the ordered item quantities back into the physical store inventory.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Sale order UUID to cancel (required). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
delete_customer ~31
Delete a customer from the Chirak store directory.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Customer UUID to delete (required). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
delete_product ~35
Permanently delete or remove a product from the Chirak inventory catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Product UUID to delete (required). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
get_chirak_help ~84
Returns a complete operational guide to Chirak store capabilities, operational cheat-sheet, active store context, and example AI prompt patterns. Call this whenever the user or agent needs help, guidance, or wants to explore store features.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional specific topic to focus on: 'products', 'sales', 'customers', 'reports', or 'general'. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
get_inventory ~103
Fetch current inventory products from Chirak, with options to filter by category or find critical low stock items.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category name to filter products (e.g. 'Coffee', 'Clothing', 'General'). |
| limit | number | – | Maximum number of products to return (default: 50, max: 100). |
| low_stock_only | boolean | – | If true, only returns products whose stock quantity is at or below the minimum threshold. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
get_sales_report ~46
Retrieve a summary report of revenue, total sales orders, units sold, and low-stock alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Time range for the sales report (default: 'today'). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
help ~52
Quick operational guide and cheat-sheet for Chirak store capabilities, active metrics, and recommended prompts.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Optional specific topic: 'products', 'sales', 'customers', 'reports', or 'general'. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
list_customers ~53
Retrieve customer contact directory and their lifetime spending metrics from Chirak.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max customers to return (default: 50). |
| search | string | – | Search customer by name, phone or email. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
record_sale ~141
Record a sale order and automatically deduct the corresponding product stocks in Chirak.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Sale channel: 'WhatsApp', 'Instagram', 'Fiziki Mağaza', 'Web Sitesi', 'Telefon Siparişi', 'Diğer'. |
| customerName | string | – | Customer full name (optional). |
| customerPhone | string | – | Customer phone number (optional). |
| items | array | yes | List of items in the order. |
| notes | string | – | Order notes or special delivery instructions. |
| paymentStatus | string | – | Payment status: 'Ödendi', 'Ödenmedi', 'Kısmi Ödeme'. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
search_product ~41
Search for products in Chirak by name, SKU code, or barcode.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The search query (product name, barcode, or SKU). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
update_customer ~104
Update contact details, delivery address, or notes of an existing customer in Chirak.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Updated address. |
| channel | string | – | Updated channel. |
| string | – | Updated email address. | |
| id | string | yes | Customer UUID (required). |
| name | string | – | Updated full name. |
| notes | string | – | Updated notes. |
| phone | string | – | Updated phone number. |
| socialHandle | string | – | Updated social handle. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
update_product ~156
Update details of an existing product in Chirak, such as selling price, cost, physical stock quantity, name, category, SKU, or barcode.
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | string | – | Updated barcode string. |
| category | string | – | Updated category name. |
| costPrice | number | – | Updated wholesale cost price. |
| id | string | yes | Product UUID (required). |
| minimumStock | number | – | Updated minimum stock threshold. |
| name | string | – | Updated product name. |
| sellingPrice | number | – | Updated retail selling price. |
| sku | string | – | Updated SKU code. |
| stockQuantity | number | – | Updated stock quantity. |
| unit | string | – | Updated unit type (e.g. 'Adet', 'Kg'). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Result data payload from Chirak API. |
| success | boolean | – | Status of the tool execution. |
No examples provided.
What is the io.github.ufhouck/chirak-mcp server?
io.github.ufhouck/chirak-mcp is listed in the public MCP registry as io.github.ufhouck/chirak-mcp. Model Context Protocol (MCP) Server for Chirak Sales & Inventory Assistant. This page covers its npm package (chirak-mcp).
Is the io.github.ufhouck/chirak-mcp server safe to use?
io.github.ufhouck/chirak-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.ufhouck/chirak-mcp server expose?
io.github.ufhouck/chirak-mcp exposes 15 tools: get_chirak_help, help, get_inventory, search_product, add_product, and 10 more. Their descriptions and schemas cost roughly 1,377 tokens of context every time the server is loaded.
Is the io.github.ufhouck/chirak-mcp server still maintained?
io.github.ufhouck/chirak-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.ufhouck/chirak-mcp server under?
io.github.ufhouck/chirak-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.