_ registry / mcp streamable-http · checked 57m ago

gigstereo

https://gigstereo.com

Registry code: 200a2db193fef737

api record

Gigstereo is a Colombian marketplace for event services (DJs, mariachis, photographers, bands, decorators, catering…). Typical flow: search_providers or get_price_guide to answer "who can I hire / how much does it cost" in a Colombian city, then request_quotes to send the user's event to matching providers for free once the user agrees. Content is in Spanish and prices are in Colombian pesos (COP). Link the user to the Gigstereo pages the tools return.

endpoint
https://gigstereo.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is gigstereo live?
Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is gigstereo free to use?
Yes — the hub reached it with no key and no payment.
What tools does gigstereo have?
5 tools: search_providers, request_quotes, get_price_guide, get_provider, list_categories.
Is gigstereo safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
311ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 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.

  • list_categories open 57m ago

    Gigstereo's service categories (Spanish names with their slugs) and the Colombian cities that have a city page. Optional: search_providers and request_quotes also understand plain service names.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • search_providers unknown never probed

    Search Gigstereo's marketplace of event providers in Colombia (DJs, mariachis, photographers, videographers, bands, decorators, catering…) by city and, optionally, service or name. Owner-verified profiles show a price range and reviews; unclaimed directory listings show neither. Link the user to each profileUrl. Content is in Spanish; prices are in Colombian pesos (COP).

    mcp-tool

    {
      "type": "object",
      "required": [
        "city"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City in Colombia, e.g. Medellín, Bogotá, Cali, Barranquilla."
        },
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "Maximum results (1-10, default 6)."
        },
        "query": {
          "type": "string",
          "description": "Optional free text matched against provider names and descriptions."
        },
        "category": {
          "type": "string",
          "description": "Service wanted, in Spanish or English (e.g. mariachi, DJ, fotógrafo de bodas, wedding photographer) or a category slug from list_categories."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • request_quotes unknown never probed

    Send the user's event request to matching providers on Gigstereo, for free: the providers who are interested contact the user directly by WhatsApp or email with their price. It is not a booking and costs nothing. Before calling: (1) collect the details from the user — never invent a name, phone or email; (2) show them a summary and tell them that Gigstereo will share their name and contact details with the matching providers, under the privacy policy https://gigstereo.com/privacy and the terms https://gigstereo.com/terms; (3) call only after they explicitly say yes, with userConsent=true. With targetProviderSlug the request goes to that provider; without it, to the providers of the city.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "eventType",
        "eventDate",
        "city",
        "details",
        "userConsent"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City of the event in Colombia."
        },
        "name": {
          "type": "string",
          "description": "The user's name."
        },
        "email": {
          "type": "string",
          "description": "The user's email. Phone or email is required."
        },
        "phone": {
          "type": "string",
          "description": "The user's Colombian mobile/WhatsApp number (10 digits, e.g. 3001234567). Phone or email is required."
        },
        "budget": {
          "type": "string",
          "description": "The user's budget in their words, e.g. hasta 800.000 COP."
        },
        "details": {
          "type": "string",
          "description": "What the user needs, 1-4 sentences (10-1500 characters). Spanish preferred: providers read it."
        },
        "category": {
          "type": "string",
          "description": "Service wanted (e.g. mariachi, DJ, fotógrafo) or a slug from list_categories. Required unless targetProviderSlug is given."
        },
        "eventDate": {
          "type": "string",
          "description": "Event date, YYYY-MM-DD. Not in the past."
        },
        "eventTime": {
          "type": "string",
          "description": "Approximate time, e.g. 8:00 p. m."
        },
        "eventType": {
          "type": "string",
          "description": "Kind of event: boda (wedding), quinceañera, cumpleaños (birthday), serenata, corporativo…"
        },
        "guestCount": {
          "type": "integer",
          "maximum": 100000,
          "minimum": 1,
          "description": "Approximate number of guests."
        },
        "userConsent": {
          "type": "boolean",
          "description": "true only if the user saw the summary and the data-sharing notice above and explicitly agreed to send it."
        },
        "neighborhood": {
          "type": "string",
          "description": "Neighborhood or venue."
        },
        "durationOrSongs": {
          "type": "string",
          "description": "Duration or number of songs, e.g. 1 hora or 10 canciones."
        },
        "targetProviderSlug": {
          "type": "string",
          "description": "Slug of the provider the user chose, if they chose one."
        }
      },
      "additionalProperties": false
    }
    arguments 76 lines
  • get_price_guide unknown 57m ago

    Reference prices Gigstereo publishes for a service in a city, each with its source and the date it was checked, plus the city page (cityPageUrl) that shows them. The only reliable source of price figures here: never invent prices. Cite cityPageUrl when you quote them. Final prices are quoted by each provider.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category",
        "city"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "City in Colombia, e.g. Bogotá."
        },
        "category": {
          "type": "string",
          "description": "Service, e.g. mariachi, DJ, fotógrafo, banda en vivo."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_provider unknown 57m ago

    Public profile of one provider by its slug (the last part of its profileUrl): description, city, service radius, price range and rating when the profile is owner-verified.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Profile slug, e.g. mariachi-los-de-medellin, or the full profileUrl."
        }
      },
      "additionalProperties": false
    }
    arguments 13 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 200a2db193fef737.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/200a2db193fef737/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/200a2db193fef737/badge.svg)](https://brick.blue/agent/200a2db193fef737?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

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.