# Intesta — trust registry lookup (pypi · intesta-mcp)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `intesta-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/io-intesta-intesta-mcp/intesta-mcp.md), [page](https://verifymcp.io/servers/io-intesta-intesta-mcp/intesta-mcp)

## Channel facts

- Registry: `pypi`
- Package: `intesta-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (MIT License) isn't a recognized OSI-approved license.
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 799 tokens (~79/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Intesta — trust registry lookup MCP server?

Intesta — trust registry lookup runs locally as a PyPI package, launched with uvx intesta-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add io-intesta-intesta-mcp -- uvx intesta-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "io-intesta-intesta-mcp": {
      "command": "uvx",
      "args": [
        "intesta-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-intesta-intesta-mcp": {
      "command": "uvx",
      "args": [
        "intesta-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add io-intesta-intesta-mcp -- uvx intesta-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-intesta-intesta-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "intesta-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-intesta-intesta-mcp --command uvx --arg intesta-mcp
```

### Hermes

```yaml
mcp_servers:
  io-intesta-intesta-mcp:
    command: "uvx"
    args: ["intesta-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "io-intesta-intesta-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "intesta-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-intesta-intesta-mcp -t stdio -c uvx -a intesta-mcp
```

### Other

```json
{
  "mcpServers": {
    "io-intesta-intesta-mcp": {
      "command": "uvx",
      "args": [
        "intesta-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 71, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-20 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 55, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-16 (score 69, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-15 (score 53, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-14 (score 68, +2)

- [security regression] Tool safety: pass → unverified
- [security regression] Malware scan: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: 97 → 79
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.1 → 0.2.0

### 2026-09-07 (score 66)

First indexed and scored.

## MCP tools (10)

### `check_trust` (~148 tokens)

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, level A0-A4, attested (true only at A1+), verdict
(sufficient | insufficient | unknown) under a named policy profile for the
given purpose (payment | data_share | follow_instructions), what_is_proven,
proof, facts_public, expires_at (re-check after it), next_step, signature.
A verdict is the registry's proof measured against the profile — never a
guarantee, never financial advice.

Input parameters:

- `domain` (string, required)
- `purpose` (string)

Output parameters:

- `result` (string)

### `get_passport` (~90 tokens)

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). Each fact carries attestation_status / evidence_class, as_of,
effective_expiry and stale — do not rely on a stale fact. Same shape as
the remote server's get_passport.

Input parameters:

- `entity_domain` (string, required)

Output parameters:

- `result` (string)

### `ask` (~94 tokens)

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.
Signed: passport_hash + registry signature you can verify offline.

Input parameters:

- `entity_domain` (string, required)
- `question` (string, required)

Output parameters:

- `result` (string)

### `search_entities` (~68 tokens)

Search published entities by name, domain or vertical (case-insensitive
literal substring, at least 3 characters). Returns at most `limit` matches
(1-50) plus `total`, each with its trust level.

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (string)

### `list_entities` (~38 tokens)

List published entities in the registry with their trust level (first 500
plus the total). On a large registry use search_entities(query) instead.

Output parameters:

- `result` (string)

### `get_trust_ladder` (~43 tokens)

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.

Output parameters:

- `result` (string)

### `search_registry` (~38 tokens)

DEPRECATED alias of search_entities (removed in 0.3.0).

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (string)

### `get_facts` (~33 tokens)

DEPRECATED alias of get_passport (removed in 0.3.0).

Input parameters:

- `domain` (string, required)

Output parameters:

- `result` (string)

### `ask_entity` (~37 tokens)

DEPRECATED alias of ask (removed in 0.3.0).

Input parameters:

- `domain` (string, required)
- `question` (string, required)

Output parameters:

- `result` (string)

### `trust_ladder` (~28 tokens)

DEPRECATED alias of get_trust_ladder (removed in 0.3.0).

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/io-intesta-intesta-mcp/intesta-mcp#diagnostics

## Score history

- 2026-09-21: 71
- 2026-09-20: 56
- 2026-09-19: 55
- 2026-09-18: 55
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 53
- 2026-09-14: 68
- 2026-09-13: 66
- 2026-09-12: 66
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 66
- 2026-09-08: 66
- 2026-09-07: 66

## Common questions

### What is the Intesta — trust registry lookup MCP server?

Intesta — trust registry lookup is an MCP server listed in the public MCP registry as io.intesta/intesta-mcp. One-call trust check for any domain (A0-A4, verdict, signed) + fact passports; same tools as remote. This page covers its PyPI package (intesta-mcp).

### Is the Intesta — trust registry lookup MCP server safe to use?

Intesta — trust registry lookup scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Intesta — trust registry lookup MCP server expose?

Intesta — trust registry lookup exposes 10 tools: check_trust, get_passport, ask, search_entities, list_entities, and 5 more. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.

### Is the Intesta — trust registry lookup MCP server still maintained?

Intesta — trust registry lookup is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/intesta-mcp/
- Socket report: https://socket.dev/pypi/package/intesta-mcp
- Repository: https://github.com/agentlabbusiness/intesta-mcp
- Website: https://intesta.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-intesta-intesta-mcp/intesta-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-intesta-intesta-mcp/intesta-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-intesta-intesta-mcp/intesta-mcp