Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,070Paid calls: 1,526Letters: 13Defects: 1,322counted just now
teppi

Server definition

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

The blob, as servednamed by its sha256

{ "instructions": "One tool: rescue_payload. Send the payload that failed and the JSON Schema it failed. Structural repairs only; anything ambiguous is refused with a reason code rather than guessed. Deterministic, no language model.", "tools": [ { "description": "Repair a malformed JSON or API payload so it matches a required schema. Use when a request, webhook, or tool output was rejected for schema validation errors: wrong types, a null where an array or object belongs, a forbidden extra property, or mismatched keys between two APIs. Deterministic repairs only. No semantic guessing. Refuses instead of inventing a value, and returns an exact change manifest plus a signed receipt so a silent 'fix' can never pass downstream unrecorded.\n\nGive it the payload that was rejected and the JSON Schema it failed. It returns one of:\n VALID the payload already conformed; nothing changed\n REPAIRED safely repaired; the returned payload satisfies the schema\n CANNOT_REPAIR no safe repair exists; repaired_payload is null on purpose\n INVALID_SCHEMA the schema is malformed or uses an unsupported keyword\n ERROR bad request, or a size/depth limit was exceeded\n\nIt repairs structure only: unambiguous type coercion, null to empty array or object, removing a property the contract forbids, renaming a key when an explicit mapping rule is supplied, and trimming whitespace that is blocking validation.\n\nIt will NOT invent a value. A missing required field, an ambiguous number like \"1,234.00\", an identifier like \"007\" that would lose its leading zeros, or a date like \"09/06/2026\" whose day/month order is unknown all return CANNOT_REPAIR with a stable reason code rather than a guess.\n\nNo language model is involved. The same input always produces the same output and the same receipt id.", "inputSchema": { "additionalProperties": false, "properties": { "mappings": { "additionalProperties": { "type": "string" }, "description": "Optional explicit key renames, e.g. {\"custId\": \"customer_id\"}. Field equivalence is NEVER inferred without a rule here.", "type": "object" }, "payload": { "description": "The JSON document that failed downstream. Any JSON value." }, "schema": { "description": "The JSON Schema the payload must satisfy. A supported subset; unsupported keywords are rejected, never ignored.", "type": "object" } }, "required": [ "payload", "schema" ], "type": "object" }, "name": "rescue_payload", "outputSchema": { "properties": { "changes": { "description": "Every repair applied, with a JSON path.", "items": { "type": "object" }, "type": "array" }, "original_hash": { "type": "string" }, "path": { "type": [ "string", "null" ] }, "problems": { "description": "Every blocking issue, with a stable reason code.", "items": { "type": "object" }, "type": "array" }, "reason_code": { "type": [ "string", "null" ] }, "receipt": { "description": "Hashes and a signature. No payload content.", "type": "object" }, "receipt_id": { "type": "string" }, "repaired_hash": { "type": [ "string", "null" ] }, "repaired_payload": { "description": "Null when status is CANNOT_REPAIR." }, "schema_valid": { "type": "boolean" }, "status": { "enum": [ "VALID", "REPAIRED", "CANNOT_REPAIR", "INVALID_SCHEMA", "ERROR" ], "type": "string" } }, "required": [ "status", "schema_valid" ], "type": "object" } } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:02491c1c4aa45f02604e6a175d0d5edb6d94943a815db7147260992c30fc446e | sha256sum