English Français العربية

Intesta — trust registry lookup

Official registry Other

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package intesta-mcp
Claude Code 
claude mcp add intesta-trust-registry-lookup -e 'INTESTA_API_KEY=<your intesta_api_key>' -- uvx intesta-mcp==0.2.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "intesta-trust-registry-lookup": {
            "command": "uvx",
            "args": [
                "intesta-mcp==0.2.0"
            ],
            "env": {
                "INTESTA_API_KEY": "<your intesta_api_key>"
            }
        }
    }
}

Environment variables

  • INTESTA_API_KEY secret Optional Intesta API key (ik_...). Public registry reads work without one; a key is only needed for metered or private use.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. intesta-mcp
  2. Tools
  3. Install
  4. Example
  5. Development

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

// 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

Frequently asked questions

What is Intesta — trust registry lookup?

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

How do I install Intesta — trust registry lookup?

It runs on your machine. In Claude Code: claude mcp add intesta-trust-registry-lookup -e 'INTESTA_API_KEY=<your intesta_api_key>' -- uvx intesta-mcp==0.2.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Intesta — trust registry lookup need an API key?

Yes. It expects INTESTA_API_KEY, which you set in its configuration.

Is Intesta — trust registry lookup open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Intesta — trust registry lookup?

It is published by agentlabbusiness. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.