ihalent MCP server
Turkish public-tender (EKAP) award intelligence: firm histories, discounts, competition, red flags
3 stars
Reviews
Write oneNobody has reviewed ihalent yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
ihalent tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- Code scan12 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 52 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How ihalent compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- GitHub stars
- 3
- more than 80% of 28,688 servers
Install ihalent in Claude Code, Cursor or VS Code
claude mcp add ihalent -- uvx ihalent
What the publisher says
From the ihalent repository's README, as published. We do not edit it. Read it on GitHub
ihalent
Turkish public-tender award intelligence: who won, for how much, at what discount, against how many bidders.
Built on top of saidsurucu/ihale-mcp — ihale-mcp reaches EKAP; ihalent structures and analyzes what it returns.
<!-- mcp-name: io.github.gulmezeren2-byte/ihalent -->
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.
Why this exists
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.
There is already an excellent tool for reaching this data: saidsurucu/ihale-mcp solved authenticated EKAP access and hands you the notices. ihalent is the layer above it — the one that turns a pile of notices into an answer. It does not re-scrape EKAP; it structures what you have collected and does the analytics that don't exist yet.
What it answers
A firm's history — every award across the dataset, folded across spelling variants:
$ ihalent firm examples/sample-awards.jsonl "ÖZDEN YEL"
ÖZDEN YEL
wins: 1 joint ventures: 1 total contract value: 19.709.997,40 TL
Discount (kırım) — ÖZDEN YEL
┌────────┬────────┬────────┬────────┐
│ 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:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
ihalent: common questions
- Is ihalent MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the ihalent safety report
- How do I install ihalent?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does ihalent need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is ihalent maintained?
- The last commit was 92 days ago (2026-08-04). The latest release is v0.3.0.
- How does ihalent compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers). Full comparison.