Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

eu.ansvar/chilean-law-mcp

NPM · @ANSVAR/CHILEAN-LAW-MCP

Chilean legislation via MCP — full-text search across statutes and provisions

0 this week 41 Trust /100

Last scanned (16 hours ago)

Scores higher than 19% of npm servers

Deprecated

This server is marked deprecated in the MCP registry.

Trust breakdown (7 categories)

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 Security92
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency65
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to Ansvar-Systems/Chilean-law-mcp). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →

What we tested

Checks we ran (8)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance

Checks we could not complete (6)

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.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

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 →

Changelog

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.

  • 9 Nov 26 0
    • Source repository: unverified → fail ▼ security
  • 8 Nov 26 0
    • Provenance: fail → unverified ▼ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 8 Aug 26 0
    • Known CVEs: partial → pass ▲ security
    • Dependency health: partial → 0.86 functional
  • 2 Aug 26 0
    • Provenance: unverified → pass ▲ security
    • Install scripts: unverified → partial ▲ security
    • Known CVEs: unverified → partial ▲ security
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • The code this package runs automatically changed: postinstall security
    • The attested source repository moved: Ansvar-Systems/Chilean-law-mcp security
    • Dependency health: partial → unverified ▼ functional
    • License: unverified → pass ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Licence: Apache-2.0 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/@ansvar/chilean-law-mcp@1.0.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Ansvar-Systems/Chilean-law-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Ansvar-Systems/Chilean-law-mcp/.github/workflows/publish.yml@refs/tags/v1.0.0
Rekor log index 976453241
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5af167aafaff5607953f50edf5b60669d6f7fe98482bb7958dcdee12511f01bad990dca23c52bfc58fc4973425b73095e9e98169004a4cd51354a86f1

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall Not reviewed test -d dist || npm run build || true

Background: Why install scripts are a supply-chain risk →

Dependencies 94 packages
Packages resolved 94
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the eu.ansvar/chilean-law-mcp server?

eu.ansvar/chilean-law-mcp runs locally as an npm package, launched with npx -y @ansvar/chilean-law-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @ansvar/chilean-law-mcp

# add to Claude Code
claude mcp add eu-ansvar-chilean-law-mcp -- npx -y @ansvar/chilean-law-mcp
Common questions

What is the eu.ansvar/chilean-law-mcp server?

eu.ansvar/chilean-law-mcp is listed in the public MCP registry as eu.ansvar/chilean-law-mcp. Chilean legislation via MCP, full-text search across statutes and provisions. This page covers its npm package (@ansvar/chilean-law-mcp).

Is the eu.ansvar/chilean-law-mcp server safe to use?

eu.ansvar/chilean-law-mcp scores 41 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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.

Is the eu.ansvar/chilean-law-mcp server still maintained?

eu.ansvar/chilean-law-mcp is marked deprecated in the MCP registry. We last reached this channel on 21 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 eu.ansvar/chilean-law-mcp server under?

eu.ansvar/chilean-law-mcp declares the Apache-2.0 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 eu.ansvar/chilean-law-mcp server?

VerifyMCP ran 8 checks on eu.ansvar/chilean-law-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about eu.ansvar/chilean-law-mcp: Security disclosure, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.