# Intesta (remote · intesta.io)

Trust registry for agents: check_trust verdict A0-A4, signed fact passports, honest refusals.

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

## Components

- remote · `intesta.io`: 75/100 (this document), [markdown](https://verifymcp.io/servers/io-intesta-registry/intesta.md), [page](https://verifymcp.io/servers/io-intesta-registry/intesta)

## Channel facts

- Endpoint: `https://intesta.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 881 tokens (~146/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Intesta MCP server?

Intesta is a hosted endpoint at https://intesta.io/mcp, so there is nothing to install locally. 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 --transport http io-intesta-registry 'https://intesta.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-intesta-registry": {
      "url": "https://intesta.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-intesta-registry": {
      "type": "http",
      "url": "https://intesta.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-intesta-registry]
url = "https://intesta.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-intesta-registry": {
      "type": "remote",
      "url": "https://intesta.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-intesta-registry --url 'https://intesta.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-intesta-registry:
    url: "https://intesta.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-intesta-registry": {
      "Transport": "http",
      "Url": "https://intesta.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-intesta-registry -t streamable-http -u 'https://intesta.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-intesta-registry": {
      "type": "http",
      "url": "https://intesta.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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 75, +1)

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

### 2026-09-19 (score 74, +1)

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

### 2026-09-16 (score 73, +1)

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

### 2026-09-14 (score 72, 0)

- [functional regression] Schema quality: 695 → 881
- [functional] Schema quality: excellent → good
- [functional] New tool “check_trust”

### 2026-09-13 (score 72, +1)

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

### 2026-09-11 (score 71, +1)

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

### 2026-09-09 (score 70, +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-07 (score 69, +1)

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

## MCP tools (6)

### `list_entities` (~70 tokens)

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.

### `get_passport` (~54 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).

Input parameters:

- `entity_domain` (string, required)

### `ask` (~84 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.

Input parameters:

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

### `search_entities` (~101 tokens)

Search 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.

Input parameters:

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

### `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.

### `check_trust` (~186 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 (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.

Input parameters:

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-intesta-registry/intesta#diagnostics

## Score history

- 2026-09-21: 75
- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 71
- 2026-09-11: 71
- 2026-09-10: 70
- 2026-09-09: 70
- 2026-09-08: 69
- 2026-09-07: 69
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 67
- 2026-09-03: 67
- 2026-09-02: 67
- 2026-09-01: 64
- 2026-08-31: 63
- 2026-08-30: 63
- 2026-08-29: 62
- 2026-08-28: 62
- 2026-08-27: 61

## Common questions

### What is the Intesta MCP server?

Intesta is an MCP server listed in the public MCP registry as io.intesta/registry. Trust registry for agents: check_trust verdict A0-A4, signed fact passports, honest refusals. This page covers its hosted endpoint (https://intesta.io/mcp).

### Is the Intesta MCP server safe to use?

Intesta scores 75 out of 100 on VerifyMCP. 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 MCP server expose?

Intesta exposes 6 tools: list_entities, get_passport, ask, search_entities, get_trust_ladder, check_trust. Their descriptions and schemas cost roughly 538 tokens of context every time the server is loaded.

### Does the Intesta MCP server require authentication?

No. We connected to Intesta without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Intesta MCP server still maintained?

Intesta 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

- Remote endpoint: https://intesta.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-intesta-registry/intesta.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-intesta-registry/intesta.json
- HTML version of this page: https://verifymcp.io/servers/io-intesta-registry/intesta