Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
Procureradar 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.
99/100
trust score
2
downloads a day
local
runs on your machine
34
downloads in 30d
What it does
ProcureRadar (Zhimao) AI skills exposed as Model Context Protocol tools — call buyer-discovery and intelligence skills directly from Cursor / Claude Desktop / Continue / any MCP-compatible AI host. Singapore (SGX) listed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user procureradar-mcp '--' npx -y procureradar-mcp-server
# 2 — ask your agent for something these tools do
# query_expansion, url_profile_extract, social_harvest_assisted and 6 more
Procureradar costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TCAll 2 servers
tonyback0101-cmyk2 servers
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. This one runs on your machine: your client starts Procureradar as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user procureradar-mcp '--' npx -y procureradar-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: 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 your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
9 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.
产业链裂变推理：输入品类（+可选国家），LLM 推理出该品类的下游买家画像（direct/indirect/adjacent 三档）+ Boolean 查询 + 扩展关键词。可直接喂给智猫数据抓取矩阵或其他搜索引擎。
No parameter schema on file.
URL → 结构化公司画像：粘贴企业官网 / LinkedIn 公司主页 / Alibaba 详情页等 URL，自动用 Bright Data 三层 fallback 抓取 + Mozilla Readability 抽正文 + LLM 抽结构化字段（company_name / country / industry / email / phone / linkedin / procurement_signals 等）。
No parameter schema on file.
Pillar 5 反爬终极方案：生成 Bookmarklet JS，用户在自己浏览器登录态下点书签即可抓取 FB / 小红书 / LinkedIn 评论区高意图买家（含 LLM 意图评分）。MCP 返回 bookmarklet_js 字符串，AI 助手指引用户保存到浏览器。
No parameter schema on file.
Facebook 小组批量成员采集：生成专门针对 FB Group 帖子区的 Bookmarklet，提取询价发帖人 + AI 评分高意图者送入 V8 富化流水线。
No parameter schema on file.
批量入种：用户粘贴一批公开 URL（FB 小组 / 公司主页 / LinkedIn），自动按 host 分流 social / company，校验+去重+入库，下一次智猫数据抓取矩阵跑时会消费。
No parameter schema on file.
公司综合情报（READ → FILL → SCORE → SYNTH）：对一家买家公司做工商 / 官网 / WHOIS / 税务 / 地图 / Logo / 舆情多源验证，输出 0-100 综合分 + verdict + risk_flags。
No parameter schema on file.
决策人挖掘综合：LinkedIn + 邮箱穿透 + WhatsApp 验证，输出 verified contacts + verdict。
No parameter schema on file.
买家意图综合：海关 + 供应链 + 区域 + 工商侧证；8 类信号派生 + effective_intent 分档（high/medium/low）+ recommended_action。
No parameter schema on file.
信号订阅：对买家 ID 订阅 hiring / news / tender 等行为信号变更，定时扫描后推送。
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Procureradar 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: —
ATrust score 99 / 100
Release 0.1.0 · scanned 15 Oct 2026
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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest5420dee41845880ba3ee31ca01876a3d495d5881dad68f8653df06b18c9ca631
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (9 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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 |
|---|---|---|
| query_expansion | no tags | |
| url_profile_extract | no tags | |
| social_harvest_assisted | no tags | |
| facebook_group_harvest | no tags | |
| seed_url_bulk_ingest | no tags | |
| company_intelligence | no tags | |
| decision_maker_intel | no tags | |
| buyer_intent_intelligence | no tags | |
| signal_watch | 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 digest5420dee41845880b
Scanned2026-10-15
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.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 Procureradar 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.