mcpbeat Sign in

Intesta MCP Server

answering

Intesta is answering right now. Last checked 9 min ago. It exposes 6 tools.

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

Uptime history 23 days of history
23 days agonow
100.0%
Uptime 24h
92 of 92 checks
6
Tools
read from the server
212 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 September 2026. No other catalogue keeps this.

14 Sep a tool appeared check_trust

Nothing serious here today

Today is the operative word: we check Intesta every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add registry --transport http https://intesta.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "registry": {
      "url": "https://intesta.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.registry]
url = "https://intesta.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "registry": {
      "url": "https://intesta.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "registry": {
      "url": "https://intesta.io/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

entities
list_entities
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_entities
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.
trust
check_trust
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.
get_trust_ladder
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.
ask
ask
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.
passport
get_passport
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).

Endpoints

URLTransportStateLatencyChecked
https://intesta.io/mcp streamable-http answering 264 ms 9 min ago

Alternatives to Intesta

same job, measured the same way
Intesta — trust registry lookup
by intesta

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

local only
Purchaseiq
by purchaseiq

Pre-purchase trust checks for AI agents: recalls, scam signals, proceed/caution/avoid verdict.

1 tools answering
I
Orcpin
by npraught

Paid x402 facts for AI agents: signed statements, door reports, endpoint checks, chain reads

223 installs/wk local only
HVTracker MCP
by yugantm

Pre-connect trust checks for AI agents and MCP servers using HVTracker's public trust registry.

63 installs/wk 8 tools answering
C
402
by 402

Trust layer for agent payments (x402, Base): verify agents, risk scores, signed escrow verdicts.

55 installs/wk local only
Scrapecheck
by fieldmodellc

Verify before your agent acts on data it paid for. Signed verdicts, checkable offline, via x402.

3 tools answering
Getregdata
by nolpak14

Business-registry data for agents: one-call Poland KYB verdict, UBO, insolvency, adverse media

66 installs/wk local only
D
Obol
by fly-obol-x402

Pre-trade safety verdicts for agents: token rug/honeypot, calldata guard, wallet risk — signed x402.

3 tools answering

Intesta — questions

Answers built from our own checks of this server.

What can Intesta do?
It exposes 6 tools, read directly from the server on our last check. Among them: ask, check_trust, get_passport, get_trust_ladder, list_entities, search_entities. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Intesta mostly used for?
Its tools cluster around entities and trust. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Intesta working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 212 ms. The bar chart above shows every period we have measured.
How do I connect Intesta?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Intesta need an API key?
No. Intesta completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Intesta?
It answers our handshake in 212 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.