Servidor MCP de DamageRestore HQ

Qué servidores del registro oficial de MCP son de DamageRestore HQ, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-13

← Volver a DamageRestore HQ

De quién es el servidor

Nombre en el registrocom.damagerestorehq/siteverificado en el registro MCP

El nombre en el registro está bajo damagerestorehq.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-13

Estadorespondecomprobado el 2026-10-13
Herramientas15
El servidor se llamaDamageRestore HQ (damagerestorehq.com)
Versión del servidor1.0.0
Versión del protocolo2025-06-18

El 2026-10-13 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 1122 ms.

Herramientas que ofrece15 herramientas · leído el 2026-10-13

dataset_columns
The columns, which of them are numeric, the row count and the provenance banner of the DamageRestore HQ dataset. Call this first to learn the schema.
dataset_search
Rows of the DamageRestore HQ dataset whose cells contain the query (case-insensitive), up to 50.
dataset_row
The rows of the DamageRestore HQ dataset where a column equals a value exactly (case-insensitive).
dataset_compare
The rows of the DamageRestore HQ dataset whose column is any of the given values, in the order given — for "X vs Y" questions.
dataset_stats
count, min, max, mean, median and sum of a numeric column of the DamageRestore HQ dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).
dataset_top
The highest (or lowest) rows of the DamageRestore HQ dataset by a numeric column — "which is the most/least X".
dataset_provenance
The source, the date it was computed, the licence and the citation for the DamageRestore HQ dataset. Read this to attribute a figure correctly.
entities_schema
Which fields the DamageRestore HQ register register carries and on how many entities, the regions and services, the identifier schemes, and how to cite it. Call this first.
entity_lookup
The DamageRestore HQ register entry for a firm, by its register identifier (scheme + value, e.g. lei) or by the slug of its page. Exact match; returns the whole record with its page.
entities_search
Entities of DamageRestore HQ register whose name, commercial name, website, address or authority contains the query, optionally within a region (id or name) and a service (slug or name). Up to 50 rows.
entities_in
The DamageRestore HQ register entities in one region (a state or a jurisdiction, by id or name), optionally for one service, 50 a page.
entities_export
Every entity of DamageRestore HQ register, 200 a page, with provenance. Needs an access key (Authorization: Bearer); export pages are metered per key per day. Without a key the answer says how to get one.
enquiry_describe
Read first. States plainly what submit_enquiry does on DamageRestore HQ: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the…
enquiry_fields
Every field of the DamageRestore HQ enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
submit_enquiry
Submits an enquiry to DamageRestore HQ — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a…

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "site": {
      "type": "http",
      "url": "https://damagerestorehq.com/mcp"
    }
  }
}

Otros servidores atribuidos a DamageRestore HQ

com.damagerestorehq/claims-indexaún sin consultarverificado en el registro MCP

Especificación OpenAPI

16 rutas, leído el 2026-10-13. Abrir la especificación ↗

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.