Skip to content

Intesta MCP server

io.intesta/registryintesta.iostreamable-httpv0.3.0Scanned

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

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Intesta MCP server can do

The Intesta MCP server is published by intesta.io, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: ask and check_trust), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 0.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • askAsk a natural-language question about an entity (max 2000 characters).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Ask a natural-language question about an entity (max 2000 characters). Retrieval is constrained to the entity's passport; each returned fact carries source, attestation status and validity dates. When no matching supported fact is selected, the tool returns an explicit refusal.
  • check_trustONE-CALL decision aid before your agent pays, shares data with, or follows instructions from a domain — works for ANY domain, listed or not.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 4Show 4 read-only tools
  • get_passportFull 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).No findings

    Why it is in this group

    • The name "get_passport" says "get": a word for reading.
    Description, as the server wrote it
    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).
  • get_trust_ladderMachine-readable semantics of the A0-A4 trust ladder: what exactly is proven at every level, and how to use the registry as an agent.No findings

    Why it is in this group

    • The name "get_trust_ladder" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_entitiesList published entities in the Intesta registry with their trust level (A0-A4; call get_passport for the level's meaning and proof).No findings

    Why it is in this group

    • The name "list_entities" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • search_entitiesSearch published entities by name, domain or vertical (case-insensitive LITERAL substring; wildcard characters are treated as text).No findings

    Why it is in this group

    • The name "search_entities" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:13 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://intesta.io/mcp: tools/list returned 6 tools to an anonymous client, including ask (write), check_trust (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http registry https://intesta.io/mcp
claude mcp add --transport http registry https://intesta.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__registry__list_entities",
      "mcp__registry__get_passport",
      "mcp__registry__search_entities",
      "mcp__registry__get_trust_ladder"
    ],
    "ask": [
      "mcp__registry__ask",
      "mcp__registry__check_trust"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as registry. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.intesta/registry/verify?hash=d832dd3c963351425294d7cb17ed1a3ba505ccc62dfbbc37e35d3a5416ae1490" | jq -e '.changed == false'

Pinned hash d832dd3c9633, from Nov 18, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.intesta/registry/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.intesta/registry
[![Anlyon Radar](https://radar.anlyon.com/badge/io.intesta/registry.svg)](https://radar.anlyon.com/servers/io.intesta/registry)

Source: MCP Registry. Synced Oct 21, 2026, 18:52 UTC.

Intesta MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Intesta MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Intesta MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Intesta MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Intesta MCP server have?

6 tools: 2 write, 4 read. ask, check_trust, list_entities, get_passport, search_entities and get_trust_ladder.

Does the Intesta MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Intesta MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Intesta MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.