PubSec Radar MCP Server

by kabrawala Your server? Claim it

answering

PubSec Radar is answering right now. Last checked 12 min ago. It exposes 5 tools.

Federal sales intelligence: expiring-contract triggers, agency spend intel, deal qualification.

Uptime history 47 days of history · worst day 96%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

1165 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check PubSec Radar every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add pubsec-sales-mcp --transport http https://pubsec-sales-mcp.kabrawala.workers.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "pubsec-sales-mcp": {
      "url": "https://pubsec-sales-mcp.kabrawala.workers.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.pubsec-sales-mcp]
url = "https://pubsec-sales-mcp.kabrawala.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "pubsec-sales-mcp": {
      "url": "https://pubsec-sales-mcp.kabrawala.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "pubsec-sales-mcp": {
      "url": "https://pubsec-sales-mcp.kabrawala.workers.dev/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agency

agency_spend_profile

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 one fiscal year. Good queries name one agency, e.g. agency="HHS". Figures come from a daily snapshot of USAspending covering the current fiscal year plus a 3-year trend; freshness is stated in the response. Federal only. Read the coverage caveats — current-FY totals are partial-year and intel-agency spend is never published.

expiring

find_expiring_contracts

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 only (no state/local). Every response includes data-freshness and coverage caveats — read them; no data ≠ no spend.

generate

generate_discovery_questions

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. agency="DHS", product_category="zero-trust network security", meeting_context="first_call". Add naics_code to surface expiring-contract questions.

incumbent

incumbent_lookup

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 caveats for name-matching tips.

qualify

qualify_opportunity

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 dates at the agency get attached). Scores measure evidence specificity, not truth; the response says what verified evidence looks like for each dimension.

Endpoints

URL	Transport	State	Latency	Checked
https://pubsec-sales-mcp.kabrawala.workers.dev/mcp	streamable-http	answering	1307 ms	12 min ago

Alternatives to PubSec Radar

same job, measured the same way

FedTally — US Federal Contract Intelligence

by woodydaniel

US federal contract recompetes with the incumbent named, awards by company, agency spend.

3 tools answering

Fed-Spend

by fed-spend

Federal contract intelligence: $7T+ awards, SAM.gov opps, pWin verdicts, recompetes, protests.

answering

Saber

by saber-mcp

Sales intelligence — research companies, qualify prospects, and find contacts.

76 tools answering

Agentberg

by agentberg

Agent-to-agent trading intelligence exchange. Publish findings, vote on quality, earn reputation.

11 tools answering

Neurohive

by adelelo13

Multi-agent memory intelligence with expertise tracking and conflict detection

49 installs/wk local only

Zoom Revenue Accelerator

by zoom

Zoom Revenue Accelerator server for sales insights, conversations, and deal intelligence.

answering

Analytics Legends — SAP Analytics Intelligence

by analyticslegends

AI agent for SAP analytics: firms, day rates, contract radar, news, concepts, studies

20 tools answering

Agentic AI

by anthonywlicausi

Deal intelligence for agents: SEC-verified financials, validation, institutional deal scoring.

4 tools answering

PubSec Radar — questions

Answers built from our own checks of this server.

What can PubSec Radar do?

It exposes 5 tools, read directly from the server on our last check. Among them: agency_spend_profile, find_expiring_contracts, generate_discovery_questions, incumbent_lookup, qualify_opportunity. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is PubSec Radar working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1165 ms. The bar chart above shows every period we have measured.

How do I connect PubSec Radar?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does PubSec Radar need an API key?

No. PubSec Radar completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is PubSec Radar?

It answers our handshake in 1165 ms on average, which is faster than 5% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.