World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Turkish public-tender (EKAP) award intelligence: firm histories, discounts, competition, red flags
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 10/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 22/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 ihalent。按照 https://mcp.popnx.com/i/gulmezeren2-byte-ihalent.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 3/3 项检查 · 在你的电脑上运行 · ✓ 命令已检查 2026年11月18日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
把这段话复制到 Claude 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude 安装 MCP server ihalent,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "ihalent": { "command": "uvx", "args": [ "ihalent" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 ihalent 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
SettingsDeveloperEdit Config
{
"mcpServers": {
"ihalent": {
"command": "uvx",
"args": [
"ihalent"
]
}
}
}用 ihalent 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 ihalent,或回答中出现 ihalent 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 ihalent
ihalent 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 ihalent 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
可连接 Claude Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Claude Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Claude Code 安装 MCP server ihalent,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):claude mcp add --scope user ihalent -- uvx ihalent 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 ihalent 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --scope user ihalent -- uvx ihalent应能看到 ihalent 在列表中并显示已连接
用 ihalent 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 ihalent,或回答中出现 ihalent 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 Cursor 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 Cursor 安装 MCP server ihalent,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "mcpServers": { "ihalent": { "command": "uvx", "args": [ "ihalent" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 ihalent 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 ihalent 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 ihalent,或回答中出现 ihalent 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要先在电脑上安装 Python (uv)(只需一次)
把这段话复制到 VS Code 的对话里。AI 会先检查电脑,告诉你要改哪个文件,并且每次都等你同意。
请在这台电脑上为 VS Code 安装 MCP server ihalent,按顺序:1) 用 uv --version 检查是否有 uv。没有的话,请让我从 https://docs.astral.sh/uv/getting-started/installation/ 安装,不要自己安装。2) 只使用这份配置(已通过 PopNx MCP 检查):{ "servers": { "ihalent": { "type": "stdio", "command": "uvx", "args": [ "ihalent" ] } } } 3) 告诉我要修改的文件完整路径或要运行的命令,等我同意。4) 不需要密钥。5) 按约定执行,然后确认 ihalent 的工具真的出现了。这段话不包含你的密钥。如果需要密钥,AI 会请你自己粘贴到文件或应用的输入框里。
已经装好了吗?先检查 · 打开终端,输入这条命令后按 Enter
uv --versionMac:按 ⌘ + Space,输入 Terminal 后按 Enter
Windows:打开“开始”菜单,输入 Windows PowerShell,然后选“打开”
还没安装: uv 没有点选式安装程序。从 uv 官方页面复制适合你系统(macOS 或 Windows)的一行命令,粘贴到终端 · 不需要单独安装 Python,uv 会在需要时自动下载
装好后关掉终端再打开,重新运行同一条命令,应显示版本号: uv --version
安装一次,所有需要 uv 的工具都能用
用 ihalent 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 ihalent,或回答中出现 ihalent 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add --scope user ihalent -- uvx ihalentClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"ihalent": {
"command": "uvx",
"args": [
"ihalent"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ihalent": {
"command": "uvx",
"args": [
"ihalent"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"ihalent": {
"type": "stdio",
"command": "uvx",
"args": [
"ihalent"
]
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 gulmezeren2-byte 验证,该账户拥有此仓库
代码最后更新于昨天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
尚未检查
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/gulmezeren2-byte-ihalent)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于昨天,最新版本(0.5.1)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| 本项 ihalent | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Turkish public-tender award intelligence: who won, for how much, at what discount, against how many bidders.
Reads the result notices KİK publishes in the daily Kamu İhale Bülteni, and anything you collected earlier with [saidsurucu/ihale-mcp](https://github.com/saidsurucu/ihale-mcp); ihalent structures and analyzes them.
Every public tender in Turkey ends with a *Sonuç İlanı* — a result notice that states the estimate, the contract price, the winner, and how many firms bid. The notices are public. They are also one at a time, unstructured, and impossible to reason across: you cannot ask EKAP "what has this company won in the last two years" or "how far below estimate does this authority actually award." ihalent turns those notices into structured records and answers exactly those questions — firm histories, discount (kırım) distributions, and competition metrics — with every number traceable back to the notice it came from.
That is real output over nine real construction awards from the December-2025 / January-2026 window (in examples/). The -2.96% at the bottom of the range is not a bug: Istanbul University awarded a 615-million-lira campus job at 2.96% above its own estimate, through an emergency "pazarlık" procedure — a contract signed over the public estimate, which is precisely the kind of thing that should be easy to see and currently is not.
I'm an industrial engineer and I work in construction. When our firm weighs a public tender, the questions that decide the bid are all about other people's history: how far below estimate does this authority award, how many firms usually show up, what has a given competitor been winning and at what price. All of that is public — it is sitting in tens of thousands of result notices on EKAP — and none of it is queryable. So everyone rebuilds a private, partial version of it by hand, in spreadsheets, badly.
The notices themselves are published in full every working day, in the Kamu İhale Bülteni. ihalent is the layer that turns that pile of notices into an answer: it reads the bulletin (or notices you collected earlier with saidsurucu/ihale-mcp), structures them, and does the analytics that don't exist yet.
A firm's history — every award across the dataset, folded across spelling variants:
$ ihalent firm examples/sample-awards.jsonl "ATAŞ MÜHENDİSLİK"
ATAŞ MÜHENDİSLİK HARİTA İMAR PLANLAMA İNŞAAT GIDA HAYVANCILIK SANAYİ VE TİCARET LİMİTED ŞİRKETİ wins: 1 joint ventures: 1 total contract value: 19.709.997,40 TL Discount (kırım) — ATAŞ MÜHENDİSLİK HARİTA İMAR PLANLAMA İNŞAAT GIDA HAYVANCILIK SANAYİ VE TİCARET LİMİTED ŞİRKETİ ┌────────┬────────┬────────┬────────┐ │ mean │ median │ min │ max │ ├────────┼────────┼────────┼────────┤ │ 33.87% │ 33.87% │ 33.87% │ 33.87% │ └────────┴────────┴────────┴────────┘ based on all 1 awards. top awarding authorities: 1x DSİ 14. Bölge Müdürlüğü
Where the discounts are — grouped and sorted, highest first:
$ ihalent discounts examples/sample-awards.jsonl --by authority
Mean discount by authority ┌──────────────────────────────────┬────────┬────────┬────────┐ │ authority │ mean │ median │ awards │ ├──────────────────────────────────┼────────┼────────┼────────┤ │ DSİ 14. Bölge Müdürlüğü │ 33.87% │ 33.87% │ 1/1 │ │ Ziraat Bankası Genel Müdürlüğü │ 31.41% │ 31.41% │ 1/1 │ │ İstanbul YİKOB │ 26.98% │ 26.98% │ 1/1 │ │ İSKİ Genel Müdürlüğü │ 26.66% │ 26.66% │ 1/1 │ │ İTÜ Rektörlüğü │ 22.68% │ 22.68% │ 1/1 │ │ Esenler Belediyesi │ 21.99% │ 21.99% │ 1/1 │ │ Ağrı İl Özel İdaresi │ 19.99% │ 19.99% │ 1/1 │ │ Kağıthane Belediyesi │ 17.41% │ 17.41% │ 1/1 │ │ İstanbul Üniversitesi-Cerrahpaşa │ -2.96% │ -2.96% │ 1/1 │ └──────────────────────────────────┴────────┴────────┴────────┘ awards column: used / considered (excluded lack an estimate, or were awarded in lots).
Competition — how many valid bids show up, and how often exactly one does (a single-bid award is a flag procurement watchdogs care about). It's in the overview above.
A number is never shown without the ground it stands on. A mean discount always comes with "over how many awards, and how many were dropped for a missing estimate." A firm's total contract value says so when some of its wins had no published price, so you read it as a floor, not the full figure. A discount is None, never 0, when the estimate wasn't published — ihalent does not invent the numbers the government didn't print. Half the value of a tool like this is refusing to guess.
pip install ihalent # the core
pip install "ihalent[bulletin]" # + reading the Kamu İhale Bülteni PDFs pip install "ihalent[mcp]" # + the MCP server
Or from source: pip install git+https://github.com/gulmezeren2-byte/ihalent.
ihalent reads a JSONL file of awards. The way to produce one is the Kamu İhale Bülteni: KİK prints every result notice in a daily bulletin (Law 4734, Art. 47), one file per tender type, on EKAP's public bulletin page. ihalent downloads those files and reads them:
# 1. collect: today's works (yapım) bulletin, or every working day since a date
ihalent fetch-bulletin --out bulletins ihalent fetch-bulletin --out bulletins --since 2026-11-01
ihalent ingest-bulletin bulletins -o awards.jsonl
ihalent overview awards.jsonl ihalent firm awards.jsonl "ACME İNŞAAT" ihalent discounts awards.jsonl --by authority --min 5
ingest-bulletin checks every file against the bulletin's own table of contents and says how many notices it read, rejected, or could not find; it exits 1 if those don't add up. A notice whose labels and values don't pair up is rejected, never guessed.
Every working day, by itself. ihalent daily FOLDER (0.5.0 and later; it needs the bulletin extra) does both steps for every tender type: it fetches what the folder is missing from the last seven days, so a week the computer was off is filled in, and rebuilds FOLDER/awards.jsonl. Each file is read once and its read is kept beside it in .ihalent-reads/, so the run stays quick as the folder grows. Let the computer's scheduler run it after the day's bulletin is out:
# Windows (PowerShell): every weekday at 19:00, or as soon as the computer is on after that
$ihalent = (Get-Command ihalent).Source $run = New-ScheduledTaskAction -Execute $ihalent -Argument "daily "$HOME\ekap"" $when = New-ScheduledTaskTrigger -Weekly -DaysOfWeek Monday,Tuesday,Wednesday,Thursday,Friday -At 19:00 $opts = New-ScheduledTaskSettingsSet -StartWhenAvailable -AllowStartIfOnBatteries -DontStopIfGoingOnBatteries Register-ScheduledTask -TaskName ihalent-daily -Action $run -Trigger $when -Settings $opts
crontab -e (command -v ihalent prints the full path)0 19 * * 1-5 /full/path/to/ihalent daily "$HOME/ekap"
A public holiday just shows as a day with no bulletin; a whole week without one exits 1, because that is also how a changed page would look. If the page ever asks for human verification or refuses, daily stops and leaves ihalent-stopped.txt in the folder; later runs don't contact the page until you delete that file.
Lots. A tender awarded in parts (kısmi teklif) gets one notice per lot, and the lots come out on different days, each printing the tender-wide estimate. ihalent merges them by İKN and sums the contracts, but gives such a tender no discount (lots_unverified): no bulletin says when the last lot has been printed, so comparing the estimate with the lots seen so far would invent a number. Each lot's winner and price are kept (lots), so a firm is credited only the lots it won.
What the bulletin does not carry: a province field. --by province stays empty for bulletin data; ihalent does not infer it. Amounts in another currency: some goods notices price the contract in euros or dollars against a lira estimate. That contract's lira price is left empty, with no exchange rate guessed, so it gets no discount; an estimate printed in lira with its foreign original beside it is read in lira. What was verified: the works and goods bulletins of 12 and 13 November 2026 and the service and consultancy bulletins of the 13th — 883 of 883 notices read, each file matching its table of contents. All were fetched with fetch-bulletin: through the archive form (the two goods days in one --since run) and, for the works bulletin of the 13th, through the day's own button. A notice that says it has no estimate ("- TRY", or a sentence saying so) is read with the estimate left empty.
The older path, via ihale-mcp. Since September 2026 EKAP's search API asks for human verification, so collecting with ihale-mcp from your own machine fails with HTTP 428. ihalent does not try to get past that check. If you still have notices collected that way, ihalent ingest bundle.json reads them.
Every command takes --json for pipelines and agents. Or skip collection and try the bundled example directly:
git clone https://github.com/gulmezeren2-byte/ihalent && cd ihalent
python examples/build_sample.py # parses the real notices in examples/notices/ ihalent overview examples/sample-awards.jsonl
| command | what it does |
|---|---|
ihalent overview AWARDS | value, discount, competition and the data gaps of a dataset |
ihalent firm AWARDS "NAME" | one company's wins, total value, discount, and where it wins |
ihalent discounts AWARDS --by X | mean/median discount grouped by authority, province or tender_type |
ihalent single-bid AWARDS | awards with a single valid bid — no real competition (a watchdog flag) |
ihalent concentration AWARDS [--authority X] | winner concentration (HHI) — do the same few firms win everything? |
ihalent flags AWARDS | per-award red flags: single bid, near-estimate price, no estimate, high drop-off |
ihalent fetch-bulletin --out DIR | download Kamu İhale Bülteni files from EKAP's public bulletin page |
ihalent ingest-bulletin DIR | bulletin result notices → awards JSONL, checked against the table of contents |
ihalent daily DIR | the last week's bulletins of every type → DIR, then DIR/awards.jsonl; for a scheduler |
ihalent parse NOTICE.md | one result notice → structured JSON |
ihalent ingest BUNDLE.json | collected ihale-mcp/EKAP output → awards JSONL |
The result notice is unstructured text; the interesting questions are aggregate. That is an awkward fit for an agent working notice-by-notice, and a natural fit for a tool: --json output with stable fields, an exit code that means something, and a firm-name match that folds spelling variants so an agent doesn't have to.
There is a native MCP server (pip install 'ihalent[mcp]') that exposes the analytics as tools — `over