modelcontextprotocol/financial-services-interest-group
Watch
1
0
Fork
You've already forked financial-services-interest-group
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add FSIG repository structure (#1)

Browse source 
- Add README with mission, meeting info, and quick start guide
- Add CHARTER with scope and extension promotion strategy
- Add GOVERNANCE with decision-making model, roles, and members
- Add CONTRIBUTING guide referencing MCP standards
- Add CODEOWNERS for @modelcontextprotocol/ig-financial-services
This commit is contained in:
Sambhav Kothari 2025-10-01 20:29:58 +01:00 • committed by GitHub
commit 6b0dd7f13a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 450 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
.github/CODEOWNERS vendored Normal file
View file

@ -0,0 +1,5 @@
# CODEOWNERS for MCP Financial Services Interest Group
# These owners will be requested for review when someone opens a pull request.
# Default owners for everything in the repo
* @modelcontextprotocol/ig-financial-services

88
CHARTER.md Normal file
View file

@ -0,0 +1,88 @@
# FSIG Charter
This document defines the mission, scope, and strategic approach of the MCP Financial Services Interest Group (FSIG).
> **For governance details, roles, and current members, see [GOVERNANCE.md](./GOVERNANCE.md)**
## Mission & Scope
### Mission
The FSIG coordinates financial-industry stakeholders to:
- **Define and build** finance-specific MCP extensions (compliance/auditability, data lineage & provenance, guardrails & attestation, etc.)
- **Advocate for spec enhancements** when extensions aren't sufficient (via SEPs with core maintainer sponsorship)
- **Drive common standards** enabling interoperability across regulated institutions
- **Provide a neutral forum** to address regulatory and risk constraints with open technical solutions
### Scope
**In Scope:**
- Technical standards and protocols for financial services
- MCP extensions addressing compliance, security, and regulatory requirements
- Appropriate implementations of extensions for testing and validation
- Interoperability patterns and conformance testing
- Documentation and reference implementations
**Out of Scope:**
- Competitively sensitive topics (pricing, customer lists, market strategies, etc.)
- Non-technical business discussions
> **Note:** FSIG adheres to the [MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md). All participants must comply with antitrust guidelines.
## Extensions vs. Core Spec
### Extensions
**Extensions** are domain-specific additions that can be developed and iterated on within the FSIG to address financial services requirements. They allow us to:
- Develop solutions for real-world financial services scenarios
- Gather implementation experience and feedback
- Move quickly on specialized domain requirements
- Provide production-ready capabilities for financial institutions
Extensions are fully supported specifications developed and maintained within the FSIG repository. They may evolve based on implementation experience and feedback from the community.
### Relationship to Core Spec
FSIG extensions complement the core MCP specification rather than fragment it. When an extension demonstrates **broad applicability beyond financial services**, it becomes a candidate for promotion to the core MCP specification through:
1. **SEP (Spec Enhancement Proposal)** — A formal proposal documenting the extension, its rationale, and implementation experience
2. **Core Maintainer Sponsorship** — Support from MCP core maintainers who shepherd the proposal
3. **Community Consensus** — Agreement from the broader MCP community through the SEP review process
This pathway ensures that domain-specific innovations can eventually benefit the entire MCP ecosystem when appropriate.
### Proactive Promotion
The FSIG actively identifies extensions with broad applicability and assesses appetite for promotion to the core spec. The group serves as:
- **Real-world validation** — Providing implementation experience and use cases from regulated environments
- **Collective advocacy** — A coalition of contributors who can speak to the value and necessity of capabilities
- **SEP champions** — Subject matter experts who can shepherd proposals through the enhancement process
When an extension shows promise for broader adoption, maintainers will:
1. **Assess applicability** — Evaluate whether the extension solves problems beyond financial services
2. **Gauge community interest** — Discuss with other MCP groups and the broader community
3. **Build consensus** — Work with FSIG members to align on the promotion strategy
4. **Coordinate with liaison** — Engage with [David Soria Parra](https://github.com/dsp-ant) to pursue SEP sponsorship
This proactive approach ensures that valuable innovations developed for financial services can benefit the entire MCP ecosystem.
**Core Maintainer Liaison:** [David Soria Parra](https://github.com/dsp-ant) serves as our liaison to the core MCP maintainers for SEP sponsorship.
## Amendments
This charter may be amended by:
1. Proposal via GitHub Issue or pull request
2. Discussion in meetings and/or GitHub
3. Consensus approval from maintainers
4. Documentation of rationale in the PR or issue
Significant changes should be announced in Discord and allow for community input before finalization.
## Questions?
For questions about this charter, please:
- Ask in the `#financial-services-ig` Discord channel
- Open a GitHub Issue
- Contact the maintainers (see [GOVERNANCE.md](./GOVERNANCE.md))

101
CONTRIBUTING.md Normal file
View file

@ -0,0 +1,101 @@
# Contributing to FSIG
Thank you for your interest in contributing to the MCP Financial Services Interest Group!
## Quick Start
1. **Join the Community**
- Join the `#financial-services-ig` channel on [MCP Discord](https://discord.com/invite/6CSzBmMkjX)
- Introduce yourself and your interests
- Review recent [meeting notes](https://docs.google.com/document/d/18lj9jcdNnr4m9d1RovotEko5LTP_9vsRTuZdfg0Igmw/edit?tab=t.0)
2. **Understand the Scope**
- Read the [README](./README.md) for an overview
- Review the [CHARTER](./CHARTER.md) for mission and scope
- Check [GOVERNANCE](./GOVERNANCE.md) for roles and decision-making
3. **Start Contributing**
- Attend bi-weekly meetings (no approval needed!)
- Browse [open issues](https://github.com/modelcontextprotocol/financial-services-interest-group/issues)
- Open issues for new ideas or questions
- Submit PRs for extensions, documentation, or improvements
## General Guidelines
For general contribution guidelines, please follow the [MCP Contributing Guide](https://github.com/modelcontextprotocol/.github/blob/main/CONTRIBUTING.md).
### FSIG-Specific Considerations
**Antitrust Compliance:**
All contributions and discussions must comply with the [MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md).
**Do NOT discuss:**
- Pricing, costs, or margins
- Customer lists or strategies
- Market division or competitive coordination
- Confidential business information
**Focus on:**
- Technical standards and specifications
- Implementation approaches
- Interoperability patterns
- Documentation and testing
## Extension Development
When developing MCP extensions for financial services:
1. **Start with a Proposal**
- Open an issue describing the extension
- Discuss use cases and requirements
- Get feedback before implementation
2. **Follow MCP Standards**
- Align with the [MCP Specification](https://spec.modelcontextprotocol.io)
- Use standard MCP patterns and conventions
- Document deviations clearly
3. **Include Documentation & Examples**
- Clear README with purpose and usage
- Working examples demonstrating the extension
- Implementation notes and considerations
4. **Consider Broad Applicability**
- Could this extension benefit other domains?
- Is there potential for promotion to core spec?
- Document use cases beyond financial services
## Proposing Core Spec Enhancements
If you believe an extension should be promoted to the core MCP spec:
1. **Gather Implementation Experience** — Deploy in real scenarios and collect feedback
2. **Discuss with FSIG** — Present at a meeting and get consensus from maintainers
3. **Contact Core Maintainer Liaison** — Reach out to [David Soria Parra](https://github.com/dsp-ant)
4. **Draft SEP** — Follow the MCP SEP process with liaison support
See [CHARTER.md](./CHARTER.md#proactive-promotion) for more details.
## Communication Channels
- **Discord:** `#financial-services-ig` — Real-time chat and questions
- **GitHub Issues:** Proposals, bugs, and structured discussions
- **GitHub Discussions:** Longer-form conversations
- **Meetings:** Bi-weekly sync (see [README](./README.md#️-meetings))
## Recognition
Active contributors are recognized in [GOVERNANCE.md](./GOVERNANCE.md). After attending 2+ meetings or making substantive contributions, you can:
- Self-nominate by opening a PR
- Or a maintainer may add you
## Getting Help
- **Ask in Discord** — The `#financial-services-ig` channel is welcoming and responsive
- **Open an issue** — For specific questions or proposals
- **Attend a meeting** — Get face-time with maintainers and other contributors
- **Contact maintainers** — See [GOVERNANCE.md](./GOVERNANCE.md) for current maintainers
---
**Thank you for contributing to FSIG! Together we're making MCP more accessible and useful for financial services.** 🎉

157
GOVERNANCE.md Normal file
View file

@ -0,0 +1,157 @@
# FSIG Governance & Members
This document describes the governance model, roles, and current members of the MCP Financial Services Interest Group (FSIG).
## Governance Model
FSIG operates with a **lightweight, consensus-driven governance model**:
- **Decision-making:** Consensus among maintainers
- **Maintainer responsibilities:** Coordinate meetings, maintain repo hygiene, facilitate collaboration, review/merge PRs, make governance decisions
- **Transparency:** All decisions documented in meeting notes or GitHub issues
- **Open participation:** Anyone can contribute, attend meetings, and provide input
### Decision-Making Process
1. **Proposals** are raised via GitHub Issues or during meetings
2. **Discussion** happens in public channels (Discord, GitHub, meetings)
3. **Consensus** is reached when no maintainer objects (lazy consensus)
4. **Objections** trigger further discussion to find compromise or alternative approaches
5. **Documentation** of decisions happens in meeting notes or issue threads
For technical decisions, maintainers may defer to subject matter experts or request broader community input.
### Core Principles
1. **Open participation** — Anyone can contribute regardless of affiliation or background
2. **Transparent decisions** — All work happens in public with documented rationale
3. **Consensus-driven** — Decisions made by maintainer consensus with community input
4. **[Antitrust compliance](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md)** — Stay within technical scope and avoid competitive coordination
5. **Community-aligned** — Collaborate with other MCP groups and align with broader ecosystem goals
## Roles & Responsibilities
### Maintainers
Maintainers are trusted members who steward the FSIG's direction and operations.
**Responsibilities:**
- Review and merge pull requests
- Coordinate meetings and set agendas
- Maintain repository hygiene and organization
- Make governance decisions via consensus
- Enforce scope and conduct standards
- Mentor and support contributors
- Represent FSIG in broader MCP community
**Privileges:**
- Write access to the repository
- Voting rights on group decisions
- Ability to approve new maintainers
**Becoming a Maintainer:**
1. Demonstrate sustained contribution to the group (code, documentation, or leadership)
2. Nomination by an existing maintainer
3. Consensus approval from current maintainers
4. Repository access and onboarding to governance processes
### Active Contributors
Active Contributors are community members who regularly participate in FSIG activities.
**Characteristics:**
- Regularly participate in meetings or discussions
- Contribute to the codebase, documentation, or proposals
- Provide domain expertise and feedback
**Privileges:**
- Triage permissions to the repository
- Recognition in this document
- Voice in technical discussions
**Becoming an Active Contributor:**
- Simply start contributing! No formal approval needed
- Maintainers may grant triage permissions after sustained participation
- Self-nominate or be nominated by others for recognition
### Contributors
Anyone can contribute to FSIG by:
- Joining discussions in Discord or GitHub
- Attending meetings and providing feedback
- Opening issues for new ideas or problems
- Submitting pull requests
- Reviewing proposals and providing expertise
No approval or membership is required to contribute.
## Current Members
### Maintainers
Maintainers have review/merge permissions on the repository and voting rights on group decisions.
| Name | Organization | GitHub |
|------|-------------|---------|
| Sambhav Kothari | Bloomberg | [@sambhav](https://github.com/sambhav) |
### Active Contributors
Contributors who regularly participate in meetings, discussions, or contribute to the codebase:
| Name | Organization | GitHub |
|------|-------------|---------|
| Xin Fu | Bloomberg | [@imfing](https://github.com/imfing) |
| Kengo Arao | Bloomberg | [@KengoA](https://github.com/KengoA) |
_To add yourself to this list, open a PR after attending at least 2 meetings or making substantive contributions._
### Emeritus Maintainers
Former maintainers who have stepped down but made significant contributions:
_None yet._
## Meetings
All FSIG meetings must include:
1. **Antitrust Reminder** — Brief reminder at the start that we must comply with the [MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md)
2. **Published Agenda** — Posted at least 48 hours prior in Discord
3. **Public Notes** — Meeting notes with decisions and action items published after each meeting
4. **Open Attendance** — All interested participants welcome, no approval required
Meeting notes are maintained in a [shared Google Doc](https://docs.google.com/document/d/18lj9jcdNnr4m9d1RovotEko5LTP_9vsRTuZdfg0Igmw/edit?tab=t.0).
## Antitrust Compliance
The FSIG strictly adheres to the [MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md).
**Prohibited Topics:**
- Pricing strategies, costs, or margins
- Customer lists or market segmentation
- Competitive strategies or market division
- Confidential business information
- Any coordination that could be construed as anti-competitive
**Enforcement:**
- Maintainers are responsible for keeping discussions on track
- Participants who repeatedly violate the policy may be excluded from meetings
- Any concerns should be raised immediately with maintainers
## Amendments
This governance document may be amended by:
1. Proposal via GitHub Issue or pull request
2. Discussion in meetings and/or GitHub
3. Consensus approval from maintainers
4. Documentation of rationale in the PR or issue
Significant changes should be announced in Discord and allow for community input before finalization.
## Questions?
For questions about FSIG governance, please:
- Ask in the `#financial-services-ig` Discord channel
- Open a GitHub Issue
- Contact the maintainers listed above

99
README.md Normal file
View file

@ -0,0 +1,99 @@
# MCP Financial Services Interest Group (FSIG)
Welcome to the **MCP Financial Services Interest Group (FSIG)** — a collaborative community focused on advancing the [Model Context Protocol (MCP)](https://modelcontextprotocol.io) for use in regulated financial services environments.
## 🎯 Mission
The FSIG coordinates financial-industry stakeholders to:
- **Define and build** finance-specific MCP extensions (compliance/auditability, data lineage & provenance, guardrails & attestation, etc.)
- **Advocate for spec enhancements** when extensions aren't sufficient (via SEPs with core maintainer sponsorship)
- **Drive common standards** enabling interoperability across regulated institutions
- **Provide a neutral forum** to address regulatory and risk constraints with open technical solutions
> **📜 See the [CHARTER](./CHARTER.md) for detailed governance, scope, and processes.**
## 💬 Communication
- **Primary Channel:** [MCP Discord](https://discord.com/invite/6CSzBmMkjX) → `#financial-services-ig`
- **Meetings:** Bi-weekly, 60 minutes
- Meeting agendas posted in Discord ≥48 hours in advance
- **Work Tracking:** GitHub Issues and Discussions in this repository
- **Reporting:** Quarterly updates to the broader MCP community
## 🗓️ Meetings
**Cadence:** Every two weeks (starting October 9th, 2025)
**Time:** 4-5pm London (BST/GMT)
**Duration:** 60 minutes
**Format:** Virtual
**Zoom Link:** [Join FSIG Bi-weekly Meeting](https://bloomberg.zoom.us/j/94297371315?pwd=v3WLhJrPEafnbZUFUMg7R19qsAYlMJ.1)
> **Note:** See the [agenda doc](https://docs.google.com/document/d/18lj9jcdNnr4m9d1RovotEko5LTP_9vsRTuZdfg0Igmw/edit?tab=t.0) for accurate next meeting times.
All meetings include:
- Brief [antitrust reminder](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md) at start
- Published agenda (48h prior)
- Public notes with decisions and action items
- Open attendance for all interested participants
**Meeting Notes & Agendas:** [FSIG Meeting Notes](https://docs.google.com/document/d/18lj9jcdNnr4m9d1RovotEko5LTP_9vsRTuZdfg0Igmw/edit?tab=t.0)
## 👥 How to Participate
We welcome participation from anyone interested in MCP for financial services!
- **Join** the `#financial-services-ig` channel on [MCP Discord](https://discord.com/invite/6CSzBmMkjX)
- **Attend** bi-weekly meetings (no approval needed!)
- **Contribute** by opening issues, submitting PRs, or providing feedback
- **Review** the [CONTRIBUTING guide](./CONTRIBUTING.md) for detailed guidelines
_See [GOVERNANCE.md](./GOVERNANCE.md) for current members, roles, and how to become a maintainer._
## 🚀 Current Focus Areas
Our initial work focuses on:
1. **Regulatory Audit & Attestation** — Portable, verifiable event/claim models
2. **Data Lineage & Citation** — Provenance, consent metadata, and source attribution
3. **Guardrails & Security** — Verification frameworks and cryptographic attestations
4. **Policy Enforcement** — Declarative policies for tool usage and data handling
## 📂 Repository Structure
```
/
├── README.md # This file - Quick start guide
├── CHARTER.md # Mission, scope, and extension strategy
├── GOVERNANCE.md # Governance model, roles, and members
├── CONTRIBUTING.md # Contribution guidelines
├── extensions/ # MCP extension specifications and examples
├── docs/ # Guides, whitepapers, and documentation
└── templates/ # Templates for extensions and SEPs
```
## 🤝 Contributing
We welcome contributions of all kinds! Please review:
- **[CONTRIBUTING.md](./CONTRIBUTING.md)** — Detailed contribution guidelines
- **[MCP Code of Conduct](https://github.com/modelcontextprotocol/.github/blob/main/CODE_OF_CONDUCT.md)** — Community standards
- **[MCP Antitrust Policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/ANTITRUST.md)** — Required compliance
**Quick Start:**
- Open an issue to propose ideas or report problems
- Submit a PR for extensions, documentation, or improvements
- Join discussions in Discord or GitHub
## 🔗 Related Resources
- [Model Context Protocol](https://modelcontextprotocol.io)
- [MCP Specification](https://spec.modelcontextprotocol.io)
- [MCP GitHub Organization](https://github.com/modelcontextprotocol)
- [MCP Discord Community](https://discord.com/invite/6CSzBmMkjX)
## 📞 Contact
- **Discord:** `#financial-services-ig` channel
- **GitHub Issues:** For proposals, questions, and discussions