Home / MCP registry index / io.github.OmniAISystems/govomniai-machine-services
GovOmniAI Machine Services
io.github.OmniAISystems/govomniai-machine-services in the official MCP registry.
Endpoint https://ucljocpnvirclrhhiicr.supabase.co/functions/v1/govomniai-mcp. Source: github.com/OmniAISystems/govomniai-web.
The registry describes it as: AI-to-AI: free risk previews; optional $0.50 MPP receipts; $5 Cropper federal checks.
We read its 7 tools on 2026-10-29. 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.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http govomniai-machine-services https://ucljocpnvirclrhhiicr.supabase.co/functions/v1/govomniai-mcp{
"mcpServers": {
"govomniai-machine-services": {
"url": "https://ucljocpnvirclrhhiicr.supabase.co/functions/v1/govomniai-mcp"
}
}
}code --add-mcp '{"name":"govomniai-machine-services","type":"http","url":"https://ucljocpnvirclrhhiicr.supabase.co/functions/v1/govomniai-mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.
Tools it advertises
list_machine_services assess_autonomous_transaction_risk_free qualify_federal_opportunity_free create_agent_action_assurance_order create_agent_action_assurance_order_1usd create_agent_offer_verification_order_3usd create_federal_opportunity_qualification_order_5usd
Run this server? Show the check in your README
The badge reflects the latest weekly read:
[](https://lazaretto.dev/mcp-registry/io-github-omniaisystems-govomniai-machine-services)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.