io.intestaPublished by intesta.ioOfficial publisherv0.3.0Updated Oct 24, 2026
Trust registry for agents: check_trust verdict A0-A4, signed fact passports, honest refusals.
A remote trust registry that lets an assistant check a trust verdict (A0–A4) and retrieve signed fact passports for agents.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.intesta%2Fregistry/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"intesta": {
"type": "http",
"url": "https://intesta.io/mcp"
}
}
}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.
Takes no parameters.
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).
entity_domainrequiredAsk a natural-language question about an entity (max 2000 characters). Retrieval is constrained to the entity's passport; each returned fact carries source, attestation status and validity dates. When no matching supported fact is selected, the tool returns an explicit refusal.
questionrequiredentity_domainrequiredSearch 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.
limitqueryrequiredMachine-readable semantics of the A0-A4 trust ladder: what exactly is proven at every level, and how to use the registry as an agent.
Takes no parameters.
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.
domainrequiredpurpose83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
