# PubSec Radar (remote · pubsec-sales-mcp.kabrawala.workers.dev)

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

- Trust score: 60/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `pubsec-sales-mcp.kabrawala.workers.dev`: 60/100 (this document), [markdown](https://verifymcp.io/servers/kabrawala-pubsec-sales-mcp/pubsec-sales-mcp.md), [page](https://verifymcp.io/servers/kabrawala-pubsec-sales-mcp/pubsec-sales-mcp)

## Channel facts

- Endpoint: `https://pubsec-sales-mcp.kabrawala.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1059 tokens (~211/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kabrawala-pubsec-sales-mcp": {
      "type": "remote",
      "url": "https://pubsec-sales-mcp.kabrawala.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kabrawala-pubsec-sales-mcp --url https://pubsec-sales-mcp.kabrawala.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kabrawala-pubsec-sales-mcp:
    url: "https://pubsec-sales-mcp.kabrawala.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "kabrawala-pubsec-sales-mcp": {
      "type": "http",
      "url": "https://pubsec-sales-mcp.kabrawala.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 59, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (5)

### `find_expiring_contracts` (~244 tokens)

Find expiring federal 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.

Input parameters:

- `agency` (string, required): Federal agency name, acronym, or code — e.g. "DHS", "Department of Defense", "070". Federal only; SLED is out of scope.
- `limit` (integer): Max contracts to return (top by obligated amount). Default 15.
- `naics_code` (string): Optional NAICS code to narrow by category, e.g. "541512" (computer systems design).
- `window_days` (integer): How far ahead to look for contract end dates, in days from today. Default 90, max 365.

### `agency_spend_profile` (~156 tokens)

Profile a federal agency's contract spending

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.

Input parameters:

- `agency` (string, required): Federal agency name, acronym, or code — e.g. "HHS", "Department of Veterans Affairs", "075".

### `incumbent_lookup` (~194 tokens)

Look up an incumbent vendor's federal contracts

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.

Input parameters:

- `agency` (string): Optional federal agency to scope the lookup, e.g. "DHS". Omit to search government-wide.
- `limit` (integer): Max awards to return (largest first). Default 15.
- `vendor` (string, required): Vendor/incumbent name as registered in federal awards, e.g. "Booz Allen Hamilton", "CACI". FPDS matches it as a phrase — shorter fragments match more.

### `generate_discovery_questions` (~220 tokens)

Generate public-sector 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.

Input parameters:

- `agency` (string, required): Federal agency the meeting is with — name, acronym, or code, e.g. "DHS".
- `meeting_context` (string): What kind of meeting you are prepping for.
- `naics_code` (string): Optional NAICS code for your category — adds questions about specific expiring contracts.
- `product_category` (string, required): What you sell, in plain words — e.g. "data analytics platform", "zero-trust network security".

### `qualify_opportunity` (~245 tokens)

Qualify a federal opportunity (public-sector MEDDPICC)

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.

Input parameters:

- `agency` (string, required): Federal agency the deal is at — name, acronym, or code, e.g. "DHS".
- `deal_facts` (object): What you know so far, one field per MEDDPICC dimension. Omit entirely (or leave fields empty) for pure-discovery scoring — gaps are the output.
- `estimated_value_usd` (number): Rough deal size in USD, if known.
- `incumbent_vendor` (string): Competitor/incumbent vendor name if known — their real awards at this agency get pulled as evidence.
- `product_category` (string, required): What you are selling, e.g. "SIEM platform".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kabrawala-pubsec-sales-mcp/pubsec-sales-mcp#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 60
- 2026-08-01: 59
- 2026-07-31: 59
- 2026-07-30: 60
- 2026-07-29: 60
- 2026-07-28: 59
- 2026-07-27: 58
- 2026-07-26: 58

## Links

- Remote endpoint: https://pubsec-sales-mcp.kabrawala.workers.dev/mcp
- Website: https://pubsec-sales-mcp.kabrawala.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/kabrawala-pubsec-sales-mcp/pubsec-sales-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/kabrawala-pubsec-sales-mcp/pubsec-sales-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/kabrawala-pubsec-sales-mcp/pubsec-sales-mcp