# FedSignal — Federal Contract Exposure, USAspending to SEC Issuer Resolution (remote · insidermcp.34.73.153.244.sslip.io)

Federal government contracts and USAspending procurement exposure for SEC-listed companies.

- Trust score: 0/100 (low)
- Change this week: −61
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-08-29

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

## Components

- remote · `insidermcp.34.73.153.244.sslip.io`: 0/100 (this document), [markdown](https://verifymcp.io/servers/io-sslip-244-153-73-34-insidermcp-fedsignal-federal-contracts/mcp-federal-contracts.md), [page](https://verifymcp.io/servers/io-sslip-244-153-73-34-insidermcp-fedsignal-federal-contracts/mcp-federal-contracts)

## Channel facts

- Endpoint: `https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.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-29.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the FedSignal — Federal Contract Exposure, USAspending to SEC… MCP server?

FedSignal — Federal Contract Exposure, USAspending to SEC… is a hosted endpoint at https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-sslip-244-153-73-34-insidermcp-fedsignal-fede 'https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts'
```

### Cursor

```json
{
  "mcpServers": {
    "io-sslip-244-153-73-34-insidermcp-fedsignal-fede": {
      "url": "https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-sslip-244-153-73-34-insidermcp-fedsignal-fede": {
      "type": "http",
      "url": "https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-sslip-244-153-73-34-insidermcp-fedsignal-fede]
url = "https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-sslip-244-153-73-34-insidermcp-fedsignal-fede": {
      "type": "remote",
      "url": "https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-sslip-244-153-73-34-insidermcp-fedsignal-fede --url 'https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-sslip-244-153-73-34-insidermcp-fedsignal-fede:
    url: "https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts"
```

### Netclaw

```json
{
  "McpServers": {
    "io-sslip-244-153-73-34-insidermcp-fedsignal-fede": {
      "Transport": "http",
      "Url": "https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-sslip-244-153-73-34-insidermcp-fedsignal-fede -t streamable-http -u 'https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts'
```

### Other

```json
{
  "mcpServers": {
    "io-sslip-244-153-73-34-insidermcp-fedsignal-fede": {
      "type": "http",
      "url": "https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts"
    }
  }
}
```

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-29 (score 0, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-08-28 (score 12, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-08-27 (score 24, −13)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-08-26 (score 37, −12)

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

### 2026-08-25 (score 49, −12)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-08-23 (score 61, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.13 → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-08-22 (score 61, +1)

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

### 2026-08-20 (score 60, +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.

## MCP tools (8)

### `federal_revenue_exposure` (~268 tokens)

Federal contract obligations for one US-listed company over time, rolled up across every award recipient entity that belongs to it, including subsidiaries that file under completely different names. Use this for any question about a public company's government revenue, defense or agency exposure, or federal contract trend.

Why not query USAspending directly: award recipients and SEC issuers share no identifier, and large issuers receive most of their federal money under subsidiary names. Searching USAspending for 'Lockheed Martin' returns a small fraction of Lockheed's obligations because the majority arrive as 'Sikorsky Aircraft Corporation'. Searching for 'UnitedHealth' returns almost nothing because its federal book arrives as 'Optum Public Sector Solutions'. This tool resolves those roll-ups.

Returns per-quarter obligations, a trend measured against the mean of prior quarters, every attributed recipient entity with its match method and confidence, and awarding-agency concentration. Obligated amounts are agency obligations, not recognized revenue.

Input parameters:

- `min_confidence` (number): Minimum entity-match confidence. 0.9 admits only verified and exact-name matches; 0 includes inferred ones.
- `quarters` (integer): Number of quarterly windows to return.
- `ticker` (string, required): Stock ticker, e.g. LMT, GD, UNH, LDOS.

### `resolve_recipient` (~222 tokens)

Map a federal award recipient's legal name to the US-listed issuer that owns it, or state authoritatively that no listed parent exists. Use when you have a contractor name from a solicitation, award notice, or news story and need to know which public company it belongs to.

Returns the ticker, the match method, a confidence score, and a written explanation. Critically, it distinguishes 'no match found' from 'this affirmatively has no listed parent'. Recipients such as national laboratory operator consortia (Triad National Security, which runs Los Alamos), universities, companies taken private (ManTech, taken private by Carlyle in 2022), and US subsidiaries of foreign-listed parents (Marinette Marine, owned by Milan-listed Fincantieri) correctly resolve to no ticker. That is a real answer, not a gap, and it prevents attributing federal revenue to the wrong issuer.

Input parameters:

- `name` (string, required): Recipient legal name as it appears in federal award data, e.g. 'ELECTRIC BOAT CORPORATION'.

### `award_momentum` (~155 tokens)

Rank US-listed issuers by the change in their federal contract obligations between the two most recent comparable quarters. Use to find which public companies are gaining or losing federal business.

Ranked by issuer rather than by recipient name, which requires rolling subsidiary entities up to a ticker. USAspending can rank recipient names but cannot tell you that Electric Boat and General Dynamics Land Systems are the same investable company.

Large swings frequently reflect award timing rather than business trajectory, because a single multi-year obligation lands entirely in one quarter. Treat this as a list of things to investigate, not conclusions.

Input parameters:

- `limit` (integer)
- `min_confidence` (number)
- `min_usd` (number): Minimum obligations in either period.

### `contract_insider_overlap` (~223 tokens)

US-listed companies where insiders made open-market purchases in the same window the company was winning federal contract obligations. This requires both corpora at once: award data has no concept of an insider, and Form 4 data has no concept of a customer.

Officer, director, and 10-percent-holder purchases are reported as separate counts, because an outside fund accumulating is a materially different signal from an operating executive buying. Only open-market purchases (Form 4 code P) are counted; grants, option exercises, gifts, and tax-withholding dispositions are compensation mechanics and are excluded.

Co-occurrence only. An insider purchase during a period of award activity does not imply knowledge of those awards, and obligations are not revenue. If the result is empty, call index_coverage before concluding there is no activity: the insider index covers a limited number of filing days.

Input parameters:

- `days` (integer)
- `limit` (integer)
- `min_award` (number)
- `min_confidence` (number)
- `min_insider_buy` (number)

### `index_coverage` (~92 tokens)

Report exactly what the index covers: Form 4 date range and filing days ingested, transaction and issuer counts, award period range, number of issuers with attributed awards, and last refresh time.

Call this before treating a small or empty result as evidence of absence. Screening tools fail quietly, returning fewer rows rather than an error, so an agent that skips this step will misreport index depth as market fact.

### `screen_insider_buys` (~108 tokens)

Screen all indexed US public companies by net open-market insider buying and return the strongest names ranked. Supporting tool for when no ticker is known yet. Rule 10b5-1 planned trades are excluded by default because they were scheduled in advance and carry no information.

Input parameters:

- `days` (integer)
- `exclude_10b5_1` (boolean)
- `limit` (integer)
- `min_value` (number)
- `officers_only` (boolean)

### `cluster_buys` (~94 tokens)

Issuers where three or more distinct insiders bought on the open market inside the same window. Several independent insiders acting alike is the most informative pattern in the Form 4 dataset. Returns participant names and roles so the caller can judge whether operators or outside holders are responsible.

Input parameters:

- `days` (integer)
- `limit` (integer)
- `min_insiders` (integer)
- `min_value` (number)

### `filings_feed` (~112 tokens)

Normalized Form 4 transactions with USD values computed, insider role resolved, 10b5-1 status flagged, and a link to the original SEC filing so any figure can be verified at source. Filter by ticker, transaction code, or minimum value.

Input parameters:

- `code` (string): Form 4 code: P purchase, S sale, A grant, M exercise.
- `days` (integer)
- `limit` (integer)
- `min_value` (number)
- `ticker` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-sslip-244-153-73-34-insidermcp-fedsignal-federal-contracts/mcp-federal-contracts#diagnostics

## Score history

- 2026-08-29: 0
- 2026-08-28: 12
- 2026-08-27: 24
- 2026-08-26: 37
- 2026-08-25: 49
- 2026-08-24: 61
- 2026-08-23: 61
- 2026-08-22: 61
- 2026-08-21: 60
- 2026-08-20: 60
- 2026-08-19: 59
- 2026-08-18: 59

## Common questions

### What is the FedSignal — Federal Contract Exposure, USAspending to SEC… MCP server?

FedSignal — Federal Contract Exposure, USAspending to SEC… is an MCP server listed in the public MCP registry as io.sslip.244.153.73.34.insidermcp/fedsignal-federal-contrac…. Federal government contracts and USAspending procurement exposure for SEC-listed companies. This page covers its hosted endpoint (https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts).

### Is the FedSignal — Federal Contract Exposure, USAspending to SEC… MCP server safe to use?

FedSignal — Federal Contract Exposure, USAspending to SEC… scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the FedSignal — Federal Contract Exposure, USAspending to SEC… MCP server expose?

FedSignal — Federal Contract Exposure, USAspending to SEC… exposes 8 tools: federal_revenue_exposure, resolve_recipient, award_momentum, contract_insider_overlap, index_coverage, and 3 more. Their descriptions and schemas cost roughly 1,274 tokens of context every time the server is loaded.

### Does the FedSignal — Federal Contract Exposure, USAspending to SEC… MCP server require authentication?

Its publisher declares no required credentials for FedSignal — Federal Contract Exposure, USAspending to SEC…. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the FedSignal — Federal Contract Exposure, USAspending to SEC… MCP server still maintained?

FedSignal — Federal Contract Exposure, USAspending to SEC… has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 22 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://insidermcp.34.73.153.244.sslip.io/mcp/federal-contracts
- Website: https://insidermcp.34.73.153.244.sslip.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-sslip-244-153-73-34-insidermcp-fedsignal-federal-contracts/mcp-federal-contracts.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-sslip-244-153-73-34-insidermcp-fedsignal-federal-contracts/mcp-federal-contracts.json
- HTML version of this page: https://verifymcp.io/servers/io-sslip-244-153-73-34-insidermcp-fedsignal-federal-contracts/mcp-federal-contracts