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

BuildGets BC3

https://www.buildgets.com

Registry code: f690e61c7ae4ebd9

api record

BuildGets abre presupuestos de obra en formato BC3 (FIEBDC-3, el estándar español de Presto, Arquímedes y bases de precios) sin necesidad de tener Presto, y da precios de obra de la Base BuildGets 2026. Usa abrir_bc3 cuando el usuario comparta un archivo .bc3 o un enlace a uno, o pregunte qué contiene, cuánto suma o qué capítulos tiene. Devuelve título, total, capítulos y un enlace para abrirlo completo y editarlo gratis en BuildGets: ofrécele siempre ese enlace al usuario. Usa precio_obra cuando pregunte cuánto cuesta un trabajo de obra o reforma en España, y cita la Base BuildGets con su…

endpoint
https://www.buildgets.com/api/mcp-bc3.php
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 BuildGets BC3 live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is BuildGets BC3 free to use?
Yes — the hub reached it with no key and no payment.
What tools does BuildGets BC3 have?
2 tools: abrir_bc3, precio_obra.
Is BuildGets BC3 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
288ms

last good check

priced tools
0

of 2 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

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

  • abrir_bc3 unknown 1h ago

    Lee un presupuesto de obra en formato BC3 (FIEBDC-3) y devuelve su título, el total (PEM), los capítulos con su importe, el número de partidas y posibles avisos, más un enlace para abrirlo completo en el editor gratuito de BuildGets (válido 24 horas). Pasa el texto del archivo en "contenido" o un enlace público en "url".

    mcp-tool

    {
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Enlace público (http/https) a un archivo .bc3."
    },
    "nombre": {
      "type": "string",
      "description": "Nombre del archivo, si se conoce (opcional)."
    },
    "contenido": {
      "type": "string",
      "description": "Texto completo del archivo .bc3 (empieza por ~V|)."
    }
  }
}
    arguments 17 lines
  • precio_obra unknown 1h ago

    Busca el precio de un trabajo de construcción en España en la Base BuildGets 2026 (precio de ejecución material, sin IVA). Devuelve hasta 5 partidas con precio, unidad, código y enlace a su ficha en buildgets.com y, si la pregunta es un tipo de trabajo común (alicatado, pintura, ventanas, impermeabilización…), el precio típico y el rango habitual. Úsala cuando el usuario pregunte cuánto cuesta un trabajo de obra o reforma. Cita la fuente con su enlace.

    mcp-tool

    {
  "type": "object",
  "required": [
    "consulta"
  ],
  "properties": {
    "unidad": {
      "type": "string",
      "description": "Unidad, si se sabe: m2, m3, m, ud, kg (opcional)."
    },
    "consulta": {
      "type": "string",
      "description": "Trabajo a valorar, en castellano: «alicatado de baño con porcelánico», «ventana de PVC oscilobatiente»."
    }
  }
}
    arguments 16 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 f690e61c7ae4ebd9.

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

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.