GigNGo Local Services Marketplace MCP server

• browse_open_tasksFree

  Browse open jobs homeowners have posted on GigNGo that locals can apply to. Each task includes title, description, `details` (the poster's Additional Details note, present on most jobs and usually the most specific part), category, budget, approximate location (coordinates are privacy-offset), when it was posted (postedAt, ageHours, ageDays, postedAgo), how many locals have applied (applicantCount, hasApplicants) and how fast the first one did (hoursToFirstApplicant), plus a link to apply. Filter by category, state, city, age or applicant count, and sort by newest, oldest, most_applicants or fewest_applicants. All filters are optional — call with no arguments for the most recent open tasks nationwide.

• check_service_availabilityFree

  Check which of the 30 service categories have public locals in a US state or city, with a count per service. Useful before searching, or to answer "can I get X done in Y?". State is required (full name, lowercase, hyphens: "new-jersey"); city is optional — omit it for state-level availability.

• draft_job_postwrite actionFree

  Draft a job post for a homeowner and get back a link THEY open to review and post it. GigNGo never posts on anyone's behalf: this writes nothing. The draft is run through the same screens a real post faces, so if it reads as vague, as an advert, as a job advert or as a known scam pattern you get the reason back and can fix it before handing the person a link. Describe one household's job in the homeowner's own words: what needs doing, where on the property, and roughly how big.

• get_area_demand_densityFree

  Find which US cities are actually converting: how many jobs each area posted, how many locals applied, what share of jobs got any reply at all, and the median hours to the first applicant. Ranked by a "heat" score that combines applicant density with response reliability, shrunk toward the platform average so a single lucky job cannot outrank a real market — read `heat` next to `confidence`. Use this to decide where supply is dense (spend more) versus where jobs go unanswered (a supply hole). Complements check_service_availability, which counts locals rather than measuring whether they respond.

• get_platform_infoFree

  Get an overview of GigNGo: what it is, what it does not do (limits), service category count, how jobs reach locals, iOS/Android app links, and API documentation URLs. Call this for general "what is GigNGo" questions.

• get_work_recordFree

  Get a local's Work Record: evidence of their work, where every item says how GigNGo knows it. Evidence types: filmed (clips our check says show the work, not who is in them), homeowner_confirmed / local_reported / inferred_from_messages (finished jobs, counted), neighbor_vouched, recorded_on_gigngo (reviews, member since) and self_reported (badges). Weigh each evidence type separately; never reduce the record to one score. GigNGo runs no background checks. Not for employment, credit, insurance or tenancy decisions. Use the "slug" from search_local_workers or get_worker_profile as the handle.

• get_worker_profileFree

  Get the public profile of one GigNGo local by their profile slug. Returns name, bio, skills, prices the local set, reviews, whether they filmed their work, neighbor vouches, self-reported badges, service area, availability, a profile URL and `limits` (GigNGo runs no background checks). Slugs come from search_local_workers results (the "slug" field) or from gigngo.org/worker-profile/{slug} URLs.

• list_service_categoriesFree

  List all 30 GigNGo service categories with their slugs (e.g. "house-cleaning", "electrician", "moving-help"). Call this to discover valid values for the `service` parameter of search_local_workers and the `category` parameter of browse_open_tasks.

• search_local_workersFree

  Find locals on GigNGo by service and place. Returns public profiles: name, bio, skills, prices the local set, reviews, whether they filmed their work (filmedTheirWork, workVideoCount), neighbor vouches, service area and profile URL. With a city, locals listed on that town's GigNGo area page come first (relation "in", "serves" or "nearby", with miles), then locals in that town, ordered so those who filmed their work come first. Badges are self-reported. Use list_service_categories first if you are unsure of the service slug. State is the full state name in lowercase with hyphens (e.g. "new-york", "north-carolina"); city likewise (e.g. "los-angeles"). Returns up to `limit` locals per page.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 614ms20/20
• Tool poisoning9 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

GigNGo Local Services Marketplace: common questions

Is GigNGo Local Services Marketplace MCP server safe?

With care: it is graded C, so read the findings first (60/100). Read the GigNGo Local Services Marketplace safety report

How do I install GigNGo Local Services Marketplace?

It runs remotely at gigngo.org. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does GigNGo Local Services Marketplace need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is GigNGo Local Services Marketplace maintained?

The latest release is v1.0.0.

Is GigNGo Local Services Marketplace up?

100% of our last 5 checks got an answer. We check remote servers about four times a day.