Intesta — trust registry lookup MCP server
io.intesta/intesta-mcp·v0.2.0One-call trust check for any domain (A0-A4, verdict, signed) + fact passports; same tools as remote
0 stars25 downloads/wk
Reviews
Write oneNobody has reviewed Intesta — trust registry lookup yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Intesta — trust registry lookup tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 19 days ago15/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace5/10
How Intesta — trust registry lookup compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 57% of 48,243 servers
- Downloads a week
- 25
- more than 11% of 12,306 servers with a package
Install Intesta — trust registry lookup in Claude Code, Cursor or VS Code
claude mcp add intesta-mcp -- uvx intesta-mcp
What the publisher says
From the Intesta — trust registry lookup repository's README, as published. We do not edit it. Read it on GitHub
intesta-mcp
<!-- mcp-name: io.intesta/intesta-mcp -->
An MCP server that lets an AI agent check who it is dealing with before it acts.
Intesta is a trust registry. Every entity has a trust level on the A0→A4 ladder (A0 claimed · A1 domain-control · A2 payment-verified · A3/A4 higher) and a set of facts, each marked confirmed (independently verified) or autocollected (scraped from public sources, not verified). This package is a thin proxy over the public HTTP API and exposes the same tool names and shapes as the remote server https://intesta.io/mcp** — one contract on every surface (since 0.2.0).
Its ethos is Intesta's own: refuse, don't guess. A level is only ever what was proven; an auto_collected fact is not a verified one. The server reports exactly what the registry says and never upgrades either.
Tools
Deprecated 0.1.x aliases (searchregistry, getfacts, askentity, trustladder) still work for one release and are removed in 0.3.0.
All tools are read-only and need no API key — public registry reads work out of the box. An optional INTESTAAPIKEY (ik_…) is only needed for metered or private use.
Errors (unknown entity, invalid question or query, API failure) are returned as MCP error results (isError: true), never as data-shaped successes.
Install
// Claude Desktop / any MCP client — mcp config
{
"mcpServers": {
"intesta": { "command": "uvx", "args": ["intesta-mcp"] }
}
}Or connect to the remote server directly (same tools, no install): https://intesta.io/mcp (streamable-http).
Example
check_trust("acme-invoicing.com")
→ {"known": false, "level": null, "attested": false, "status": "not_checked",
"verdict": "unknown", "policy_profile": "payment/v1",
"next_step": "Not in the Intesta registry: nothing is proven either way. Treat as unverified. ...",
"signature": {...}}
check_trust("darkpanther.eu", purpose="data_share")
→ {"known": true, "level": "A1", "attested": true, "verdict": "sufficient",
"what_is_proven": "...", "proof": {"method": "well_known", "verified_at": "..."},
"expires_at": "2026-10-03T...", "signature": {...}}A verdict is the registry's proof measured against a published profile — never a guarantee, never financial advice. Verify the signature against https://intesta.io/.well-known/intesta-key (see https://intesta.io/llms.txt).
Development
pip install -e ".[test]"
pytestLicense: MIT. Publisher: DC ESCRYPT SL — https://intesta.io
Nothing above is checked by us. What we check is on the safety report.
Intesta — trust registry lookup: common questions
- Is Intesta — trust registry lookup MCP server safe?
- Mostly: it is graded B (78/100). Read the Intesta — trust registry lookup safety report
- How do I install Intesta — trust registry lookup?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Intesta — trust registry lookup need an API key?
- Yes. The registry entry asks for
INTESTA_API_KEY. - Is Intesta — trust registry lookup maintained?
- The last commit was 52 days ago (2026-09-14). The latest release is v0.2.0.
- What can I use instead of Intesta — trust registry lookup?
- Servers from other publishers that do the same job: Domain Liveness MCP server.
- How does Intesta — trust registry lookup compare with other MCP servers?
- safety score 78/100 (higher than 57% of 48,243 servers); downloads a week 25 (more than 11% of 12,306 servers with a package). Full comparison.
Alternatives to Intesta — trust registry lookup
Same job from other publishers: the closest match first, then the best rated.
- Domain LivenessIs this business's website still there? Checks apex and www, and DNS separately from HTTP.not reviewedEstablishedA