Endpoints: 28,729MCP servers: 18,413Payout addresses: 2,071Paid calls: 1,552Letters: 14Defects: 1,331counted 4 min ago
teppi

Server definition

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

The blob, as servednamed by its sha256

{ "instructions": "Intesta is a registry of business fact passports (a trust layer for the web). Answers are built ONLY from an entity's passport — if no matching fact exists, you get an honest refusal (that is a guarantee against hallucinations, not an error). Every fact carries an explicit attestation_status (auto_collected / owner_claimed / document_backed / independently_verified) and its source. Trust ladder of the entity itself: A0 (Claimed): The entity is listed in the registry. Its facts are either self-declared by the owner or auto-collected by the registry from public sources (see each fact's attestation_status and source); none have been independently verified.; A1 (Domain control): The owner proved control of the entity's domain by publishing a registry-issued cryptographic token via DNS TXT or an HTTPS /.well-known file; the registry checked it server-side.; A2 (Payment-verified): In addition to A1, the owner completed a real card payment through the registry's payment provider (Stripe Checkout), binding a verified payer — card and billing details vouched by the provider — to the entity. This is payer verification, not a full KYC/identity check (that is A3+).; A3 (Organization): In addition to A2, legal-entity documents were verified and bound to the fact passport.; A4 (Named attestation): Individual facts are attested by named attestors who publicly take responsibility for their accuracy. Typical flow: search_entities(query) or list_entities -> get_passport(domain) or ask(domain, question). Per-entity agent cards also exist at https://intesta.io/.well-known/intesta/{domain}.", "tools": [ { "description": "Ask a natural-language question about an entity (max 2000 characters).\n The answer is built strictly from the entity's attested fact passport; each\n returned fact carries source, attestation status and validity dates. A\n refusal means the passport has no such fact — the engine never guesses.", "inputSchema": { "properties": { "entity_domain": { "title": "Entity Domain", "type": "string" }, "question": { "title": "Question", "type": "string" } }, "required": [ "entity_domain", "question" ], "title": "askArguments", "type": "object" }, "name": "ask", "outputSchema": null }, { "description": "ONE-CALL decision aid before your agent pays, shares data with, or follows\n instructions from a domain — works for ANY domain, listed or not.\n Returns known (is it in the registry), level A0-A4, attested (true only at\n A1+: something was independently verified), verdict for the given purpose\n (sufficient | insufficient | unknown) under a named policy profile,\n what_is_proven, proof, facts_public, expires_at (the earliest freshness\n expiry among the domain's facts — re-check after it), next_step, and the\n registry signature. purpose: payment (default) | data_share | follow_instructions.\n A verdict is the registry's proof measured against the profile — never a\n guarantee, never financial advice.", "inputSchema": { "properties": { "domain": { "title": "Domain", "type": "string" }, "purpose": { "default": "payment", "title": "Purpose", "type": "string" } }, "required": [ "domain" ], "title": "check_trustArguments", "type": "object" }, "name": "check_trust", "outputSchema": null }, { "description": "Full public fact passport of an entity: attested statements with\n sources, plus the attestation block (what the trust level proves, how and\n when it was verified).", "inputSchema": { "properties": { "entity_domain": { "title": "Entity Domain", "type": "string" } }, "required": [ "entity_domain" ], "title": "get_passportArguments", "type": "object" }, "name": "get_passport", "outputSchema": null }, { "description": "Machine-readable semantics of the A0-A4 trust ladder: what exactly is\n proven at every level, and how to use the registry as an agent.", "inputSchema": { "properties": {}, "title": "get_trust_ladderArguments", "type": "object" }, "name": "get_trust_ladder", "outputSchema": null }, { "description": "List published entities in the Intesta registry with their trust level\n (A0-A4; call get_passport for the level's meaning and proof). Returns at\n most 500 entities plus the registry total — on a large registry use\n search_entities(query) instead of paging through everything.", "inputSchema": { "properties": {}, "title": "list_entitiesArguments", "type": "object" }, "name": "list_entities", "outputSchema": null }, { "description": "Search published entities by name, domain or vertical (case-insensitive\n LITERAL substring; wildcard characters are treated as text). Use this\n instead of list_entities when the registry is large. The query must be at\n least 3 characters. Returns at most `limit` matches (1-50) plus `total`,\n the number of matching entities in the whole registry.", "inputSchema": { "properties": { "limit": { "default": 20, "title": "Limit", "type": "integer" }, "query": { "title": "Query", "type": "string" } }, "required": [ "query" ], "title": "search_entitiesArguments", "type": "object" }, "name": "search_entities", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:f90aec78db8fd8a553149c5abf0d15b31d3c45b097649b324c98773f979f5880 | sha256sum