Intesta
REMOTE · INTESTA.IO · SCANNED SEP 21
Trust registry for agents: check_trust verdict A0-A4, signed fact passports, honest refusals.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · intesta.io
claude mcp add --transport http io-intesta-registry 'https://intesta.io/mcp'
{
"mcpServers": {
"io-intesta-registry": {
"url": "https://intesta.io/mcp"
}
}
} {
"servers": {
"io-intesta-registry": {
"type": "http",
"url": "https://intesta.io/mcp"
}
}
} [mcp_servers.io-intesta-registry] url = "https://intesta.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-intesta-registry": {
"type": "remote",
"url": "https://intesta.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-intesta-registry --url 'https://intesta.io/mcp' --transport streamable-http
mcp_servers:
io-intesta-registry:
url: "https://intesta.io/mcp" {
"McpServers": {
"io-intesta-registry": {
"Transport": "http",
"Url": "https://intesta.io/mcp"
}
}
} assistant mcp add io-intesta-registry -t streamable-http -u 'https://intesta.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 0
- Schema quality: 695 → 881 ▼ functional
- Schema quality: excellent → good functional
- New tool “check_trust” functional
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://intesta.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=intesta.io | CN=YE2,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5645be383716b0291156a4ab073dad7eed5 |
| SANs: intesta.io, www.intesta.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of intesta.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| intesta.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://intesta.io/mcp | Verified | 200 | |
| http (plaintext) | http://intesta.io/mcp | HTTPS enforced | 301 | https://intesta.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_domain | string | yes | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
check_trust ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| purpose | string | – | – |
No output schema declared.
No examples provided.
get_passport ~54
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).
| Name | Type | Req | Description |
|---|---|---|---|
| entity_domain | string | yes | – |
No output schema declared.
No examples provided.
get_trust_ladder ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_entities ~70
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_entities ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
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.