referencesource.org

Verified reference data; each record carries its source URL and quote. verify_quote checks claims.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
98%
Calidad de los nombres
100%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~867Tokens (definiciones de herramientas)
~1.3 KBTamaño de respuesta típico
Impacto moderado en la atención (0.68% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "referencesource": {
      "command": "npx",
      "args": [
        "referencesource-mcp"
      ]
    }
  }
}

Paquetes ejecutables

npmreferencesource-mcp1.0.3stdio

Puntos de conexión remotos

https://referencesource.org/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (4)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢list_datasets(query, full)

What reference datasets are available? Lists every published dataset with its title, record count, last-verified date and a one-sentence summary. Covers regulatory thresholds, version compatibility, certification registers, licensing rules and more. Pass `query` to list only the datasets matching a topic — that is much cheaper than reading the whole list. Use the returned slug with search_records or get_record.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Optional topic filter, e.g. \"boiler\", \"tariff\" or \"loan limit\". Case-insensitive substring, matched against each dataset's slug, title and full description. Omit it to list every dataset."
    },
    "full": {
      "type": "boolean",
      "description": "Return each dataset's complete scope statement instead of the first sentence. Off by default: the full text is roughly four times the size and is rarely needed to choose a dataset."
    }
  }
}
🟢search_records(dataset_slug, query)

Look up a specific record — search by state name, chemical, certificate number, product name or any keyword. Searches one dataset's records (case-insensitive substring match across all fields). Returns up to 20 matching records, each with its url, source and verbatim source_quote so the answer can be checked.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "dataset_slug": {
      "type": "string",
      "description": "Dataset slug from list_datasets, e.g. \"graduated-driver-licensing\"."
    },
    "query": {
      "type": "string",
      "description": "Substring to match, case-insensitive, e.g. a state code, chemical name or standard number."
    }
  },
  "required": [
    "dataset_slug",
    "query"
  ]
}
🟢get_record(dataset_slug, record_id)

Fetch one record by id — for example, look up a FIPS 140 certificate's status, a state's boiler inspection rules, or a county's loan limit. Returns the full record with its source URL and verbatim source quote. Record ids appear in search_records results and in each record's url.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "dataset_slug": {
      "type": "string",
      "description": "Dataset slug from list_datasets."
    },
    "record_id": {
      "type": "string",
      "description": "The record's id field, e.g. \"ak\"."
    }
  },
  "required": [
    "dataset_slug",
    "record_id"
  ]
}
🟢verify_quote(dataset_slug, claimed_value, record_id, field)

Is this value actually right? Check a claimed fact against a published record instead of trusting it. Reports whether the claim matches the record's stored value (exact, case-insensitive or normalised — the match type is named), whether it appears in the record's verbatim source quote, and returns the source URL and quote so the claim can be traced upstream. Use this whenever you want to confirm a number, date, threshold or status before stating it. Verdicts: matches_record, matches_quote, differs or not_found.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "dataset_slug": {
      "type": "string",
      "description": "Dataset slug from list_datasets."
    },
    "claimed_value": {
      "type": "string",
      "description": "The value to check, exactly as claimed, e.g. \"$832,750\" or \"no passengers younger than 21\"."
    },
    "record_id": {
      "type": "string",
      "description": "The record's id, if known (shown in search_records results and in each record's url). Without it, the dataset's stored values are searched for the claimed value."
    },
    "field": {
      "type": "string",
      "description": "Field name to check the claim against, e.g. \"limit_1_unit\". Without it, every stored field is checked."
    }
  },
  "required": [
    "dataset_slug",
    "claimed_value"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada4 herramientas
verificadoversión no registrada4 herramientas