FINOS MCP - FDC3 (community)
PYPI · FINOS-MCP-FDC3
Read-only MCP for FDC3 intents, context schemas and intent suggestions. Independent project.
Available components
Last scanned (23 hours ago)
Scores higher than 74% of PyPI servers
Category Developer Tools
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 Usability38
- 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 587 tokens (~53/item across 11 items; 9 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +3
- Stability: unverified → 0.27 ▲ functional
- 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-fdc3@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 | 3481210073 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:985c4cc17f74599141cb4f0aad1af6589ec727c215fe703b1f23da7dd4c620bf |
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 →
find_intents_by_context ~44
FDC3-API-style alias of list_intents(context_type=...): the intents that accept a context type.
| Name | Type | Req | Description |
|---|---|---|---|
| context_type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| fdc3_version | – | yes | – |
| intents | array | yes | – |
No examples provided.
get_context_schema ~56
Get the JSON Schema for a context type (by type such as fdc3.instrument, or by name such as Instrument), with a summary of required and optional properties and the standard example.
| Name | Type | Req | Description |
|---|---|---|---|
| type | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| example | – | – | – |
| json_schema | object | yes | The vendored JSON Schema document. |
| properties | array | yes | – |
| required | array | yes | – |
| schema_id | – | yes | – |
| schema_uri | string | yes | – |
| title | string | yes | – |
| type | string | yes | – |
No examples provided.
get_intent ~50
Get one intent by name (case-insensitive): accepted contexts, result type, description, deprecation status, and the fdc3:// resource holding its reference documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| citation_uri | string | – | – |
| contexts | array | – | – |
| deprecated | boolean | – | – |
| description | string | – | – |
| doc_path | string | yes | – |
| name | string | yes | – |
| result | – | – | – |
| since | – | – | – |
| standard | boolean | – | – |
| title | string | yes | – |
No examples provided.
list_context_types ~46
List the FDC3 context types (fdc3.instrument, fdc3.contact, ...), whether each is experimental, and which intents accept it.
| Name | Type | Req | Description |
|---|---|---|---|
| experimental | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context_types | array | yes | – |
| fdc3_version | – | yes | – |
No examples provided.
list_intents ~65
List the standard FDC3 intents with the context types each accepts and the result type it returns, if any. Filter to intents that accept one context_type (e.g. fdc3.instrument).
| Name | Type | Req | Description |
|---|---|---|---|
| context_type | – | – | – |
| include_deprecated | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| fdc3_version | – | yes | – |
| intents | array | yes | – |
No examples provided.
search_intents ~31
Keyword search over intent names and descriptions.
| 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.
suggest_intent ~81
Suggest which intents to raise for a context. Pass the context object (its `type` is used; if missing or unknown the object is matched structurally against every schema), or a context_type. An optional goal ("show a price chart") re-ranks by description.
| Name | Type | Req | Description |
|---|---|---|---|
| context | – | – | – |
| context_type | – | – | – |
| goal | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| context_type | – | yes | – |
| detected_by | string | yes | – |
| suggestions | array | yes | – |
| validation | – | – | – |
No examples provided.
validate_context ~67
Validate a context object against its FDC3 schema. The type is read from the object's `type` field unless given explicitly. Issues carry a JSON path and a kind (required, type, enum, unknown_field, ...).
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | yes | – |
| 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 - FDC3 (community) server?
FINOS MCP - FDC3 (community) runs locally as a PyPI package, launched with uvx finos-mcp-fdc3. 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-fdc3
claude mcp add vardhjain-finos-mcp-fdc3 -- uvx finos-mcp-fdc3
What is the FINOS MCP - FDC3 (community) server?
FINOS MCP - FDC3 (community) is listed in the public MCP registry as io.github.vardhjain/finos-mcp-fdc3. Read-only MCP for FDC3 intents, context schemas and intent suggestions. Independent project. This page covers its PyPI package (finos-mcp-fdc3).
Is the FINOS MCP - FDC3 (community) server safe to use?
FINOS MCP - FDC3 (community) scores 77 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 - FDC3 (community) server expose?
FINOS MCP - FDC3 (community) exposes 9 tools: list_intents, get_intent, list_context_types, get_context_schema, validate_context, and 4 more. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.
Is the FINOS MCP - FDC3 (community) server still maintained?
FINOS MCP - FDC3 (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 - FDC3 (community) server under?
FINOS MCP - FDC3 (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.