FINOS MCP - Common Domain Model (community)
PYPI · FINOS-MCP-CDM
Read-only MCP for FINOS CDM 7.8.0 types and trade JSON validation. Independent project.
Available components
Last scanned (1 day ago)
Scores higher than 69% of PyPI 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
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 35 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 vardhjain/finos-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 8 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability39
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 712 tokens (~71/item across 10 items; 9 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 9 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 current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 58
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 4 Nov 2026 · Analysed pypi/finos-mcp-cdm@0.3.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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | vardhjain/finos-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/vardhjain/finos-mcp/.github/workflows/release.yml@refs/tags/v0.3.2 |
| Rekor log index | 3481209171 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8326cd425ffd3dcdf8056b73d7706cf330f373cd3ee8bc5dceed1d227fcccc8c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| No linked repository | 1 |
| 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_type ~65
Describe one CDM type by name (TradeState) or fully qualified name (cdm.event.common.TradeState): every field with its type and cardinality, choice alternatives, which types reference it, and the schema resource to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | – | For choice types: the alternative type names. |
| description | – | yes | – |
| extends | – | yes | – |
| fields | array | yes | – |
| kind | string | yes | – |
| name | string | yes | – |
| namespace | string | yes | – |
| root_type | boolean | yes | – |
| schema_filename | string | yes | – |
| schema_uri | string | yes | – |
| used_by | array | yes | – |
No examples provided.
explain_event ~82
Explain a CDM BusinessEvent. Pass the event JSON to read its qualifier, instruction kinds, before/after trade states and the products involved; or pass a qualifier name (Execution, Termination, ...) to get the Qualify_* rule from the CDM sources and a sample that exercises it.
| Name | Type | Req | Description |
|---|---|---|---|
| event | – | – | – |
| qualifier | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| after_products | array | – | – |
| after_trade_count | integer | – | – |
| before_trade_count | integer | – | – |
| format_detected | – | – | – |
| instruction_types | array | – | – |
| notes | array | – | – |
| qualifier | – | yes | – |
| qualify_function | – | yes | – |
| sample_uris | array | – | – |
No examples provided.
get_sample ~50
Fetch one vendored sample document by name (see list_samples), e.g. a Rune-format Execution BusinessEvent for an interest-rate swap, to use as a template.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| citation_uri | string | yes | – |
| format | string | yes | – |
| json_document | object | yes | – |
| name | string | yes | – |
| root_type | – | yes | – |
No examples provided.
list_products ~70
Catalogue of product types: the product template types (NonTransferableProduct, TransferableProduct, TradableProduct, EconomicTerms, Payout) and every Payout alternative (InterestRatePayout, CreditDefaultPayout, OptionPayout, ...), with the vendored samples that use each.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cdm_version | string | yes | – |
| entries | array | yes | – |
No examples provided.
list_samples ~41
List the vendored sample documents (Rune-format from CDM 7.8.0, legacy from 6.30.0).
| Name | Type | Req | Description |
|---|---|---|---|
| format | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| samples | array | yes | – |
No examples provided.
list_types ~82
List CDM types. Filter by namespace prefix (cdm.product), kind (type, enum, choice, meta) or root types only (the 16 top-level document types such as TradeState).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | – |
| namespace | – | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| root_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| page | integer | yes | – |
| page_size | integer | yes | – |
| total | integer | yes | – |
No examples provided.
search_types ~40
Keyword search over CDM type names and descriptions (e.g. 'floating rate payout').
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
server_info ~25
Describe this server: standard version, upstream provenance, exposed counts, latency, policy.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | – | – |
| latency | object | – | – |
| name | string | yes | – |
| policy | object | – | – |
| read_only | boolean | – | – |
| resources | array | – | – |
| standard | string | yes | – |
| standard_version | – | – | – |
| tools | array | – | – |
| upstream_commit | – | – | – |
| upstream_ref | – | – | – |
| upstream_repo | – | – | – |
| version | string | yes | – |
No examples provided.
validate_object ~144
Validate a CDM JSON object against the published schema. The format (Rune with '@type'/'@key'/'@ref' keys, or legacy 'value'/'meta' wrappers) is detected unless given. The type comes from '@type' or the type argument (e.g. TradeState). Use schema_version='6.30.0' for legacy documents produced by CDM 6. Every issue carries the JSON path in your document and a kind (required, cardinality, type, enum, ...).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| object | object | yes | – |
| schema_version | – | – | – |
| type | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| format_detected | – | – | – |
| issues | array | – | – |
| stats | object | – | – |
| type | – | – | – |
| valid | boolean | yes | – |
| validator | string | yes | – |
| warnings | array | – | – |
No examples provided.
How do I install the FINOS MCP - Common Domain Model (community) server?
FINOS MCP - Common Domain Model (community) runs locally as a PyPI package, launched with uvx finos-mcp-cdm. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · finos-mcp-cdm
claude mcp add vardhjain-finos-mcp-cdm -- uvx finos-mcp-cdm
What is the FINOS MCP - Common Domain Model (community) server?
FINOS MCP - Common Domain Model (community) is listed in the public MCP registry as io.github.vardhjain/finos-mcp-cdm. Read-only MCP for FINOS CDM 7.8.0 types and trade JSON validation. Independent project. This page covers its PyPI package (finos-mcp-cdm).
Is the FINOS MCP - Common Domain Model (community) server safe to use?
FINOS MCP - Common Domain Model (community) scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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.
What tools does the FINOS MCP - Common Domain Model (community) server expose?
FINOS MCP - Common Domain Model (community) exposes 9 tools: describe_type, list_types, list_products, validate_object, explain_event, and 4 more. Their descriptions and schemas cost roughly 599 tokens of context every time the server is loaded.
Is the FINOS MCP - Common Domain Model (community) server still maintained?
FINOS MCP - Common Domain Model (community) is still listed as active in the MCP registry. We last reached this channel on 4 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 FINOS MCP - Common Domain Model (community) server under?
FINOS MCP - Common Domain Model (community) 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.