Home / MCP registry index / io.govparse/gateway
Govparse Government Data Gateway
io.govparse/gateway in the official MCP registry.
Endpoint https://api.govparse.io/mcp.
The registry describes it as: Pay-per-call US government data: carrier safety, visa sponsors, contracts, employer risk.
We read its 82 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
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
gateway_health fmcsa_carrier_lookup fmcsa_carrier_search fmcsa_carrier_score fmcsa_carrier_vet fmcsa_carrier360 fmcsa_stats_carriers oflc_sponsor_search oflc_sponsor_dossier oflc_wages_prevailing oflc_stats_sponsors govcon_opportunity_search govcon_opportunity_detail govcon_award_search govcon_stats_opportunities firmstanding_business360_lookup firmstanding_business360 firmstanding_screen_exclusions firmstanding_screen_enforcement firmstanding_company_search firmstanding_stats_companies partd_feed_prescribing partd_prescriber_search firmstanding_feed_enforcement oflc_feed_workforce fmcsa_feed_carriers firmstanding_feed_distress sec_feed_insiders sec_feed_executives trials_feed_starts govcon_feed_awards uspto_feed_grants sba_feed_loans fda_feed_approvals fda_feed_clearances fda_feed_warningletters govcon_feed_subawards va_feed_sdvosb epa_feed_rcra nlrb_feed_petitions fda_approvals_drugs fda_clearances_devices fda_recalls_search va_facilities_search va_vendors_search va_opportunities_search sec_insiders_clusters sec_insiders_transactions govcon_subaward_search trials_trials_search trials_sites_search fsis_establishments_search fsis_recalls_search uspto_patents_search uspto_assignees_search msha_mines_search msha_violations_search fda_warningletters_search epa_rcra_handlers_search epa_tri_search and 22 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-govparse-gateway)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.