# HillSignal (remote · www.hillsignal.com)

Federal contracts, SAM notices, congressional trades, PAC money, insider trades, bills, EOs, themes.

- Trust score: 83/100 (high trust)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-30

## Components

- remote · `www.hillsignal.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-hillsignal-hillsignalapp/api-mcp.md), [page](https://verifymcp.io/servers/com-hillsignal-hillsignalapp/api-mcp)

## Channel facts

- Endpoint: `https://www.hillsignal.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-09-30.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3864 tokens (~161/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the HillSignal MCP server?

HillSignal is a hosted endpoint at https://www.hillsignal.com/api/mcp, 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 com-hillsignal-hillsignalapp 'https://www.hillsignal.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hillsignal-hillsignalapp": {
      "url": "https://www.hillsignal.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hillsignal-hillsignalapp": {
      "type": "http",
      "url": "https://www.hillsignal.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hillsignal-hillsignalapp]
url = "https://www.hillsignal.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hillsignal-hillsignalapp": {
      "type": "remote",
      "url": "https://www.hillsignal.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hillsignal-hillsignalapp --url 'https://www.hillsignal.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hillsignal-hillsignalapp:
    url: "https://www.hillsignal.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hillsignal-hillsignalapp": {
      "Transport": "http",
      "Url": "https://www.hillsignal.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hillsignal-hillsignalapp -t streamable-http -u 'https://www.hillsignal.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-hillsignal-hillsignalapp": {
      "type": "http",
      "url": "https://www.hillsignal.com/api/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-09-29 (score 83, +1)

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

### 2026-09-28 (score 82, +7)

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

### 2026-09-26 (score 75, +1)

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

### 2026-09-25 (score 74, 0)

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

### 2026-09-24 (score 74, +1)

- [security] Tool “foreign_agents” rewrote its description, which is the text the model reads

### 2026-09-23 (score 73, 0)

- [security] Tool “foreign_agents” rewrote its description, which is the text the model reads

### 2026-09-21 (score 73, +1)

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

### 2026-09-20 (score 72, 0)

- [security] Tool “foreign_agents” rewrote its description, which is the text the model reads

## MCP tools (24)

### `resolve_entity` (~80 tokens)

Resolve a company name to a ticker

Map an organization name (a contract recipient, a subsidiary, a PAC sponsor, a Form D issuer) to its public-company ticker. Exact normalized match against SEC legal names, aliases and the Exhibit 21 subsidiary map; returns the method and a confidence, or the reason for a miss. Never guesses.

Input parameters:

- `name` (string, required): Organization name as written

### `get_entity` (~104 tokens)

Company profile

One company in the federal record: contracts won, PACs, patents, private raises, members of Congress who hold board seats there, insider trades, and its connections graph. Look up by ticker, entity_id, or a name (resolved exactly).

Input parameters:

- `entity_id` (string): HillSignal entity id (hs:entity:...)
- `name` (string): Company name; resolved by exact match
- `ticker` (string): Stock ticker, e.g. LMT

### `search_awards` (~237 tokens)

Federal contract awards

Search federal contract awards (USAspending, $10M+) by recipient, ticker, awarding agency, keyword, date range or minimum amount. Returns total_matching and pages with offset (up to 50 per call), sorted by date or amount. For "who won the most" questions use award_totals instead, which counts every match.

Input parameters:

- `agency` (string): Awarding agency or sub-agency (partial), e.g. "Navy"
- `keyword` (string): Word in the award description or NAICS description
- `limit` (number): Max rows, 1-50 (default 25)
- `min_amount` (number): Minimum award amount in USD
- `offset` (number): Row offset for paging (default 0)
- `recipient` (string): Recipient or parent name (partial)
- `since` (string): ISO date (YYYY-MM-DD); only rows on or after this date
- `sort` (string): date (default) | amount
- `ticker` (string): Resolved ticker
- `until` (string): ISO date; only rows on or before this date

### `award_totals` (~217 tokens)

Award totals by recipient, ticker or agency

Aggregate every matching federal award (same filters as search_awards) into totals per recipient, per resolved ticker, or per awarding agency: award count, total dollars, share, first and last award, largest award. Use this for "who won the most from the Navy this year" and similar questions; it counts all matches, not a page.

Input parameters:

- `agency` (string): Awarding agency or sub-agency (partial)
- `group_by` (string): recipient (default) | ticker | agency
- `keyword` (string): Word in the award description
- `limit` (number): Top groups to return, 1-50 (default 25)
- `min_amount` (number): Minimum award amount in USD
- `recipient` (string): Recipient or parent name (partial)
- `since` (string): ISO date (YYYY-MM-DD); only rows on or after this date
- `ticker` (string): Resolved ticker
- `until` (string): ISO date; only rows on or before this date

### `search_opportunities` (~155 tokens)

What the government is about to buy

Search SAM.gov notices: Sources Sought and Pre-solicitations (the earliest public signal of a purchase), solicitations and combined synopses. Filter by keyword, NAICS, agency, notice type, date.

Input parameters:

- `agency` (string): Department or organization (partial)
- `keyword` (string): Word in the notice title
- `limit` (number): Max rows, 1-25 (default 10)
- `naics` (string): NAICS code or prefix, e.g. 3364
- `notice_type` (string): sources_sought | presolicitation | solicitation | combined
- `since` (string): ISO date (YYYY-MM-DD); only rows on or after this date

### `congressional_trades` (~166 tokens)

Congressional stock trades

Stock trades disclosed by members of Congress (House and Senate Periodic Transaction Reports), by member name, ticker, transaction type or date. Returns one row per transaction with the disclosed amount range and the filing PDF. limit caps the FILINGS read, not the trades returned, and filings_matching is how many exist: when truncated is set, far more trades exist than are shown and returned_trades must never be quoted as a total.

Input parameters:

- `limit` (number): Max rows, 1-25 (default 10)
- `politician` (string): Member name (partial)
- `since` (string): ISO date (YYYY-MM-DD); only rows on or after this date
- `ticker` (string): Ticker traded
- `transaction_type` (string): purchase | sale

### `get_politician` (~91 tokens)

Member of Congress profile

A member of Congress: committees, board seats and other positions from annual Financial Disclosures (with resolved tickers), recent stock trades, and top PAC contributors from FEC data. Look up by name or bioguide_id; ambiguous names return candidates.

Input parameters:

- `bioguide_id` (string): Bioguide id, e.g. P000197
- `name` (string): Member name

### `insider_trades` (~113 tokens)

Insider trades (Form 4)

SEC Form 4 insider transactions by ticker or insider name; filter to buys or sells, minimum value, date.

Input parameters:

- `insider` (string): Insider name (partial)
- `limit` (number): Max rows, 1-25 (default 10)
- `min_value` (number): Minimum total value USD
- `since` (string): ISO date (YYYY-MM-DD); only rows on or after this date
- `ticker` (string): Ticker
- `type` (string): buy | sell

### `search_bills` (~148 tokens)

Bills and government events

Full-text search over bills, contract awards and other government events with their analysed sector and ticker exposure. Filter by bill number, ticker, sector, date or event type.

Input parameters:

- `bill_number` (string): e.g. HR1234 or S567
- `event_type` (string): Comma-separated event types
- `limit` (number): Max rows, 1-25 (default 10)
- `query` (string): Search words
- `sector` (string): Sector label, e.g. Defense
- `since` (string): ISO date (YYYY-MM-DD); only rows on or after this date
- `ticker` (string): Ticker named in the analysis

### `executive_orders` (~84 tokens)

Executive orders and presidential actions

Executive orders, proclamations and memoranda with affected sectors and tickers.

Input parameters:

- `limit` (number): Max rows, 1-25 (default 10)
- `query` (string): Words in the title or summary
- `sector` (string): Sector label
- `since` (string): ISO date (YYYY-MM-DD); only rows on or after this date

### `pac_lookup` (~122 tokens)

A company's PAC and who it funds

Corporate and trade-association PACs linked to a public company (by ticker) or found by committee name, with the candidates they fund. Answers "does Lockheed have a PAC and who does it give to", "which politicians take money from Pfizer's PAC". For super PACs and mega-donors use super_pacs and money_trail instead.

Input parameters:

- `committee_name` (string): PAC or sponsor name (partial)
- `limit` (number): Max rows, 1-25 (default 10)
- `ticker` (string): Issuer ticker

### `pac_totals` (~163 tokens)

Biggest PAC donors

Which PACs give the most: contributors to tracked candidates ranked by total dollars (FEC Schedule A), by election cycle, with donor-processing conduits like ActBlue and WinRed separated out. mode=disbursers ranks committees by their own reported disbursements instead. Use for "which PACs donate the most to Congress" questions; for super PACs use super_pacs.

Input parameters:

- `cycle` (number): Two-year election cycle, e.g. 2026 or 2024; omit for all
- `limit` (number): Top rows, 1-50 (default 10)
- `mode` (string): contributors (default) | disbursers
- `query` (string): Filter contributor or committee name (partial)

### `lobbying` (~203 tokens)

What a company asks Washington for

Senate LDA lobbying disclosures: what a company spent lobbying, which firms it hired, which issues it worked, which agencies it contacted, which bills it named, and how many of its lobbyists previously held government posts. Or pass bill= for everyone who lobbied a given bill. This is the intent layer — super PAC money says who a company is FOR, lobbying says what it WANTS. Answers "what is Coinbase lobbying on", "who lobbied HR1234", "which agencies does Lockheed contact".

Input parameters:

- `bill` (string): Bill number, e.g. HR1234 or S.567 — returns everyone who lobbied it
- `company` (string): Company name; resolved by exact match
- `limit` (number): Max rows, 1-50 (default 20)
- `since_year` (number): Only filings from this year onward
- `ticker` (string): Issuer ticker, e.g. COIN

### `money_trail` (~248 tokens)

Follow one donor's money

How much a person or organization gave, through which entities, to which committees, and what those committees did with it. Answers "how much did Elon Musk give to Trump", "who did Timothy Mellon fund", "where did Uline's money go". Returns donor_identity (the resolved person or organization, every employer spelling folded into one, with lifetime totals), given_via (the LLCs, trusts and partnerships the cheques were actually written under — how the money reached the committee), the recipient committees, and each super PAC's independent spending for and against candidates. Names go in as written ("Elon Musk"); the FEC form ("MUSK, ELON") is handled. Ambiguous names return matched_as; narrow with employer.

Input parameters:

- `cycle` (number): Two-year election cycle, e.g. 2024 or 2026; omit for current and previous
- `employer` (string): Narrow to receipts whose employer field contains this (e.g. "Tesla")
- `limit` (number): Max recipient committees, 1-25 (default 10)
- `name` (string, required): Donor: a person ("Ken Griffin") or organization ("Uline")

### `super_pacs` (~373 tokens)

Super PACs: the biggest, and who is behind one

Which super PACs are pulling the strings: the largest by money raised, spent or on hand for a cycle, from the FEC's own committee totals. With query or committee_id, one committee's profile: its top donors, what it spent for and against which candidates, and the vendors it paid for campaign work. With shared_vendors, the media buyers and consultancies working for more than one committee. With public_companies, listed companies ranked by the political money they give, resolved to tickers. A committee profile also names the public companies behind its money. Answers "biggest super PACs this cycle", "who funds MAGA Inc", "what is America PAC spending on", "which firms work for both sides", "which public companies give the most".

Input parameters:

- `committee_id` (string): FEC committee id, e.g. C00879510
- `cycle` (number): Two-year election cycle (default: current)
- `limit` (number): Max rows, 1-25 (default 10)
- `min_committees` (number): With shared_vendors: minimum committees sharing a vendor (default 2)
- `public_companies` (boolean): Return publicly traded companies ranked by political money given, resolved to tickers
- `query` (string): Committee name (partial), e.g. "America PAC"
- `shared_vendors` (boolean): Return vendors paid by two or more committees instead of a committee ranking
- `sort` (string): receipts (default) | independent_expenditures | disbursements | cash_on_hand
- `ticker` (string): With public_companies: one issuer, e.g. COIN
- `types` (string): "all" to include every PAC type; default super PACs and hybrids only

### `outside_money` (~138 tokens)

Who is spending for or against a candidate

Outside money on a candidate: every super PAC and other filer spending independently to support or oppose them, with totals, from FEC Schedule E. Answers "who is backing Trump", "which groups are attacking this senator", "how much outside money is in the Ohio Senate race". Candidate names go in as written.

Input parameters:

- `candidate` (string, required): Candidate name, e.g. "Donald Trump", "Ossoff"
- `cycle` (number): Two-year election cycle, e.g. 2024 or 2026; omit for all
- `limit` (number): Max committees per side, 1-50 (default 15)

### `data_coverage` (~49 tokens)

What HillSignal has

Row counts and the latest dated row for every dataset behind these tools, plus entity-resolution coverage. Call it when an answer depends on how complete the data is, or before saying something does not exist.

### `list_themes` (~35 tokens)

Government themes

The themes the government is currently funding across bills, contracts, solicitations and filings, each with a permanent page and a verdict.

### `get_theme` (~63 tokens)

Theme chronology

One theme in full: the setup, the dated chronology with each beat linked to its source record, why it matters, what to watch, and the evidence.

Input parameters:

- `theme_id` (string, required): Theme id from list_themes (with or without hs:theme: prefix)

### `latest_events` (~110 tokens)

Latest events (firehose)

The newest events across every source (awards, trades, filings, bills, orders, themes), with provenance. Optional filters by category, ticker or source id.

Input parameters:

- `categories` (string): Comma-separated categories, e.g. contract,trade,filing
- `limit` (number): Max events, 1-25 (default 20)
- `sources` (string): Comma-separated source ids from /api/wire
- `tickers` (string): Comma-separated tickers

### `track_record` (~38 tokens)

HillSignal forward track record

Every forward call HillSignal made since May 2025, verified against SPY 30 days later, with the inclusion rules and the miss rate.

### `institutional_holders` (~60 tokens)

Institutional holders (13F)

Largest institutional holders of a ticker from 13F-HR filings HillSignal has ingested, latest position per institution.

Input parameters:

- `limit` (number): Max rows, 1-25 (default 10)
- `ticker` (string, required): Ticker

### `foreign_agents` (~497 tokens)

Who works for a foreign government, and for how much

Who is paid to represent a foreign government or party inside the United States, and HOW MUCH, from the Justice Department's FARA register and the contracts filed with it. Pass top="contracts" for the biggest deals — the largest contract prices, who pays whom, and who owns the client in the filer's own sworn words. Pass country= to LIST THAT COUNTRY'S AGENTS BY NAME: registered_agents is the full current roster, each with its foreign principal, registration number and dates, plus former_agents and the counts. Answer "how many agents does Israel have and who are they" from that roster. Pass bill= for the foreign interests that lobbied a bill, or nothing for the country leaderboard. A country response also carries also_in_lobbying_data, the minority of those agents that additionally file under the Lobbying Disclosure Act, split into DIRECT, where the lobbying client IS the foreign principal and bills are named, and SHARED_FIRM, where one firm holds a foreign registration and separate domestic clients — context, never a claim about those clients. That subset is never the roster. Countries are spelled as the register spells them. A country roster also carries the MONEY per agent: agreed_price is the contract price from the agreement exhibit filed at registration, always with the rate it is stated at, and reported_receipts is what the agent later reported actually receiving, as a floor rather than earnings. Both are null where no figure could be proved. Each agent may also carry foreign_principal_owned_by — the filer's sworn words on who owns the foreign principal, which is how a US-registered company names its foreign parent.

Input parameters:

- `bill` (string): Bill number, e.g. HR1234 — returns foreign principals that lobbied it
- `country` (string): Country as the register spells it, e.g. "ISRAEL", "SAUDI ARABIA", "KOREA, SOUTH"
- `limit` (number): Max rows, 1-100 (default 20)
- `rate` (string): With top=contracts: the rate to rank, "month" (default) or "year", "quarter", "hour", "one-time". Rates are never mixed or converted.
- `top` (string): Pass "contracts" to rank the BIGGEST foreign-agent contract prices on file — who is paid the most, by whom. Combine with country= to narrow it.

### `form_d_raises` (~140 tokens)

Private raises (Form D)

SEC Form D private placements by issuer name, resolved ticker, date or minimum amount. No minimum size is applied: pass min_amount to impose one. A null offering_amount means the filer stated no offering size, which Form D permits, and is not a raise of zero.

Input parameters:

- `limit` (number): Max rows, 1-25 (default 10)
- `min_amount` (number): Minimum offering amount USD
- `query` (string): Issuer name (partial)
- `since` (string): ISO date (YYYY-MM-DD); only rows on or after this date
- `ticker` (string): Resolved public parent ticker

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hillsignal-hillsignalapp/api-mcp#diagnostics

## Score history

- 2026-09-30: 83
- 2026-09-29: 83
- 2026-09-28: 82
- 2026-09-27: 75
- 2026-09-26: 75
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 73
- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 67
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 65

## Common questions

### What is the HillSignal MCP server?

HillSignal is an MCP server listed in the public MCP registry as com.hillsignal/hillsignalapp. Federal contracts, SAM notices, congressional trades, PAC money, insider trades, bills, EOs, themes. This page covers its hosted endpoint (https://www.hillsignal.com/api/mcp).

### Is the HillSignal MCP server safe to use?

HillSignal scores 83 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 HillSignal MCP server expose?

HillSignal exposes 24 tools: resolve_entity, get_entity, search_awards, award_totals, search_opportunities, and 19 more. Their descriptions and schemas cost roughly 3,634 tokens of context every time the server is loaded.

### Does the HillSignal MCP server require authentication?

No. We connected to HillSignal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the HillSignal MCP server still maintained?

HillSignal is still listed as active in the MCP registry. We last reached this channel on 30 September 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://www.hillsignal.com/api/mcp
- Website: https://www.hillsignal.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-hillsignal-hillsignalapp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hillsignal-hillsignalapp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hillsignal-hillsignalapp/api-mcp