Skip to content

About

Financial Services Interest Group

Resources

Code of conduct

Contributing

Security policy

Stars

62 stars

Watchers

14 watching

Forks

Latest commit

 

History

11 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

MCP Financial Services Interest Group (FSIG)

The MCP Financial Services Interest Group (FSIG) is a collaborative community advancing the Model Context Protocol (MCP) for use in regulated financial services environments.

Charter: modelcontextprotocol.io/community/interest-groups/financial-services — mission, scope, leadership, membership, operations, and discussion topics. Calendar: MCP Meetings — Finance Meeting notes & agendas: FSIG Meeting Notes Discord: #financial-services-ig

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 for the full scope, leadership, membership, and current discussion topics.

Related Working Groups

FSIG members are actively contributing to these MCP working groups and experimental extensions:

Meetings

Cadence: Every two weeks · Time: 16:00–17:00 London (BST/GMT) · Duration: 60 minutes · Format: Virtual

See the calendar for the next meeting and the meeting notes doc for agendas. Meeting requirements — open attendance, advance agendas, and public notes — follow MCP group governance. Each meeting opens with an antitrust reminder.

Current Focus Areas

  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
├── CONTRIBUTING.md   # How to contribute
├── extensions/       # MCP extension specifications and examples
└── docs/             # Guides, whitepapers, and documentation

How to Participate

Anyone can participate — no approval or membership is required:

Leadership and membership are listed in the charter.

Contributing

We welcome contributions of all kinds. Please review:

Related Resources

About

Financial Services Interest Group

Resources

Code of conduct

Contributing

Security policy

Stars

62 stars

Watchers

14 watching

Forks

Releases

Packages

Used by

Contributors