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

nexusai-publico

https://api.nexusai.company

Registry code: 32c3282aebbee975

api record

Información pública de NexusAI, empresa boliviana de software con IA para negocios (chatbot de WhatsApp que vende, caja e inventario, pedidos para restaurantes, citas, tarjetas de fidelidad, condominios y contabilidad). Usa nexusai_recomendar con el tipo de negocio para sugerir el producto que le sirve; para contratar, WhatsApp +591 75312048.

endpoint
https://api.nexusai.company/mcp/publico
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 nexusai-publico live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is nexusai-publico free to use?
Yes — the hub reached it with no key and no payment.
What tools does nexusai-publico have?
4 tools: nexusai_recomendar, nexusai_detalle_producto, nexusai_productos, nexusai_contacto.
Is nexusai-publico 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
554ms

last good check

priced tools
0

of 4 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 4 tools
2 open 2 never probed 2 of 4 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.

  • nexusai_productos open 2h ago

    Qué es NexusAI (software con IA para negocios en Bolivia) y la lista de sus productos con lo que hace cada uno, el precio y el enlace. Úsala cuando alguien pregunte por un chatbot de WhatsApp, sistema de ventas, software para restaurantes, agenda de citas, tarjeta de fidelidad, administración de condominios o contabilidad para un negocio en Bolivia.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • nexusai_contacto open 2h ago

    Cómo contratar un producto de NexusAI (WhatsApp de ventas, forma de pago, condiciones), guías prácticas para negocios y cómo un cliente conecta su asistente de IA a su cuenta por MCP.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • nexusai_recomendar unknown never probed

    Dado un tipo de negocio y lo que necesita (p. ej. "pizzería que recibe pedidos por WhatsApp" o "barbería que quiere recordar citas"), devuelve los productos de NexusAI que le sirven, ordenados, con el motivo, el precio y cómo empezar.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "negocio"
      ],
      "properties": {
        "negocio": {
          "type": "string",
          "maxLength": 300,
          "minLength": 2,
          "description": "Tipo de negocio y qué necesita, en palabras del usuario"
        }
      }
    }
    arguments 15 lines
  • nexusai_detalle_producto unknown 2h ago

    Todo sobre un producto de NexusAI: qué hace, para quién es, qué incluye, cómo se empieza, precio y preguntas frecuentes. Productos: Tienda IA, Gestor IA, Pedidos IA, Clientes IA, Fidelidad IA, Condominios IA, NexusContable.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "producto"
      ],
      "properties": {
        "producto": {
          "type": "string",
          "maxLength": 60,
          "minLength": 2,
          "description": "Nombre o id del producto, p. ej. \"Pedidos IA\""
        }
      }
    }
    arguments 15 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 32c3282aebbee975.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/32c3282aebbee975/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/32c3282aebbee975/badge.svg)](https://brick.blue/agent/32c3282aebbee975?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
80%

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.