Cmf Chile
NPM · @PIPEWORX/MCP-CMF-CHILE · 2 COMPONENTS
CMF Chile MCP -- Comision para el Mercado Financiero (Chile's financial regulator).
Available components
Last scanned (10 hours ago)
Scores higher than 55% of npm servers
Category Finance and Payments
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository. View diagnostics → Unverified
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-cmf-chile). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 866 tokens (~288/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- 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.
- Provenance in Provenance & TransparencyRepository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository.
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 −4
- Provenance: pass → unverified ▼ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
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 npm/@pipeworx/mcp-cmf-chile@0.2.1
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 | pipeworx-io/mcp-cmf-chile |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-cmf-chile/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612119752 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:07a88fa5fd48249f5db0c0bb7e859f460f43521d7e307ae18c618e7190dc07f2517f22232dc5e7c4992c92537393cf364a83c70711b0d0181b2275be9 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
cmf_registry ~200
Look up a legal entity in the CMF registers by RUT or name. Returns (1) supervised-entity register hits: CMF code, name, entity type and whether the registration is current; and (2) the register of financial service providers created by Chile's Fintec law, with the services each provider is authorised for (crowdfunding platform, alternative trading system, credit advice, investment advice, custody, order routing, intermediation) and status. RUT may be written 77.532.023-0 or 77532023. An absent entity returns found:false with the scope searched, which means 'not in these registers', not 'does not exist'. Natural persons are never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Entity name or part of it, e.g. "Abaqus". |
| rut | string | – | Chilean RUT of the entity, e.g. "77.532.023-0". |
No output schema declared.
No examples provided.
cmf_regulation ~226
Look up CMF regulations: NCG (normas de carácter general), CIR (circulares) and OFC (oficios circulares). Pass a number (with type NCG|CIR|OFC) to resolve one norm, e.g. type=NCG number=514 returns its title, issue date, PDF link, the resolution that approved it, and which norms modify, repeal or are modified by it. Or pass a Spanish keyword query (e.g. "finanzas abiertas") and/or a year to list matching norms, newest first. At least one of number, query or year is required.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number|string | – | Max norms to return (default 20, max 100). |
| number | number|string | – | Norm number, e.g. 514. |
| query | string | – | Spanish keyword(s) searched in the norm text/title, e.g. "finanzas abiertas". |
| type | string | – | Norm type. Default ALL. |
| year | number|string | – | Issue year, e.g. 2026. |
No output schema declared.
No examples provided.
cmf_sanctions ~384
Search the CMF (Chile's financial regulator) register of sanction resolutions, about 1,500 resolutions from 2002 to today: each row has the resolution number, date, subject (e.g. 'APLICA SANCIÓN A ITAÚ CORREDORES DE BOLSA LIMITADA') and a link to the resolution document. Filter by free-text query (Spanish; matches the subject, accent- and case-insensitive, all words must match) and/or year. Resolutions that name individuals are served with the person's name as the register publishes it (Bruce's case ruling of 2026-10-25, scoped to this tool): every row carries its source record (resolution number, date, CMF document link); no address is ever served for an individual and a natural person's RUT is stripped from the subject; anyone named can ask for removal at support@pipeworx.io and a removed name is replaced in the subject and its document link dropped (counted in withheld_by_removal_request). Each row has a subject_kind (person | organisation | mixed | unclassified) assigned only from explicit cues in the subject (honorific = person; corporate-form word = organisation); a bare personal name with neither cue is 'unclassified', not guessed, and subject_kind_basis says why. When nothing matches, returns found:false with the exact scope searched (a sanction announced in a press release but absent from the register is not covered).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number|string | – | Max rows to return (default 25, max 200). Newest first. |
| query | string | – | Optional Spanish words to match in the resolution subject, e.g. "Itaú" or "Cooperativa Oriente". All words must match. |
| year | number|string | – | Optional resolution year, e.g. 2026. |
No output schema declared.
No examples provided.
How do I install the Cmf Chile MCP server?
Cmf Chile runs locally as an npm package, launched with npx -y @pipeworx/mcp-cmf-chile. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-cmf-chile
claude mcp add pipeworx-io-cmf-chile -- npx -y @pipeworx/mcp-cmf-chile
What is the Cmf Chile MCP server?
Cmf Chile is an MCP server listed in the public MCP registry as io.github.pipeworx-io/cmf-chile. CMF Chile MCP -- Comision para el Mercado Financiero (Chile's financial regulator). This page covers its npm package (@pipeworx/mcp-cmf-chile).
Is the Cmf Chile MCP server safe to use?
Cmf Chile scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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.
What tools does the Cmf Chile MCP server expose?
Cmf Chile exposes 3 tools: cmf_sanctions, cmf_regulation, cmf_registry. Their descriptions and schemas cost roughly 810 tokens of context every time the server is loaded.
Is the Cmf Chile MCP server still maintained?
Cmf Chile 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 Cmf Chile MCP server under?
Cmf Chile 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 Cmf Chile MCP server?
VerifyMCP ran 15 checks on Cmf Chile, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Cmf Chile: Provenance. 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.