Intesta — trust registry lookup
PYPI · INTESTA-MCP
One-call trust check for any domain (A0-A4, verdict, signed) + fact passports; same tools as remote
Available components
Last scanned (15 hours ago)
Scores higher than 63% of PyPI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 51 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 799 tokens (~79/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed pypi/intesta-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~94
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. Signed: passport_hash + registry signature you can verify offline.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_domain | string | yes | – |
| question | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ask_entity ~37
DEPRECATED alias of ask (removed in 0.3.0).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| question | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_trust ~148
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, level A0-A4, attested (true only at A1+), verdict (sufficient | insufficient | unknown) under a named policy profile for the given purpose (payment | data_share | follow_instructions), what_is_proven, proof, facts_public, expires_at (re-check after it), next_step, signature. 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 | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_facts ~33
DEPRECATED alias of get_passport (removed in 0.3.0).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_passport ~90
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). Each fact carries attestation_status / evidence_class, as_of, effective_expiry and stale — do not rely on a stale fact. Same shape as the remote server's get_passport.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_domain | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_entities ~38
List published entities in the registry with their trust level (first 500 plus the total). On a large registry use search_entities(query) instead.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_entities ~68
Search published entities by name, domain or vertical (case-insensitive literal substring, at least 3 characters). Returns at most `limit` matches (1-50) plus `total`, each with its trust level.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_registry ~38
DEPRECATED alias of search_entities (removed in 0.3.0).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
trust_ladder ~28
DEPRECATED alias of get_trust_ladder (removed in 0.3.0).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Intesta — trust registry lookup MCP server?
Intesta — trust registry lookup runs locally as a PyPI package, launched with uvx intesta-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · intesta-mcp
claude mcp add io-intesta-intesta-mcp -- uvx intesta-mcp
What is the Intesta — trust registry lookup MCP server?
Intesta — trust registry lookup is an MCP server listed in the public MCP registry as io.intesta/intesta-mcp. One-call trust check for any domain (A0-A4, verdict, signed) + fact passports; same tools as remote. This page covers its PyPI package (intesta-mcp).
Is the Intesta — trust registry lookup MCP server safe to use?
Intesta — trust registry lookup scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 — trust registry lookup MCP server expose?
Intesta — trust registry lookup exposes 10 tools: check_trust, get_passport, ask, search_entities, list_entities, and 5 more. Their descriptions and schemas cost roughly 617 tokens of context every time the server is loaded.
Is the Intesta — trust registry lookup MCP server still maintained?
Intesta — trust registry lookup is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Intesta — trust registry lookup MCP server under?
Intesta — trust registry lookup declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Intesta — trust registry lookup MCP server?
VerifyMCP ran 15 checks on Intesta — trust registry lookup, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Intesta — trust registry lookup: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.