_ registry / mcp streamable-http · checked 17h ago

gigngo

https://gigngo.org

Registry code: cafb71541efbb14e

api record

GigNGo is a US local-services marketplace. Homeowners post jobs and hire free; locals show their work on video, and neighbors can vouch for them. Use these read-only tools to find locals, find videos of locals doing a job, read a local's public profile, see which services have locals in a city or state, and browse open jobs. GigNGo runs no background checks and does not check licenses or insurance. Badges are self-reported by the local. When you recommend a local, say so, and prefer locals whose filmedTheirWork is true. Every result carries a `limits` field; pass it on. Locations use…

endpoint
https://gigngo.org/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
563ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 10 tools
3 open 7 never probed 3 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • browse_open_tasks open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "description": "Optional city slug, lowercase with hyphens. Example: \"los-angeles\"."
    },
    "sort": {
      "enum": [
        "newest",
        "oldest",
        "most_applicants",
        "fewest_applicants",
        "priority"
      ],
      "type": "string",
      "description": "Order of results. \"oldest\" surfaces the jobs that have been waiting longest (the ones about to be abandoned); \"most_applicants\" surfaces where locals are actually competing."
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Max tasks to return (1-50, default 20)."
    },
    "state": {
      "type": "string",
      "description": "Optional full US state name, lowercase, hyphens for spaces. Example: \"pennsylvania\"."
    },
    "category": {
      "type": "string",
      "description": "Optional service category slug, e.g. \"moving-help\". See list_service_categories."
    },
    "maxAgeDays": {
      "type": "integer",
      "maximum": 365,
      "minimum": 1,
      "description": "Only tasks posted within this many days."
    },
    "unanswered": {
      "type": "boolean",
      "description": "Only tasks with zero applicants so far — the unfilled queue."
    }
  }
}
    arguments 44 lines
  • get_area_demand_density open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "sort": {
      "enum": [
        "heat",
        "applicants",
        "responseRate",
        "openUnanswered",
        "jobs",
        "confidence"
      ],
      "type": "string",
      "description": "Ranking. \"openUnanswered\" surfaces supply holes instead of hot markets."
    },
    "limit": {
      "type": "integer",
      "maximum": 300,
      "minimum": 1,
      "description": "Max areas to return (1-300, default 50)."
    },
    "state": {
      "type": "string",
      "description": "Optional state filter — full name or two-letter code, e.g. \"texas\" or \"TX\"."
    },
    "minJobs": {
      "type": "integer",
      "minimum": 1,
      "description": "Only areas with at least this many jobs in the window. Use 5+ for a shortlist of established markets; smaller areas are real but weigh less as evidence."
    }
  }
}
    arguments 32 lines
  • get_platform_info open 17h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_worker_profile unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "The local's profile slug, e.g. \"john-smith-handyman-orlando\"."
    }
  }
}
    arguments 12 lines
  • get_work_record unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "handle"
  ],
  "properties": {
    "handle": {
      "type": "string",
      "description": "The local's public handle or profile slug, e.g. \"juan-lopez-handyman\"."
    }
  }
}
    arguments 12 lines
  • find_work_clips unknown never probed

    Find short videos of locals doing a kind of job, e.g. "deck building", "pressure washing", "house cleaning". Every clip was checked to show someone actually doing the work. Returns a watch page URL (link people there), an embed URL, the local's first name and town, the job's search words, and the local's profile. With a city or state, clips from that town come first (where: "town"), then that state ("state"), then anywhere ("elsewhere") — say which when you show one. A clip shows how someone works, not who they are: GigNGo runs no background checks. Pass on the `limits` field.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job"
  ],
  "properties": {
    "job": {
      "type": "string",
      "description": "The job in a few words, e.g. \"deck staining\", \"furnace repair\"."
    },
    "city": {
      "type": "string",
      "description": "Optional city, lowercase, hyphens for spaces. Example: \"grand-rapids\"."
    },
    "limit": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "Max clips (1-20, default 8)."
    },
    "state": {
      "type": "string",
      "description": "Optional US state, full name (\"michigan\") or code (\"MI\")."
    }
  }
}
    arguments 26 lines
  • draft_job_post unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "description"
  ],
  "properties": {
    "city": {
      "type": "string",
      "description": "Optional city, e.g. \"Saginaw\"."
    },
    "state": {
      "type": "string",
      "description": "Optional US state, e.g. \"michigan\" or \"MI\"."
    },
    "title": {
      "type": "string",
      "description": "Optional short title, e.g. \"Fence repair\"."
    },
    "category": {
      "type": "string",
      "description": "Optional service slug or id. See list_service_categories."
    },
    "description": {
      "type": "string",
      "description": "The job in the homeowner's words, 12-1000 characters."
    }
  }
}
    arguments 28 lines
  • list_service_categories unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • check_service_availability unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "state"
  ],
  "properties": {
    "city": {
      "type": "string",
      "description": "Optional city name, lowercase, hyphens for spaces. Example: \"orlando\". Omit for state-wide availability."
    },
    "state": {
      "type": "string",
      "description": "Full US state name, lowercase, hyphens for spaces. Example: \"florida\"."
    }
  }
}
    arguments 16 lines
  • search_local_workers unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "service",
    "state"
  ],
  "properties": {
    "city": {
      "type": "string",
      "description": "Optional city name, lowercase, hyphens for spaces. Example: \"san-francisco\"."
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "Max locals to return (1-50, default 20)."
    },
    "state": {
      "type": "string",
      "description": "Full US state name, lowercase, hyphens for spaces. Example: \"new-york\"."
    },
    "service": {
      "type": "string",
      "description": "Service category slug, e.g. \"house-cleaning\", \"handyman\", \"lawn-care\"."
    }
  }
}
    arguments 27 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cafb71541efbb14e/badge.svg)](https://brick.blue/agent/cafb71541efbb14e)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.