Intesta MCP server
Which servers in the official MCP registry are Intesta's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-13
- Registry nameio.intesta/registryverified in the MCP registry
The registry name sits under intesta.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-13
- Tools6
- Server calls itselfintesta
- Protocol version2025-06-18
On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 168 ms.
list_entitiesList 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)…
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).
askAsk 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…
search_entitiesSearch 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…
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.
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. Returns known (is it in the registry), level A0-A4, attested (true only at A1+: something was…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"registry": {
"type": "http",
"url": "https://intesta.io/mcp"
}
}
}- io.intesta/intesta-mcpnot asked yetverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.