financial-services-interest-group

The FSIG MCP server is a community-driven development environment for extending the Model Context Protocol (MCP) to financial services use cases. It focuses on regulatory auditability, data lineage, guardrails, attestation, and policy enforcement within regulated environments. The repository documents extensions, governance, and best practices for building interoperable MCP components that address compliance, provenance, and security needs. To use the server and its tools, follow the repository's CONTRIBUTING and extension guidelines to explore available extensions, sample models, and policy definitions. When you start any server component, you should connect to the MCP ecosystem endpoints and reference the extension specifications to ensure compatibility and verifiability of events and attestations across participants.

Prerequisites:

• Ensure you have a working environment with Docker installed, or a compatible runtime for your chosen deployment method (e.g., Node.js, Python) if you plan to run local tooling.
• Familiarize yourself with MCP concepts: extensions, attestations, provenance, and governance documents.

Step-by-step installation (recommended generic approach):

1. Clone the repository: git clone https://github.com/modelcontextprotocol/modelcontextprotocol-financial-services-interest-group.git cd modelcontextprotocol-financial-services-interest-group
2. Review governance and contribution guidelines:
   • Open CONTRIBUTING.md
3. If using Docker (recommended for isolated runs):
   • Build or pull an appropriate image that contains FSIG MCP components (see extensions/ and docs/ for references)
   • Run a container with required environment variables (example placeholder): docker run -i --env FSIG_MODE=dev --env MCP_ENDPOINT=https://mcp.example.org modelcontextprotocol/fsig-image:latest
4. If running locally from source (Node/Python/other runtime will vary):
   • Install dependencies (per language in use): npm install or python -m pip install -r requirements.txt
   • Start the server component as described in the relevant extension or docs (for example: node path/to/server.js or uvx path/to/app.py)
5. Connect to the MCP network:
   • Use the provided endpoints and follow the extension guidelines to register your component, publish events, and verify attestations.
6. Validate with sample data:
   • Load sample events and provenance records from extensions/sample-data and run through the verification pipeline described in the docs.

Notes and tips:

• This FSIG repo focuses on regulatory auditability, data lineage, guardrails, and policy enforcement. When configuring environments, ensure that time synchronization and cryptographic keys are managed securely to support attestation verification.
• Review CHARTER.md, GOVERNANCE.md, and CONTRIBUTING.md to understand governance, roles, and contribution workflows before proposing extensions.
• If issues arise, leverage the MCP Discord channel #financial-services-ig or GitHub Issues to discuss extension needs, compatibility, and regulatory alignment.
• Environment variables you may encounter include flags for mode (development/production), MCP endpoints, and credentials for provenance/attestation services. Replace placeholders with your actual values in a secure manner.