Model Context Protocol (MCP) server for Apollo.io API integration
Nothing to run from here
PubSec 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.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Federal sales intelligence: expiring-contract triggers, agency spend intel, deal qualification.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pubsec-radar-mcp https://pubsec-sales-mcp.kabrawala.workers.dev/mcp
# 2 — ask your agent for something these tools do
# find_expiring_contracts, agency_spend_profile, incumbent_lookup and 2 more
PubSec 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
KAAll 1 server
Kabrawala1 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 pubsec-radar-mcp https://pubsec-sales-mcp.kabrawala.workers.dev/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
5 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.
Use this when prospecting or prepping a federal account and you want sales triggers: contracts at an agency that end soon, with the incumbent vendor, dollar values, and contracting office. Expiring contracts mean upcoming recompetes — the best time to displace an incumbent. Good queries name one agency and optionally a NAICS code, e.g. agency="DHS", naics_code="541512", window_days=90. Federal onl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agency | string | yes | Federal agency name, acronym, or code — e.g. "DHS", "Department of Defense", "070". Federal only; SLED is out of scope. |
| naics_code | string | no | Optional NAICS code to narrow by category, e.g. "541512" (computer systems design). |
| window_days | integer | no | How far ahead to look for contract end dates, in days from today. Default 90, max 365. |
| limit | integer | no | Max contracts to return (top by obligated amount). Default 15. |
Use this to answer "what does this agency actually buy, and from whom?" before a first call: total contract obligations, 3-year trend, top 10 vendors, and top 10 NAICS categories for the latest fiscal year with published data. Good queries name one agency, e.g. agency="HHS". Figures come from a daily snapshot of USAspending (latest published fiscal year plus a 3-year trend); the fiscal year and fr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agency | string | yes | Federal agency name, acronym, or code — e.g. "HHS", "Department of Veterans Affairs", "075". |
Use this to answer "who am I displacing and when?": a vendor name (plus optional agency scope) returns their current and recent awards with values and end dates, flagging awards that end within 12 months as displacement windows. Good queries use the vendor's registered name or a distinctive fragment, e.g. vendor="Booz Allen", agency="DHS". Federal only. Zero results ≠ no presence — check the cavea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendor | string | yes | Vendor/incumbent name as registered in federal awards, e.g. "Booz Allen Hamilton", "CACI". FPDS matches it as a phrase — shorter fragments match more. |
| agency | string | no | Optional federal agency to scope the lookup, e.g. "DHS". Omit to search government-wide. |
| limit | integer | no | Max awards to return (largest first). Default 15. |
Use this when prepping a meeting with a federal agency: it returns discovery questions tuned to public-sector selling (fiscal-year timing, contract vehicles, FedRAMP/ATO, incumbents), grounded in the agency's live spending data where possible — each data-backed question cites the number that motivated it with a source URL. Good queries name the agency, what you sell, and the meeting type, e.g. age
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agency | string | yes | Federal agency the meeting is with — name, acronym, or code, e.g. "DHS". |
| product_category | string | yes | What you sell, in plain words — e.g. "data analytics platform", "zero-trust network security". |
| naics_code | string | no | Optional NAICS code for your category — adds questions about specific expiring contracts. |
| meeting_context | string | no | What kind of meeting you are prepping for. |
Use this to pressure-test a federal deal: pass what you know per MEDDPICC dimension (leave unknowns empty) and get back an evidence-scored scorecard adapted for public sector — budget authority instead of generic economic buyer, procurement vehicle as the paper process — with gap-closing questions and public-record evidence pulled automatically (name the incumbent_vendor and their real awards/end
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agency | string | yes | Federal agency the deal is at — name, acronym, or code, e.g. "DHS". |
| product_category | string | yes | What you are selling, e.g. "SIEM platform". |
| estimated_value_usd | number | no | Rough deal size in USD, if known. |
| incumbent_vendor | string | no | Competitor/incumbent vendor name if known — their real awards at this agency get pulled as evidence. |
| deal_facts | object | no | What you know so far, one field per MEDDPICC dimension. Omit entirely (or leave fields empty) for pure-discovery scoring — gaps are the output. |
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 PubSec 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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 0.1.0.
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 PubSec 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.