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

Tool	What 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

Metadata

Release files for intesta-mcp 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for intesta-mcp 0.2.0
File	Size	Uploaded	Provenance
intesta_mcp-0.2.0.tar.gz	10.7 kB	Sep 14, 2026	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for intesta-mcp 0.2.0
File	Interpreter	ABI	Platform	Reset
intesta_mcp-0.2.0-py3-none-any.whl 8.3 kB Sep 14, 2026 Without provenance	Python 3	none	any	Details

Total release size: 19.0 kB

Release files / intesta_mcp-0.2.0.tar.gz

Download URL	intesta_mcp-0.2.0.tar.gz
Size	10.7 kB
Tags	Source
SHA-256 checksum How to use checksums	`c1feb3a395e07dbbfe0f1e8fdf6ce34ec5f062e1c4991c5783c855eecca4ab07`
BLAKE2b-256 checksum How to use checksums	`83b8d741772bccf2fb9565537ccc3626a3835e5dd0d2e521837f86911eb3b86a`
Upload date	Sep 14, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}`

Release files / intesta_mcp-0.2.0-py3-none-any.whl

Download URL	intesta_mcp-0.2.0-py3-none-any.whl
Size	8.3 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`51a821d3347ad18f8ff6e85427283b2a131dc7a3934795b14d146a880d77da6b`
BLAKE2b-256 checksum How to use checksums	`8b5695aa877d14fa6096aec2b513affe24a544f889ec99bbb1126dd4eb00b0d4`
Upload date	Sep 14, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`uv/0.11.3 {"installer":{"name":"uv","version":"0.11.3","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}`

Security for intesta-mcp 0.2.0

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.