Intesta
Trust registry for agents: check_trust verdict A0-A4, signed fact passports, honest refusals.
Sollte ich dies verwenden
Qualität und Sicherheit
Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.
Kontextkosten
Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.
Installieren
Installation mit einem Klick
Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:
{
"mcpServers": {
"registry": {
"url": "https://intesta.io/mcp"
}
}
}Remote-Endpunkte
https://intesta.io/mcpstreamable-httpWas es kann
Tool-Inventar
Tools (6)
🟢list_entities
List published entities in the Intesta registry with their trust level (A0-A4; call get_passport for the level's meaning and proof). Returns at most 500 entities plus the registry total — on a large registry use search_entities(query) instead of paging through everything.
Eingabe-Schema
{
"type": "object",
"properties": {},
"title": "list_entitiesArguments"
}🟢get_passport(entity_domain)
Full public fact passport of an entity: attested statements with sources, plus the attestation block (what the trust level proves, how and when it was verified).
Eingabe-Schema
{
"type": "object",
"properties": {
"entity_domain": {
"title": "Entity Domain",
"type": "string"
}
},
"required": [
"entity_domain"
],
"title": "get_passportArguments"
}⚪ask(entity_domain, question)
Ask a natural-language question about an entity (max 2000 characters). The answer is built strictly from the entity's attested fact passport; each returned fact carries source, attestation status and validity dates. A refusal means the passport has no such fact — the engine never guesses.
Eingabe-Schema
{
"type": "object",
"properties": {
"entity_domain": {
"title": "Entity Domain",
"type": "string"
},
"question": {
"title": "Question",
"type": "string"
}
},
"required": [
"entity_domain",
"question"
],
"title": "askArguments"
}🟢search_entities(query, limit)
Search published entities by name, domain or vertical (case-insensitive LITERAL substring; wildcard characters are treated as text). Use this instead of list_entities when the registry is large. The query must be at least 3 characters. Returns at most `limit` matches (1-50) plus `total`, the number of matching entities in the whole registry.
Eingabe-Schema
{
"type": "object",
"properties": {
"query": {
"title": "Query",
"type": "string"
},
"limit": {
"default": 20,
"title": "Limit",
"type": "integer"
}
},
"required": [
"query"
],
"title": "search_entitiesArguments"
}🟢get_trust_ladder
Machine-readable semantics of the A0-A4 trust ladder: what exactly is proven at every level, and how to use the registry as an agent.
Eingabe-Schema
{
"type": "object",
"properties": {},
"title": "get_trust_ladderArguments"
}🟢check_trust(domain, purpose)
ONE-CALL decision aid before your agent pays, shares data with, or follows instructions from a domain — works for ANY domain, listed or not. Returns known (is it in the registry), level A0-A4, attested (true only at A1+: something was independently verified), verdict for the given purpose (sufficient | insufficient | unknown) under a named policy profile, what_is_proven, proof, facts_public, expires_at (the earliest freshness expiry among the domain's facts — re-check after it), next_step, and the registry signature. purpose: payment (default) | data_share | follow_instructions. A verdict is the registry's proof measured against the profile — never a guarantee, never financial advice.
Eingabe-Schema
{
"type": "object",
"properties": {
"domain": {
"title": "Domain",
"type": "string"
},
"purpose": {
"default": "payment",
"title": "Purpose",
"type": "string"
}
},
"required": [
"domain"
],
"title": "check_trustArguments"
}Empfohlene Prompts
search_entitiessearch_entitiesget_passportget_passportlist_entitiesCommunity
Nachweis