Canli Validation
NPM · CANLI-VALIDATION-MCP · 2 COMPONENTS · SCANNED SEP 27
Deflated Sharpe and PBO checks. A verdict is not admission to anything and is not a forecast.
Available components
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 Security63
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
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 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3026 tokens (~189/item across 16 items; 14 tools + 2 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 Management70
- Stability observed for 21 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
How do I install the Canli Validation MCP server?
Canli Validation runs locally as an npm package, launched with npx -y canli-validation-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-validation-mcp
claude mcp add arhancanli-canli-validation-mcp -- npx -y canli-validation-mcp
{
"mcpServers": {
"arhancanli-canli-validation-mcp": {
"command": "npx",
"args": [
"-y",
"canli-validation-mcp"
]
}
}
} {
"servers": {
"arhancanli-canli-validation-mcp": {
"command": "npx",
"args": [
"-y",
"canli-validation-mcp"
]
}
}
} codex mcp add arhancanli-canli-validation-mcp -- npx -y canli-validation-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"arhancanli-canli-validation-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"canli-validation-mcp"
],
"enabled": true
}
}
} openclaw mcp add arhancanli-canli-validation-mcp --command npx --arg -y --arg canli-validation-mcp
mcp_servers:
arhancanli-canli-validation-mcp:
command: "npx"
args: ["-y", "canli-validation-mcp"] {
"McpServers": {
"arhancanli-canli-validation-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"canli-validation-mcp"
]
}
}
} assistant mcp add arhancanli-canli-validation-mcp -t stdio -c npx -a -y canli-validation-mcp
{
"mcpServers": {
"arhancanli-canli-validation-mcp": {
"command": "npx",
"args": [
"-y",
"canli-validation-mcp"
]
}
}
} 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.
- 27 Sept 26 −10
- Known CVEs: pass → unverified ▼ security
- Schema quality: 168 → 189 ▼ functional
- Schema quality: 168 → 190 ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Dependency health: 0.85 → 1.00 ▲ functional
- First check of Tool coverage: 100 functional
- Package version: 0.7.0 → 0.8.2 functional
- Package version: 0.7.0 → 0.8.1 functional
- Package version: 0.7.0 → 0.8.0 functional
- Package version: 0.7.0 → 0.7.1 functional
- 26 Sept 26 +15
- Known CVEs: unverified → pass ▲ security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Dependency health: unverified → 0.85 ▲ functional
- Schema quality: fair → excellent functional
- Package version: 0.5.0 → 0.7.0 functional
- Package version: 0.5.0 → 0.6.0 functional
- 25 Sept 26 +2
- Known CVEs: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: arhancanli/canlicapital security
- Schema quality: 786 → 1027 ▼ functional
- Schema quality: 786 → 939 ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- First check of Schema quality: 100 functional
- Package version: 0.2.0 → 0.5.0 functional
- Package version: 0.2.0 → 0.4.0 functional
- Package version: 0.2.0 → 0.3.1 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- Schema quality: 644 → 786 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.2 → 0.2.0 functional
- 21 Sept 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 20 Sept 26 −10
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.43 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.2 functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 27 Sept 2026 · Analysed npm/canli-validation-mcp@0.8.2
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-publish.yml@refs/tags/mcp-v0.8.2 |
| Rekor log index | 2977366873 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:25e37f88dcd3f56f70e1c5aec51c7bd89cd1fc912897fadc7beb1cc00154f8f58d1f817beea4e6441b5a4565658ecb2f3ac3710c6c5b04553ef4652c8 |
Background: How many MCP packages publish verified provenance →
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 →
audit_backtest Audit a backtest ~450
Audit one strategy's return series in one call: deflated Sharpe, the minimum track record length for its Sharpe to beat the benchmark, and, with every variant's returns, the probability of backtest overfitting. Point returns_file at the backtest's CSV or JSON rather than copying long series into the call. Each check is the matching validate_ tool's result with its own receipt, side by side; the audit does not grade the strategy. Prefer it to calling those validators one by one when you have one strategy's return series. Uses one validation per check. A deflated Sharpe or overfitting probability above or below any threshold is not admission to anything and is not a forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| benchmark_sharpe_annualized | number | – | Annualized Sharpe to beat; default 0. |
| confidence | number | – | Between 0 and 1; default 0.95. |
| cross_trial_sharpe_sd_annualized | number | yes | Standard deviation of the annualized Sharpe across those trials. |
| effective_independent_trials | integer | yes | Independent variants tried before choosing this one. |
| n_splits | integer | – | Even number of blocks, at least 2; default 16. |
| periods_per_year | number | yes | Observations per year: 252 daily, 365 daily crypto, 52 weekly, 12 monthly. |
| returns | array | – | Periodic returns as fractions (0.01 is 1%), oldest first; replaces the Sharpe, observations, skew and kurtosis fields. |
| returns_column | – | – | Header name or 1-based position of the returns column when returns_file has several numeric columns. |
| returns_file | string | – | Path to a CSV or JSON file of the returns on the machine running this server, instead of returns. Not available on the hosted endpoint. |
| variants | array | – | Optional returns of every variant tried, this one included, as fractions: one row per period, one column per variant. Adds the overfitting check. |
| variants_file | string | – | Path to a CSV or JSON file of every variant's returns (one numeric column per variant), instead of variants. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | object | – | – |
| error | – | – | – |
| limits | array | – | – |
| not_run | object | – | – |
| note | string | – | – |
| readings | object | – | – |
No examples provided.
company_financial_history Company financial history (SEC) ~213
SEC-reported financial history for one company from the canlicapital.com company reference (GET /company-data/{cik}.json), by cik or by ticker (resolved through GET /api/v1/company-tickers.json, companies in the release only). Without a concept it lists the available histories; with one it returns observations, newest first, each with its filing accession, form, filed date and unit, plus the SHA-256 of the original SEC response. No key required. Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | SEC CIK; send cik or ticker. |
| concept | string | – | us-gaap concept such as Assets; omit to list them. |
| limit | integer | – | Most observations, newest first; default 40. |
| ticker | string | – | Ticker such as AAPL; send ticker or cik. |
| Name | Type | Req | Description |
|---|---|---|---|
| claim_boundary | string | – | – |
| company | object | – | – |
| error | – | – | – |
| histories | array | – | – |
| history | object | – | – |
| source | object | – | – |
No examples provided.
get_key Get a free validation key ~137
Issue a free canlicapital.com validation key (POST /api/v1/keys) and hold it in memory for this session. Only needed before a validation when neither CANLI_KEY nor local mode is set; the read tools (get_receipt, service_status, company_financial_history) never need a key. Quotas: 1000 validations per key per UTC day, 5 keys per client per UTC day, 1048576 bytes per validation request, 1024 bytes per key revocation request, 20000 observations per series, 200 variants per matrix.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Name for the key. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | – | – | – |
| key_present | boolean | – | – |
| key_source | string | – | – |
| note | string | – | – |
No examples provided.
get_receipt Get a receipt ~111
Fetch a stored verdict by receipt id (GET /api/v1/receipts/{id}) to re-read an earlier result. No key. To check that the receipt is genuine, use verify_receipt. The receipt is content-hashed, reproducible from the open-source core it names, and signed with Ed25519 by a key published at https://canlicapital.com/.well-known/canli-receipt-keys.json.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Receipt id from a validation result. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
No examples provided.
service_status Service status ~75
Whether the validation API is up, with quota constants (GET /api/v1/validate/status); check after a timeout before resubmitting. No key. This verdict is about the series exactly as submitted. The service never saw the data source, its costs, survivorship, or any lookahead in how the series was built.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
No examples provided.
validate_backtest_length Minimum backtest length ~212
Minimum backtest length, in years, before the best of N independent trials is not expected to reach a target Sharpe by luck, and with backtest_years, the most independent trials those years allow. Send effective_independent_trials, backtest_years, or both. Use it before or while planning a search, to size the backtest for the number of trials; once a search has a result, use validate_deflated_sharpe. A deflated Sharpe or overfitting probability above or below any threshold is not admission to anything and is not a forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| backtest_years | number | – | Length of the backtest in years, to get the most independent trials it allows. |
| effective_independent_trials | integer | – | Independent trials (backtests, parameter sets, ideas) tried; gives the minimum backtest length. |
| target_sharpe_annualized | number | – | In-sample annualized Sharpe you would take as a discovery; default 1. |
| Name | Type | Req | Description |
|---|---|---|---|
| computed | string | – | – |
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
| note | string | – | – |
| receipt | – | – | – |
No examples provided.
validate_breadth Validate breadth ceiling ~169
Highest book Sharpe reachable by adding sleeves of this quality and correlation, the Sharpe at a sleeve count, and the sleeves a target needs. Use it for portfolio construction, to see what adding strategies can and cannot do; it validates no single strategy. This verdict is about the series exactly as submitted. The service never saw the data source, its costs, survivorship, or any lookahead in how the series was built.
| Name | Type | Req | Description |
|---|---|---|---|
| average_pairwise_correlation | number | yes | Average correlation between sleeves, -1 to 1. |
| sleeve_sharpe | number | yes | Annualized Sharpe of one sleeve. |
| sleeves | integer | – | Sleeve count, to get that book's Sharpe. |
| target | number | – | Target book Sharpe, to get the sleeves it needs. |
| Name | Type | Req | Description |
|---|---|---|---|
| computed | string | – | – |
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
| note | string | – | – |
| receipt | – | – | – |
No examples provided.
validate_deflated_sharpe Validate deflated Sharpe ~341
Deflated Sharpe ratio: the probability (0 to 1) that one selected strategy's Sharpe beats the best Sharpe that luck alone would give across the variants tried, with the probabilistic Sharpe and that luck benchmark. Use it for the strategy you kept after a search, when you know how many variants were tried and how their Sharpe ratios spread; send the seven statistics or a return series, not both. With every variant's returns use validate_overfitting; to state luck as a trial count use validate_luck_trials; for a multiple-testing haircut use validate_haircut_sharpe. A deflated Sharpe or overfitting probability above or below any threshold is not admission to anything and is not a forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| cross_trial_sharpe_sd_annualized | number | – | Standard deviation of the annualized Sharpe across those trials. |
| effective_independent_trials | integer | – | Independent variants tried before choosing this one. |
| non_excess_kurtosis | number | – | Kurtosis, not excess kurtosis; 3 if Normal. |
| observations | integer | – | Number of return observations. |
| observed_sharpe_annualized | number | – | Annualized Sharpe as observed. |
| periods_per_year | number | – | Observations per year: 252 daily, 365 daily crypto, 52 weekly, 12 monthly. |
| returns | array | – | Periodic returns as fractions (0.01 is 1%), oldest first; replaces the Sharpe, observations, skew and kurtosis fields. |
| skew | number | – | Skewness of returns; 0 if Normal. |
| Name | Type | Req | Description |
|---|---|---|---|
| computed | string | – | – |
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
| note | string | – | – |
| receipt | – | – | – |
No examples provided.
validate_haircut_sharpe Haircut Sharpe ratio ~303
Haircut Sharpe ratio for multiple testing (Harvey and Liu, 2015): the Sharpe a single test would have needed once the number of tests is counted, by Bonferroni and for independent tests, and with the other tests' Sharpe ratios by Holm and BHY. Use it to report a Sharpe adjusted for the number of tests, as finance papers do; for a probability that the Sharpe is real, use validate_deflated_sharpe. A deflated Sharpe or overfitting probability above or below any threshold is not admission to anything and is not a forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| autocorrelation | number | – | First-order autocorrelation of the returns, -1 to 1; default 0. Corrects the annualized Sharpe as Lo (2002). |
| observations | integer | yes | Number of return observations behind the Sharpe ratio. |
| observed_sharpe_annualized | number | yes | Annualized Sharpe as observed. |
| other_sharpe_ratios_annualized | array | – | Annualized Sharpe ratios of the other tests, over the same observations; adds the Holm and BHY haircuts. |
| periods_per_year | number | yes | Observations per year: 252 daily, 365 daily crypto, 52 weekly, 12 monthly. |
| tests | integer | – | Total tests run, this one included; gives the Bonferroni and independent-test haircuts. |
| Name | Type | Req | Description |
|---|---|---|---|
| computed | string | – | – |
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
| note | string | – | – |
| receipt | – | – | – |
No examples provided.
validate_luck_trials Luck-equivalent trials ~286
How many skill-less strategies a search would have had to try for its best to reach this Sharpe by luck, and, with a trial count, the chance that it did. Calibrated by Monte Carlo. Use it to state luck as a count ("as good as the best of N random tries") or to test a result against the trials actually run; for a probability that the Sharpe is real, use validate_deflated_sharpe. A deflated Sharpe or overfitting probability above or below any threshold is not admission to anything and is not a forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| autocorrelation | number | – | First-order autocorrelation of the returns, -1 to 1; default 0. Corrects the annualized Sharpe as Lo (2002). |
| effective_independent_trials | integer | – | Independent trials tried; adds the chance that the best of them reached this Sharpe by luck. |
| observations | integer | yes | Number of return observations behind the Sharpe ratio. |
| observed_sharpe_annualized | number | yes | Annualized Sharpe as observed. |
| periods_per_year | number | yes | Observations per year: 252 daily, 365 daily crypto, 52 weekly, 12 monthly. |
| skew | number | – | Skewness of the returns; below -0.5 the reading warns that the counts are too generous. |
| Name | Type | Req | Description |
|---|---|---|---|
| computed | string | – | – |
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
| note | string | – | – |
| receipt | – | – | – |
No examples provided.
validate_overfitting Validate overfitting (CSCV) ~176
Probability of backtest overfitting (0 to 1) by CSCV: how often the variant that is best in sample falls below the median out of sample. Use it when you have every variant's returns as a matrix (periods by variants); with summary statistics only, use validate_deflated_sharpe. A deflated Sharpe or overfitting probability above or below any threshold is not admission to anything and is not a forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| matrix | array | yes | Returns as fractions: one row per period, one column per variant. |
| max_combinations | integer | – | Most splits evaluated, up to 2000 (default). |
| n_splits | integer | – | Even number of blocks, at least 2; default 16. |
| seed | number | – | Sampling seed; default 42. |
| Name | Type | Req | Description |
|---|---|---|---|
| computed | string | – | – |
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
| note | string | – | – |
| receipt | – | – | – |
No examples provided.
validate_paper_evidence Validate paper evidence ~112
Whether a paper or simulated performance record meets canli.paper-evidence.v0, with each failure's JSON pointer. Use it on a record document before publishing or relying on it: it checks structure and required disclosures, not whether the returns are good. This verdict is about the series exactly as submitted. The service never saw the data source, its costs, survivorship, or any lookahead in how the series was built.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | A canli.paper-evidence.v0 record. |
| Name | Type | Req | Description |
|---|---|---|---|
| computed | string | – | – |
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
| note | string | – | – |
| receipt | – | – | – |
No examples provided.
validate_track_record Minimum track record length ~262
Minimum track record length, in observations and years, for an observed Sharpe to beat a benchmark at a confidence level, and with observations, the record's probabilistic Sharpe so far. Use it for a live or paper record: how long it must run before its Sharpe is evidence. To size a backtest against the number of trials, use validate_backtest_length. A deflated Sharpe or overfitting probability above or below any threshold is not admission to anything and is not a forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| benchmark_sharpe_annualized | number | – | Annualized Sharpe to beat; default 0. |
| confidence | number | – | Between 0 and 1; default 0.95. |
| non_excess_kurtosis | number | yes | Kurtosis, not excess kurtosis; 3 if Normal. |
| observations | integer | – | Record length so far, to get its probabilistic Sharpe. |
| observed_sharpe_annualized | number | yes | Annualized Sharpe as observed. |
| periods_per_year | number | yes | Observations per year: 252 daily, 365 daily crypto, 52 weekly, 12 monthly. |
| skew | number | yes | Skewness of returns; 0 if Normal. |
| Name | Type | Req | Description |
|---|---|---|---|
| computed | string | – | – |
| data | object | – | – |
| error | – | – | – |
| limits | array | – | – |
| note | string | – | – |
| receipt | – | – | – |
No examples provided.
verify_receipt Verify a receipt ~150
Check a validation receipt's Ed25519 signature offline against the canlicapital.com public key bundled in this package, that its output hashes to its output_sha256, and that its content hashes to its id. Send an id to fetch the receipt first, or a receipt already fetched. The receipt is content-hashed, reproducible from the open-source core it names, and signed with Ed25519 by a key published at https://canlicapital.com/.well-known/canli-receipt-keys.json.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Receipt id from a validation result. |
| receipt | object | – | A receipt as get_receipt returns it (its data), to verify without fetching it. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | – | – | – |
| error | – | – | – |
| key_id | string|null | – | – |
| meaning | string | – | – |
| receipt_id | string|null | – | – |
| valid | boolean | – | – |
No examples provided.
What is the Canli Validation MCP server?
Canli Validation is an MCP server listed in the public MCP registry as io.github.arhancanli/canli-validation-mcp. Deflated Sharpe and PBO checks. A verdict is not admission to anything and is not a forecast. This page covers its npm package (canli-validation-mcp).
Is the Canli Validation MCP server safe to use?
Canli Validation scores 81 out of 100 on VerifyMCP. 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 Validation MCP server expose?
Canli Validation exposes 14 tools: get_key, validate_deflated_sharpe, validate_overfitting, validate_paper_evidence, validate_breadth, and 9 more. Their descriptions and schemas cost roughly 2,997 tokens of context every time the server is loaded.
Is the Canli Validation MCP server still maintained?
Canli Validation is still listed as active in the MCP registry. We last reached this channel on 27 September 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 Validation MCP server under?
Canli Validation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.