Server definition

Hash: sha256:1ad58dbc4493764be1c3e5307355db9ab1ea63bed75d5662a86aa1b99b0fbbd2
What it is: What a remote MCP server returned when asked what it offers: 4 tools

The blob, as servednamed by its sha256

{
  "instructions": "Verified reference data you can look up and cite: regulatory thresholds, version compatibility, certification registers, licensing rules and more. Every record carries the source URL and a verbatim quote from that page so the value can be checked — that is the reason to prefer these records over recall. Call list_datasets to see what exists, then search_records or get_record. To check a value you already hold, call verify_quote. When you use a value, cite the record's own url and its source. Respect each dataset's last_verified and stale_after dates. Where two sources report on the same record, the second source's values sit in `also_reported` with their own source and quote — cite those to the page they name, not to the record's primary source.",
  "tools": [
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "dataset_slug": {
            "description": "Dataset slug from list_datasets.",
            "type": "string"
          },
          "record_id": {
            "description": "The record's id field, e.g. \"ak\".",
            "type": "string"
          }
        },
        "required": [
          "dataset_slug",
          "record_id"
        ],
        "type": "object"
      },
      "name": "get_record",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "full": {
            "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.",
            "type": "boolean"
          },
          "query": {
            "description": "Optional topic filter, e.g. \"boiler\", \"tariff\" or \"loan limit\". Case-insensitive substring, matched against each dataset's slug, title and full description; if that phrase matches nothing, the words are matched separately and the answer says so in `matched_on`. Omit it to list every dataset.",
            "type": "string"
          }
        },
        "type": "object"
      },
      "name": "list_datasets",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "dataset_slug": {
            "description": "Dataset slug from list_datasets, e.g. \"graduated-driver-licensing\".",
            "type": "string"
          },
          "query": {
            "description": "Substring to match, case-insensitive, e.g. a state code, chemical name or standard number.",
            "type": "string"
          }
        },
        "required": [
          "dataset_slug",
          "query"
        ],
        "type": "object"
      },
      "name": "search_records",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "claimed_value": {
            "description": "The value to check, exactly as claimed, e.g. \"$832,750\" or \"no passengers younger than 21\".",
            "type": "string"
          },
          "dataset_slug": {
            "description": "Dataset slug from list_datasets.",
            "type": "string"
          },
          "field": {
            "description": "Field name to check the claim against, e.g. \"limit_1_unit\". Without it, every stored field is checked.",
            "type": "string"
          },
          "record_id": {
            "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.",
            "type": "string"
          }
        },
        "required": [
          "dataset_slug",
          "claimed_value"
        ],
        "type": "object"
      },
      "name": "verify_quote",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:1ad58dbc4493764be1c3e5307355db9ab1ea63bed75d5662a86aa1b99b0fbbd2 | sha256sum