# FINOS MCP - FDC3 (community) (pypi · finos-mcp-fdc3)

Read-only MCP for FDC3 intents, context schemas and intent suggestions. Independent project.

- Trust score: 77/100 (medium)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `finos-mcp-fdc3`: 77/100 (this document), [markdown](https://verifymcp.io/servers/vardhjain-finos-mcp-fdc3/finos-mcp-fdc3.md), [page](https://verifymcp.io/servers/vardhjain-finos-mcp-fdc3/finos-mcp-fdc3)

## Channel facts

- Registry: `pypi`
- Package: `finos-mcp-fdc3`
- Version: `0.3.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 35 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to vardhjain/finos-mcp).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 8 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 38/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 587 tokens (~53/item across 11 items; 9 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add vardhjain-finos-mcp-fdc3 -- uvx finos-mcp-fdc3
```

### Cursor

```json
{
  "mcpServers": {
    "vardhjain-finos-mcp-fdc3": {
      "command": "uvx",
      "args": [
        "finos-mcp-fdc3"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vardhjain-finos-mcp-fdc3": {
      "command": "uvx",
      "args": [
        "finos-mcp-fdc3"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add vardhjain-finos-mcp-fdc3 -- uvx finos-mcp-fdc3
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vardhjain-finos-mcp-fdc3": {
      "type": "local",
      "command": [
        "uvx",
        "finos-mcp-fdc3"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vardhjain-finos-mcp-fdc3 --command uvx --arg finos-mcp-fdc3
```

### Hermes

```yaml
mcp_servers:
  vardhjain-finos-mcp-fdc3:
    command: "uvx"
    args: ["finos-mcp-fdc3"]
```

### Netclaw

```json
{
  "McpServers": {
    "vardhjain-finos-mcp-fdc3": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "finos-mcp-fdc3"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add vardhjain-finos-mcp-fdc3 -t stdio -c uvx -a finos-mcp-fdc3
```

### Other

```json
{
  "mcpServers": {
    "vardhjain-finos-mcp-fdc3": {
      "command": "uvx",
      "args": [
        "finos-mcp-fdc3"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 77, +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.

### 2026-11-03 (score 76, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-10-29 (score 73, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 58)

First indexed and scored.

## MCP tools (9)

### `list_intents` (~65 tokens)

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).

Input parameters:

- `context_type`
- `include_deprecated` (boolean)

Output parameters:

- `fdc3_version`
- `intents` (array)

### `get_intent` (~50 tokens)

Get one intent by name (case-insensitive): accepted contexts, result type, description,
deprecation status, and the fdc3:// resource holding its reference documentation.

Input parameters:

- `name` (string, required)

Output parameters:

- `citation_uri` (string)
- `contexts` (array)
- `deprecated` (boolean)
- `description` (string)
- `doc_path` (string)
- `name` (string)
- `result`
- `since`
- `standard` (boolean)
- `title` (string)

### `list_context_types` (~46 tokens)

List the FDC3 context types (fdc3.instrument, fdc3.contact, ...), whether each is
experimental, and which intents accept it.

Input parameters:

- `experimental`

Output parameters:

- `context_types` (array)
- `fdc3_version`

### `get_context_schema` (~56 tokens)

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.

Input parameters:

- `type` (string, required)

Output parameters:

- `example`
- `json_schema` (object): The vendored JSON Schema document.
- `properties` (array)
- `required` (array)
- `schema_id`
- `schema_uri` (string)
- `title` (string)
- `type` (string)

### `validate_context` (~67 tokens)

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, ...).

Input parameters:

- `context` (object, required)
- `type`

Output parameters:

- `format_detected`
- `issues` (array)
- `stats` (object)
- `type`
- `valid` (boolean)
- `validator` (string)
- `warnings` (array)

### `suggest_intent` (~81 tokens)

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.

Input parameters:

- `context`
- `context_type`
- `goal`

Output parameters:

- `context_type`
- `detected_by` (string)
- `suggestions` (array)
- `validation`

### `find_intents_by_context` (~44 tokens)

FDC3-API-style alias of list_intents(context_type=...): the intents that accept a
context type.

Input parameters:

- `context_type` (string, required)

Output parameters:

- `fdc3_version`
- `intents` (array)

### `search_intents` (~31 tokens)

Keyword search over intent names and descriptions.

Input parameters:

- `k` (integer)
- `query` (string, required)

Output parameters:

- `result` (array)

### `server_info` (~25 tokens)

Describe this server: standard version, upstream provenance, exposed counts, latency, policy.

Output parameters:

- `counts` (object)
- `latency` (object)
- `name` (string)
- `policy` (object)
- `read_only` (boolean)
- `resources` (array)
- `standard` (string)
- `standard_version`
- `tools` (array)
- `upstream_commit`
- `upstream_ref`
- `upstream_repo`
- `version` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/vardhjain-finos-mcp-fdc3/finos-mcp-fdc3#diagnostics

## Score history

- 2026-11-04: 77
- 2026-11-03: 76
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 58
- 2026-10-27: 58
- 2026-10-26: 58

## Common questions

### 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.

## Links

- PyPI project: https://pypi.org/project/finos-mcp-fdc3/
- Socket report: https://socket.dev/pypi/package/finos-mcp-fdc3
- Repository: https://github.com/vardhjain/finos-mcp
- Website: https://vardhjain.github.io/finos-mcp/
- Changelog RSS feed: https://verifymcp.io/servers/vardhjain-finos-mcp-fdc3/finos-mcp-fdc3.xml
- Changelog JSON feed: https://verifymcp.io/servers/vardhjain-finos-mcp-fdc3/finos-mcp-fdc3.json
- HTML version of this page: https://verifymcp.io/servers/vardhjain-finos-mcp-fdc3/finos-mcp-fdc3