Home / MCP registry index / com.hillsignal/hillsignalapp
HillSignal
com.hillsignal/hillsignalapp in the official MCP registry.
Endpoint https://www.hillsignal.com/api/mcp.
The registry describes it as: Federal contracts, SAM notices, congressional trades, PAC money, insider trades, bills, EOs, themes.
We read its 27 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
resolve_entity get_entity search_awards award_totals search_opportunities get_opportunity congressional_trades get_politician insider_trades search_bills executive_orders pac_lookup pac_totals lobbying money_trail super_pacs outside_money data_coverage list_themes get_theme latest_events track_record institutional_holders foreign_agents foreign_agent_filings patents form_d_raises
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-hillsignal-hillsignalapp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.