Canli Capital
NPM · CANLI-MCP · 2 COMPONENTS
315 finance tools, 35 prompts: quant, SEC and EU filings, fact checks, rates, odds, DeFi, macro.
Available components
Last scanned (5 hours ago)
Scores higher than 78% 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
- 3 of 23 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to arhancanli/canlicapital). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 979 tokens (~54/item across 18 items; 3 tools + 15 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
- Supports UI / widget rendering.Pass
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Dependency health: 0.97 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Capabilities: pass functional
- Package version: 0.4.0 → 0.6.0 functional
- Package version: 0.4.0 → 0.5.0 functional
- 14 Oct 26 +32
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: good functional
- First check of Schema quality: pass functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- 13 Oct 26 0
- Package version: 0.3.0 → 0.4.0 functional
- 12 Oct 26 50
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 18 Oct 2026 · Analysed npm/canli-mcp@0.6.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 | arhancanli/canlicapital |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/arhancanli/canlicapital/.github/workflows/mcp-canli-publish.yml@refs/tags/canli-mcp-v0.6.0 |
| Rekor log index | 3261022327 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4bd023d28e4fae3f725b032850fedb823a0727ffbf70744f0793486ccdac56a1bde0137448e7d72c0de4f82d67943e37327cfd177d6f61a9c2e01f2e9 |
Background: How many MCP packages publish verified provenance →
Dependencies 23 packages
| Packages resolved | 23 |
|---|---|
| Stale | 3 |
| 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 →
describe_tool Describe a tool ~37
Get one tool's full description and exact input JSON Schema before calling run_tool.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A tool name from find_tool. |
Structured output declared, but exposes no named fields.
No examples provided.
find_tool Find a tool ~99
Search the 311 finance tools (packs: quant, validation, fundamentals, research, backtest, markets) by what you need, e.g. "deflated sharpe", "black scholes greeks", "revenue as of 2019". Returns names, packs, argument signatures and one-line descriptions, best first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 6. |
| query | string | yes | What you need, in plain words. |
Structured output declared, but exposes no named fields.
No examples provided.
run_tool Run tools ~318
Run one tool ({name, arguments}) or several in one call ({calls: [...]}). Any argument can be {"$file": "path.csv", "column": "close"} (or "columns": [...] / "all") instead of pasted numbers. {"$result": i, "path": "close"} passes batch call i's output into a later call; every result also has a ref ("r1", "r2", ...) that later run_tool calls can pass the same way, {"$result": "r1", "path": "close"}, so data never needs to be copied.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | The tool's arguments (single call). |
| calls | array | – | Several calls in one round trip. Calls without $result references run concurrently. |
| digits | integer | – | Round fractional numbers in the results to this many significant figures (4-6 saves output tokens); whole numbers such as counts, shares and IDs are never changed. Default: as each tool returns them. |
| name | string | – | Tool name from find_tool (single call). |
| receipt | boolean | – | Add input and output SHA-256 and pack versions so the result can be recomputed and compared. |
| return | string | – | For a batch: every result (default) or only the last one. |
| select | array | – | Return only these fields of each result, as dotted paths, e.g. ["verdict", "multiple_testing.best", "rows.0.accession"] (table rows take column names). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Canli Capital MCP server?
Canli Capital runs locally as an npm package, launched with npx -y canli-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 · canli-mcp
claude mcp add arhancanli-canli-mcp -- npx -y canli-mcp
What is the Canli Capital MCP server?
Canli Capital is an MCP server listed in the public MCP registry as io.github.arhancanli/canli-mcp. 315 finance tools, 35 prompts: quant, SEC and EU filings, fact checks, rates, odds, DeFi, macro. This page covers its npm package (canli-mcp).
Is the Canli Capital MCP server safe to use?
Canli Capital scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 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 Canli Capital MCP server expose?
Canli Capital exposes 3 tools: find_tool, describe_tool, run_tool. Their descriptions and schemas cost roughly 454 tokens of context every time the server is loaded.
Is the Canli Capital MCP server still maintained?
Canli Capital is still listed as active in the MCP registry. We last reached this channel on 18 October 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 Canli Capital MCP server under?
Canli Capital declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.