Home / MCP registry index / org.gigngo/gigngo
GigNGo: US locals for home jobs and errands
org.gigngo/gigngo in the official MCP registry.
Endpoint https://gigngo.org/mcp.
The registry describes it as: Find a US local for a home job or errand, watch their filmed work, draft a post the person confirms
We read its 10 tools on 2026-10-21. 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
search_local_workers get_worker_profile get_work_record find_work_clips draft_job_post list_service_categories check_service_availability browse_open_tasks get_area_demand_density get_platform_info
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/org-gigngo-gigngo)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.