_ registry / mcp + a2a streamable-http · checked 42m ago

vizo-via-publica

https://mcp.vizolatam.com

Registry code: ac8ae1da1b4c2749

api record

Vizo es un marketplace de vía pública (publicidad exterior / OOH) en Paraguay y Uruguay: carteles, vallas, pantallas LED, paradas de ómnibus y pantallas indoor de varias empresas, con su ubicación en el mapa. Usá buscar_espacios para encontrar espacios por ciudad y tipo, ficha_espacio y comparar_espacios para detalles, y plan_de_medios para sugerir una combinación. La mayoría de los precios se cotizan a pedido: solicitar_cotizacion envía el pedido a Vizo (sin costo ni pago), y Vizo responde por email con precio y disponibilidad. Antes de solicitar_cotizacion, mostrale al usuario los espacios,…

endpoint
https://mcp.vizolatam.com/mcp
door code
5263266f62be1ecd
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 vizo-via-publica live?
Yes — it answered the hub's last check (checked 42m ago). It answered 100% of checks over the last 30 days.
Is vizo-via-publica free to use?
Yes — the hub reached it with no key and no payment.
What tools does vizo-via-publica have?
6 tools: ficha_espacio, plan_de_medios, solicitar_cotizacion, comparar_espacios, buscar_espacios, ciudades_y_tipos.
Is vizo-via-publica 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
137ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

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

  • buscar_espacios open 42m ago

    Busca carteles, vallas, pantallas LED, paradas de ómnibus y pantallas indoor en Paraguay y Uruguay por ciudad, tipo y texto libre. Devuelve id, ubicación, formato y la página del espacio.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "pais": {
          "type": "string",
          "description": "Paraguay o Uruguay"
        },
        "tipo": {
          "type": "string",
          "description": "led, cartel, parada/mupi, indoor, reloj o ascensor"
        },
        "texto": {
          "type": "string",
          "description": "Zona, avenida o referencia, ej.: Mariscal López, shopping, ruta"
        },
        "ciudad": {
          "type": "string",
          "description": "Ciudad, ej.: Asunción, Ciudad del Este, Encarnación, Montevideo, Punta del Este"
        },
        "limite": {
          "type": "integer",
          "description": "Cuántos resultados (1 a 30, por defecto 10)"
        }
      }
    }
    arguments 25 lines
  • ciudades_y_tipos open 42m ago

    Lista las ciudades con espacios en Vizo, cuántos hay y de qué tipo, por país.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "pais": {
          "type": "string",
          "description": "Paraguay o Uruguay (opcional)"
        }
      }
    }
    arguments 9 lines
  • ficha_espacio unknown never probed

    Todos los datos públicos de un espacio a partir del id devuelto por buscar_espacios (ubicación, coordenadas, formato, tipo, página).

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "id del espacio, ej.: py-1"
        }
      }
    }
    arguments 12 lines
  • plan_de_medios unknown never probed

    Sugiere una combinación de espacios en una ciudad según el objetivo (marca, lanzamiento, barrio/local, promoción, evento, shopping). El precio final se confirma con solicitar_cotizacion.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ciudad"
      ],
      "properties": {
        "pais": {
          "type": "string"
        },
        "ciudad": {
          "type": "string"
        },
        "cantidad": {
          "type": "integer",
          "description": "Cuántos espacios proponer (1 a 15, por defecto 6)"
        },
        "objetivo": {
          "type": "string",
          "description": "marca, lanzamiento, barrio, local, promoción, evento o shopping"
        },
        "presupuesto": {
          "type": "string",
          "description": "Presupuesto aproximado con moneda, ej.: 5.000.000 PYG por quincena (informativo)"
        }
      }
    }
    arguments 26 lines
  • solicitar_cotizacion unknown never probed

    Envía a Vizo un pedido de cotización (precio y disponibilidad) de uno o más espacios para unas fechas. No cobra nada: Vizo responde por email. Usar SOLO después de mostrar al usuario los espacios, las fechas y sus datos, y con su confirmación explícita.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ids",
        "desde",
        "hasta",
        "nombre",
        "email",
        "whatsapp",
        "confirmado_por_el_usuario"
      ],
      "properties": {
        "ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "ids de los espacios (máx. 15)"
        },
        "desde": {
          "type": "string",
          "description": "Fecha de inicio AAAA-MM-DD"
        },
        "email": {
          "type": "string"
        },
        "hasta": {
          "type": "string",
          "description": "Fecha de fin AAAA-MM-DD"
        },
        "nombre": {
          "type": "string",
          "description": "Nombre de la persona o empresa"
        },
        "mensaje": {
          "type": "string",
          "description": "Comentario opcional (marca, objetivo, presupuesto)"
        },
        "whatsapp": {
          "type": "string",
          "description": "WhatsApp con código de país, ej. 595981123456"
        },
        "confirmado_por_el_usuario": {
          "type": "boolean",
          "description": "true solo si el usuario confirmó explícitamente el envío"
        }
      }
    }
    arguments 48 lines
  • comparar_espacios unknown 42m ago

    Compara hasta 10 espacios por id (ubicación, formato, tipo y ciudad).

    mcp-tool

    {
      "type": "object",
      "required": [
        "ids"
      ],
      "properties": {
        "ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Lista de ids"
        }
      }
    }
    arguments 15 lines
_ try it over mcp 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 ac8ae1da1b4c2749.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ac8ae1da1b4c2749/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/ac8ae1da1b4c2749/badge.svg)](https://brick.blue/agent/ac8ae1da1b4c2749?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 knowoff the mcp door
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
1
ok
1
failed
0
success rate
100%
median latency
148ms
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
—

1 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.