Claude Financial Services: what the public plugins actually provide
Financial Services quickstart: review a synthetic reconciliation
Install one documented plugin and define a checkable draft without connecting real financial records.
What you will learn
- Prepare input with a known answer
- Check configuration before installation
- Accept, stop or restore
Before you start
- Command-line and JSON familiarity
- A disposable workspace with synthetic financial records
A proposed learning project turns validated requests into reviewable records without giving documents control of routing.
Key takeaways
- Known answers make the first run auditable.
- The inspected MCP JSON fails preflight.
- Cancel unexpected access requests.
Prepare input with a known answer
Create two tiny tables with the same invoice identifier but different totals. Include one deliberately missing date and keep a private answer sheet. This separates arithmetic or missing-data errors from questions about unfamiliar business context.
The first prompt should request a draft discrepancy table, source-row references and unanswered questions. Require it to leave the missing date unknown. Supplying imaginary client names avoids exposing customer material during setup.
Check configuration before installation
The README adds the marketplace, financial-analysis and gl-reconciler. However, the pinned financial-analysis/.mcp.json fails JSON parsing near the box entry. An independent raw-source fetch matched the capture. Stop at this preflight failure; do not describe this exact configuration as install-ready.
Use a separately reviewed corrected upstream revision before following the installation example. Marketplace installation can fetch newer files than 574ed36, so record that revision and inspect the difference. We did not install the host or test a repaired configuration.
Accept, stop or restore
Accept a draft only if its numbers match your answer sheet, each discrepancy identifies its input row and the absent date stays absent. A request to post a correction exceeds the trial even if the suggested correction is numerically right.
Keep the original workspace and plugin settings available for restoration. If the host requests an unexpected connector or permission, cancel that action, inspect the requested scope and repeat with synthetic local inputs before reconnecting anything.
Decision guide
| Criterion | Option A | Option B |
|---|---|---|
| Best when | You need predictable behavior and easy auditing | You need adaptive optimization and have reliable telemetry |
| Main risk | May leave performance on the table | Can become difficult to explain or debug |
Implementation steps
- 1
Create the two tables and answer sheet.
- 2
Parse configuration; stop if invalid, as in this pinned revision.
- 3
Only after a reviewed correction, compare the draft with the expected discrepancy.
Copy-ready example
python -m json.tool plugins/vertical-plugins/financial-analysis/.mcp.json
# STOP on failure. Only after reviewing a corrected revision:
claude plugin marketplace add anthropics/financial-services
claude plugin install financial-analysis@claude-for-financial-services
claude plugin install gl-reconciler@claude-for-financial-servicesFrequently asked questions
Must every connector be authorized?
No. Start with the smallest task and authorize only sources it actually needs.
Can I install this exact revision unchanged?
The inspected MCP JSON is invalid. Review a corrected revision before installation; this article does not claim a successful repaired run.
Sources
- Financial Services / README.mdSource checked 2026-09-23
- Financial Services / plugins/vertical-plugins/financial-analysis/.mcp.jsonSource checked 2026-09-23