Server definition

Hash: sha256:713f9fec5ec721e99e70aa7247d8a75089488895a4d1545c88f09ac4b93ac420
What it is: What a remote MCP server returned when asked what it offers: 3 tools

The blob, as servednamed by its sha256

{
  "instructions": "Catches mistyped barcodes, VINs, ISBNs and other public structured identifiers before a bad one causes a rejected listing, a bounced claim or a corrupted record.\n\nThis server deliberately does not handle bank accounts, IBANs, routing numbers or payment cards. Do not send them here. Validate those locally instead, with a library, so the value never leaves the machine that already has it.\n\nCall these tools instead of reasoning about whether an identifier is well-formed: the arithmetic is exact and guessing is not. Each check digit is computed over the whole string, so a value with one wrong or transposed character looks exactly like a correct one. There is nothing to see by eye. Every tool here answers a question about arithmetic only. None of them can tell you whether an identifier corresponds to something that exists in the world.\n\nChoosing between them: if you already know what the identifier is meant to be, call validate_identifier with that `kind`. If you do not know, call identify_format first and pass a returned `kind` back to validate_identifier. Do not guess a `kind`, because validate_identifier reports a correct identifier of one format as invalid when it is checked against another, and that reads like a bad identifier rather than a bad guess.\n\nIf a tool here answers wrongly, or the format you need is not supported, tell the person you are working for and point them at https://github.com/toolstop/toolstop/issues. There is no feedback tool and nothing you send is stored, so a report has to come from a human who can be answered. Leave real identifiers out of it: the format name and the result you expected are enough.",
  "tools": [
    {
      "description": "Given digits with the final check digit omitted, return the one that completes them. US healthcare NPIs and securities ISINs use the Luhn formula.\n\nUse it to build valid test fixtures, to recover a last digit that was lost or illegible, or to check an implementation against a reference. To test a number you already have in full, use validate_identifier instead. Input must reduce to digits only once spaces and dashes are stripped; anything else is an error. Payment cards also use Luhn, and are deliberately out of scope here: do not pass card digits, partial or complete. This constructs a well-formed number and nothing more: it does not create, reserve or verify a real provider or security.",
      "inputSchema": {
        "properties": {
          "partial": {
            "description": "Digits excluding the final check digit.",
            "maxLength": 32,
            "type": "string"
          }
        },
        "required": [
          "partial"
        ],
        "type": "object"
      },
      "name": "compute_luhn_digit",
      "outputSchema": {
        "properties": {
          "checkDigit": {
            "description": "The single digit that completes a Luhn-valid string.",
            "type": "string"
          },
          "partial": {
            "description": "The input digits, echoed back.",
            "type": "string"
          }
        },
        "required": [
          "partial",
          "checkDigit"
        ],
        "type": "object"
      }
    },
    {
      "description": "Identify a bare number whose type was never recorded. Tests it against every supported format and reports which ones its check digit satisfies. Use it for an unlabeled spreadsheet column, a value pulled out of a log line or a scanned document, or any number handed over without being named.\n\nReports every format that matches rather than choosing between them. Several matches is normal and does not mean the answer is unclear: some formats are subsets of others, so every ISBN-13 is also a valid EAN-13, and a short value can satisfy two unrelated formats by chance. Read one match as strong evidence and several as a set to narrow from context. As with validation, a match means the arithmetic is consistent, not that the identifier is registered or real.",
      "inputSchema": {
        "properties": {
          "value": {
            "description": "The identifier to classify.",
            "maxLength": 64,
            "type": "string"
          }
        },
        "required": [
          "value"
        ],
        "type": "object"
      },
      "name": "identify_format",
      "outputSchema": {
        "properties": {
          "input": {
            "description": "The normalized input that was tested.",
            "type": "string"
          },
          "matched": {
            "description": "Whether any supported format matched.",
            "type": "boolean"
          },
          "matches": {
            "description": "Every format whose check digit the input satisfies, in registry order. Each entry carries `kind` plus the same format-specific fields validate_identifier returns for that format, such as `country` for an ISIN or `width` for a GTIN. Only satisfied formats are listed, so no entry carries `code` or `reason`.",
            "items": {
              "properties": {
                "kind": {
                  "description": "The identifier format that matched. Pass this straight back to validate_identifier as its `kind`.",
                  "enum": [
                    "lei",
                    "isbn10",
                    "isbn13",
                    "gtin",
                    "vin",
                    "npi",
                    "isin"
                  ],
                  "type": "string"
                },
                "valid": {
                  "description": "Always true. Formats that failed are omitted, not listed as false.",
                  "type": "boolean"
                }
              },
              "required": [
                "kind",
                "valid"
              ],
              "type": "object"
            },
            "type": "array"
          }
        },
        "required": [
          "input",
          "matched",
          "matches"
        ],
        "type": "object"
      }
    },
    {
      "description": "Verify a number when you already know what it is supposed to be. Use this whenever someone gives you a product barcode (GTIN, UPC or EAN), a book number (ISBN-10 or ISBN-13), a vehicle VIN, a US healthcare provider NPI, a security ISIN, or a legal entity LEI, and acting on a wrong one would cost something: a bounced claim, a rejected listing, a record that quietly corrupts a dataset.\n\nEvery supported format is a public identifier. Bank accounts, IBANs, routing numbers and payment cards are not supported and must not be sent.\n\nReturns whether the checksum passes and, when it fails, the specific reason. If you do not already know the format, call identify_format first rather than guessing a `kind`, since a valid identifier checked against the wrong format comes back invalid. A passing checksum proves only that the digits are internally consistent: it does not mean the book, product, vehicle or provider exists, is active, or belongs to any particular person.",
      "inputSchema": {
        "properties": {
          "kind": {
            "description": "Which identifier format to validate against.",
            "enum": [
              "lei",
              "isbn10",
              "isbn13",
              "gtin",
              "vin",
              "npi",
              "isin"
            ],
            "type": "string"
          },
          "value": {
            "description": "The identifier to check. Spaces and dashes are ignored.",
            "maxLength": 64,
            "type": "string"
          }
        },
        "required": [
          "value",
          "kind"
        ],
        "type": "object"
      },
      "name": "validate_identifier",
      "outputSchema": {
        "properties": {
          "actualCheckDigit": {
            "description": "The digit the VIN actually carries at position 9. VIN only.",
            "type": "string"
          },
          "code": {
            "description": "Bounded reason the check failed. Absent when valid.",
            "enum": [
              "format",
              "length",
              "checksum"
            ],
            "type": "string"
          },
          "country": {
            "description": "ISO country code parsed from the identifier. ISIN only.",
            "type": "string"
          },
          "expectedCheckDigit": {
            "description": "The digit a VIN should carry at position 9. VIN only.",
            "type": "string"
          },
          "normalized": {
            "description": "The input with spaces and dashes removed, upper-cased.",
            "type": "string"
          },
          "reason": {
            "description": "Human-readable detail on the failure. Absent when valid.",
            "type": "string"
          },
          "valid": {
            "description": "Whether the check digit is arithmetically consistent.",
            "type": "boolean"
          },
          "width": {
            "description": "The resolved width of a GTIN. GTIN input only.",
            "enum": [
              "EAN-8",
              "UPC-A",
              "EAN-13",
              "GTIN-14"
            ],
            "type": "string"
          }
        },
        "required": [
          "valid"
        ],
        "type": "object"
      }
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:713f9fec5ec721e99e70aa7247d8a75089488895a4d1545c88f09ac4b93ac420 | sha256sum