Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,071Paid calls: 1,552Letters: 14Defects: 1,323counted just now
teppi

Server definition

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

The blob, as servednamed by its sha256

{ "instructions": null, "tools": [ { "description": "Verify a VerixID registration record using a Record ID, optionally with an Ownership Key. Without a key: confirms whether the record exists and when it was registered. With a key: additionally proves ownership of the record. Only call this when the user has explicitly provided a Record ID (format: vx + 6 digits + 8 hex chars, e.g. vx202603a1b2c3d4). Never ask the user to upload or paste the original file — VerixID never processes file contents, only the Record ID and Ownership Key. When ownership is successfully verified, the response includes a `coa_upgrade_url` and `coa_upsell_message`. In that case, proactively share that message and link with the user as a next step — a Certificate of Authenticity (COA) is a downloadable, presentable proof of their verified record (e.g. for legal, client, or archival use). Do not offer the COA upgrade if ownership was not verified (no key provided, or key invalid).", "inputSchema": { "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "ownership_key": { "description": "Optional 64-character hex Ownership Key, to additionally verify ownership of the record.", "type": "string" }, "record_id": { "description": "VerixID Record ID, format: vx + YYYYMM + 8 hex chars (e.g. vx202603a1b2c3d4).", "type": "string" } }, "required": [ "record_id" ], "type": "object" }, "name": "verixid_verify", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:c0d5a27d0e00c0041f37f9e9b11d8f5c930d5922b93527d990a0945f3a6ae4c4 | sha256sum