_ registry / mcp http-sse · checked 7m ago

ARCAR_MCP_Server_Trigger

https://nave.q2bot.com

Registry code: f45f4898af9fc2f4

api record

Servidor MCP para integraciones con arcar.org

from a public catalogue that lists it, not from the operator

endpoint
https://nave.q2bot.com/mcp/arcar-org
protocol
http-sse ·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 ARCAR_MCP_Server_Trigger live?
Yes — it answered the hub's last check (checked 7m ago). It answered 100% of checks over the last 30 days.
Is ARCAR_MCP_Server_Trigger free to use?
Not measured yet.
What tools does ARCAR_MCP_Server_Trigger have?
6 tools: Vehiculos_por_Rango_de_Precio, Vehiculos_Recientes, Buscar_Vehiculos, Vehiculos_por_Marca, Vehiculos_Destacados, Obtener_Vehiculo_por_ID.
Is ARCAR_MCP_Server_Trigger 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 99.3%· all time 99.3%

latency
300ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 268 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
iot & hardware vehicles & automotive
used for
  • search vehicle listings
  • get a vehicle by id
  • filter vehicles by brand or price
takes → gives
text, data → data
tools
6 reads
_ 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 6 tools
6 never probed 0 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.

  • Vehiculos_por_Rango_de_Precio reads unknown never probed

    Get, add and update data in Microsoft SQL

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "moneda",
    "precioMinimo",
    "precioMaximo"
  ],
  "properties": {
    "moneda": {
      "type": "string",
      "description": "Moneda del precio: USD para dolares o $ para pesos argentinos"
    },
    "precioMaximo": {
      "type": "number",
      "description": "Precio maximo del rango"
    },
    "precioMinimo": {
      "type": "number",
      "description": "Precio minimo del rango"
    }
  },
  "additionalProperties": true
}
    arguments 24 lines
  • Vehiculos_Recientes reads unknown never probed

    Get, add and update data in Microsoft SQL

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "cantidad"
  ],
  "properties": {
    "cantidad": {
      "type": "number",
      "description": "Cantidad de vehiculos recientes a devolver entre 1 y 20"
    }
  },
  "additionalProperties": true
}
    arguments 14 lines
  • Buscar_Vehiculos reads unknown never probed

    Get, add and update data in Microsoft SQL

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "searchTerm"
  ],
  "properties": {
    "searchTerm": {
      "type": "string",
      "description": "Termino de busqueda para filtrar vehiculos por marca modelo o caracteristicas"
    }
  },
  "additionalProperties": true
}
    arguments 14 lines
  • Vehiculos_por_Marca reads unknown never probed

    Get, add and update data in Microsoft SQL

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "marca"
  ],
  "properties": {
    "marca": {
      "type": "string",
      "description": "Nombre de la marca del vehiculo"
    }
  },
  "additionalProperties": true
}
    arguments 14 lines
  • Vehiculos_Destacados reads unknown never probed

    Get, add and update data in Microsoft SQL

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": true
}
    arguments 6 lines
  • Obtener_Vehiculo_por_ID reads unknown never probed

    Get, add and update data in Microsoft SQL

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "vehicleId"
  ],
  "properties": {
    "vehicleId": {
      "type": "number",
      "description": "ID numerico del vehiculo a consultar"
    }
  },
  "additionalProperties": true
}
    arguments 14 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 f45f4898af9fc2f4.

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