Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
AI project radar is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Taiwan Government Procurement Bidding Documents - Read-Only Search: Amount Increments, Bidding Period Calculation, Bidding Knowledge Base, Bidding Announcements, Suppliers and Agencies. Free and Registration-Free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ai-project-radar-mcp https://tenderrader.com/mcp
# 2 — ask your agent for something these tools do
# get_procurement_thresholds, calc_tender_deadline, search_guides and 5 more
AI project radar costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TEAll 1 server
tenderrader1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ai-project-radar-mcp https://tenderrader.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
回傳現行政府採購金額級距（112 年 1 月 1 日起）：中央機關小額採購 15 萬元以下、公告金額 150 萬元、查核金額與巨額採購（依工程／財物／勞務不同），含法規出處與常見舊資料提醒。
No parameter schema on file.
依招標期限標準計算：採購金額落在哪個級距、法定最短等標期幾日，以及（給公告日時）最早可截止投標日。支援招標期限標準第 2～6、9、11 條，含電子領標／投標等縮短情形。算的是法定下限，機關可訂得更長。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount_twd | number | yes | 採購金額（新臺幣元），用預算金額或預估採購總額 |
| kind | string | yes | works＝工程、goods＝財物、service＝勞務（查核金額與巨額門檻三者不同） |
| method | string | yes | open＝公開招標、selective＝選擇性招標（資格預先審查）、evaluate＝公開評選之限制性招標、solicit＝公開徵求之限制性招標、quote＝公開取得書面報價或企劃書、restricted＝未經公開評選／公開徵求之限制性招標 |
| second_solicit | boolean | no | 僅 method=solicit：是否為第二次以後的公開徵求（第一次 10 日以上；第二次以後不得少於 5 日） |
| shorten | object | no | 招標期限標準第 9 條可縮短的情形：public_viewing 公開閱覽（−5 日，不得少於 10 日）、e_doc 電子領標（−3 日，不得少於 5 日）、e_bid 電子投標（−2 日，不得少於 5 日） |
| publish_date | string | no | 公告日（選填）。填了才會算最早可截止投標日；公告當日算入第 1 日 |
用問題或關鍵字檢索 AI標案雷達的投標知識庫（47 篇制度與實務說明）與免費工具，回傳「一句話答案」、法規出處與頁面網址。適合回答「開口契約是什麼」「押標金什麼情況沒收」這類制度問題。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | 要查的問題或關鍵字，例如「開口契約是什麼」「勞務採購金額級距」「押標金沒收」 |
| limit | integer | no | 最多回傳幾筆（預設 5） |
搜尋本站索引中近期（最多 30 天）的政府招標公告，可依關鍵字、機關所在地、採購類別、狀態篩選，最多 10 筆。逐日讀取（每天最多 1,500 筆），不是全部歷史；招標公告只從 2026/06 起收錄。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | no | 標案名稱／機關名稱關鍵字，多個詞用空白分開（全部都要出現） |
| region | string | no | 機關所在地（依機關名稱判定，其餘一律歸「中央機關」；不是履約地點） |
| category | string | no | 採購類別文字，例如「工程類」「財物類」「勞務類」或更細的類別名稱片段 |
| status | string | no | announced＝只有招標公告、索引裡尚無決標或無法決標紀錄（預設；不保證仍在截止日前）；awarded＝已決標；failed＝無法決標；any＝全部 |
| days | integer | no | 只看最近幾天公告的案子（1～30，預設 14） |
| limit | integer | no | 最多回傳幾筆（1～10，預設 5） |
用機關代碼與案號查單一標案：標題、機關、公告日、類型、預算、狀態，以及（有本輪決標公告時）決標金額與得標廠商。只讀本站資料，不即時查政府網站。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| unit_id | string | yes | 機關代碼（例如 A.9.6M） |
| job_number | string | yes | 標案案號（例如 J115041） |
用統一編號（或公司名稱開頭）查廠商：投標件數（下限）、得標件數、期間、主要往來機關、商工登記基本資料。不提供得標率、電話、負責人或地址。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tax_id | string | no | 統一編號（8 碼） |
| name | string | no | 公司名稱開頭（前綴比對，至少 2 個字）。與 tax_id 擇一 |
用機關代碼（或名稱關鍵字）查機關：收錄的招標公告與決標件數、常用公告類型、主要得標廠商、近 12 個月每月收錄件數、近期標案。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| unit_id | string | no | 機關代碼 |
| name | string | no | 機關名稱關鍵字（至少 2 個字）。與 unit_id 擇一 |
回傳本站用自己資料算好的統計快照：招標預算級距、流標廢標之後同案是否再決標、標的分類分布；附母體定義與統計日期。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | budget-bands＝招標預算級距；failed-tender＝流標廢標之後；category-mix＝標的分類。省略則列出可用主題 |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AI project radar or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest7d934fccadb27ed0563084817d1cbe07d69790c1f24c5f991d8d82bbaed8d9dd
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_procurement_thresholds | no tags | |
| calc_tender_deadline | no tags | |
| search_guides | no tags | |
| search_tenders | no tags | |
| get_tender | no tags | |
| lookup_vendor | no tags | |
| lookup_agency | no tags | |
| get_market_stats | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7d934fccadb27ed0
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish AI project radar can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.