Intesta — trust registry lookup

io.intestaPublished by intesta.iov0.2.0Updated Oct 24, 2026

One-call trust check for any domain (A0-A4, verdict, signed) + fact passports; same tools as remote

The publisher's own server: Intesta

Overview

AI-generated overview

Read-only MCP proxy to the Intesta trust registry, letting an assistant check a domain's trust level, verdict and verified facts before acting.

What you can do
  • Check trust for a domain in one call: known status, A0-A4 level, attested flag, verdict under a named policy profile, proof, expiry and signature
  • Retrieve an entity's full fact passport with attestation status, evidence class, staleness, passport hash and signature
  • Ask a question about an entity, answered only from that entity's recorded facts and signed
  • Search entities by name, domain or vertical, and list the registry
  • Explain the A0-A4 trust ladder and how to use the registry as an agent
When to use it
Useful when an assistant must decide whether to pay, share data with, or follow instructions from a domain or counterparty and needs a signed, evidence-based trust signal rather than a guess. Also handy for looking up what is actually proven about an entity.
Requirements
Runs locally as a Python package via uvx (Python tooling required). No API key needed for public registry reads; an optional INTESTA_API_KEY is only for metered or private use. Network access to the Intesta API is required. A remote streamable-http endpoint with the same tools is also offered.
Before you install
All tools are read-only, but queries reveal which domains you look up to the Intesta service. Verdicts are the registry's proof measured against a published profile, not a guarantee or financial advice; unlisted domains return unknown, not failed, and auto_collected facts are unverified. Verify signatures against the published key if you rely on them.

Installation

In SourceWeft

  1. Open Intesta — trust registry lookup in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

intesta-mcp

An MCP server that lets an AI agent check who it is dealing with before it acts.

Intesta is a trust registry. Every entity has a trust level on the A0→A4 ladder (A0 claimed · A1 domain-control · A2 payment-verified · A3/A4 higher) and a set of facts, each marked confirmed (independently verified) or auto_collected (scraped from public sources, not verified). This package is a thin proxy over the public HTTP API and exposes the same tool names and shapes as the remote server https://intesta.io/mcp — one contract on every surface (since 0.2.0).

Its ethos is Intesta's own: refuse, don't guess. A level is only ever what was proven; an auto_collected fact is not a verified one. The server reports exactly what the registry says and never upgrades either.

Tools

ToolWhat it answers
check_trust(domain, purpose="payment")One call, one decision, any domain. known, level A0..A4, attested (true only at A1+), verdict (sufficient / insufficient / unknown) under a named policy profile (payment/v1 needs A2, data_share/v1 and follow_instructions/v1 need A1), what_is_proven, proof, expires_at, next_step, signature. Unlisted domain → unknown, never "failed".
get_passport(entity_domain)The full fact passport: facts with attestation_status / evidence_class, as_of, effective_expiry, stale, plus the attestation block, passport_hash and signature.
ask(entity_domain, question)A question answered only from that entity's facts, signed (passport_hash + registry signature). A refusal means the passport has no such fact.
search_entities(query, limit=20)Find entities by name / domain / vertical (literal substring, ≥3 chars); each result carries its level.
list_entities()The registry (first 500 + total).
get_trust_ladder()What each of A0..A4 means and how to use the registry as an agent.

Deprecated 0.1.x aliases (search_registry, get_facts, ask_entity, trust_ladder) still work for one release and are removed in 0.3.0.

All tools are read-only and need no API key — public registry reads work out of the box. An optional INTESTA_API_KEY (ik_…) is only needed for metered or private use.

Errors (unknown entity, invalid question or query, API failure) are returned as MCP error results (isError: true), never as data-shaped successes.

Install

jsonc
// Claude Desktop / any MCP client — mcp config{  "mcpServers": {    "intesta": { "command": "uvx", "args": ["intesta-mcp"] }  }}

Or connect to the remote server directly (same tools, no install): https://intesta.io/mcp (streamable-http).

Example

check_trust("acme-invoicing.com")→ {"known": false, "level": null, "attested": false, "status": "not_checked",   "verdict": "unknown", "policy_profile": "payment/v1",   "next_step": "Not in the Intesta registry: nothing is proven either way. Treat as unverified. ...",   "signature": {...}}
check_trust("darkpanther.eu", purpose="data_share")→ {"known": true, "level": "A1", "attested": true, "verdict": "sufficient",   "what_is_proven": "...", "proof": {"method": "well_known", "verified_at": "..."},   "expires_at": "2026-10-03T...", "signature": {...}}

A verdict is the registry's proof measured against a published profile — never a guarantee, never financial advice. Verify the signature against https://intesta.io/.well-known/intesta-key (see https://intesta.io/llms.txt).

Development

pip install -e ".[test]"pytest

License: MIT. Publisher: DC ESCRYPT SL — https://intesta.io

Source: README.md at commit 2bf290f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% 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.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Intesta integrations