Skip to content

Add eu-finreg plugin — EU financial regulation specialist - #69

Closed
Velvoite wants to merge 1 commit into
anthropics:mainfrom
velvoite-eu:add-eu-finreg-plugin
Closed

Add eu-finreg plugin — EU financial regulation specialist#69
Velvoite wants to merge 1 commit into
anthropics:mainfrom
velvoite-eu:add-eu-finreg-plugin

Conversation

@Velvoite

Copy link
Copy Markdown

Summary

Adds the eu-finreg plugin under external_plugins/ — the EU financial regulation specialist in the claude-for-legal ecosystem. Built and maintained by Silly Pilot Oy.

It complements regulatory-legal for legal and compliance teams at EU-regulated financial institutions: payment institutions, CASPs, investment firms, AIFMs, e-money institutions, insurers, and credit institutions.

regulatory-legal gives generic regulatory workflows. eu-finreg gives the structured EU financial regulation corpus underneath, with actor-role-aware scoping by jurisdiction (FIN-FSA, BaFin, EBA, ESMA, EIOPA, EUR-Lex) and entity type. When a query is "what's the regulatory pattern around AI deployment?" → regulatory-legal. When it's "what does DORA Art 28(3) require for our payment institution's ICT third-party register?" → eu-finreg.

What it includes

Seven slash commands (six interactive + one scheduled):

  • /eu-finreg:setup — syncs the user's regulatory posture from their Velvoite workspace to a local CLAUDE.md
  • /eu-finreg:obligations [regulation] — canonical obligations filtered to entity type + actor role
  • /eu-finreg:deadlines [days] — upcoming compliance deadlines (future-dated application / transition dates)
  • /eu-finreg:reg-watch [days] — recent regulatory documents in scope
  • /eu-finreg:enforcement [regulation] [min_fine_eur] — enforcement decisions (fines, sanctions, warnings) for entity type
  • /eu-finreg:search "<query>" — free-text corpus search
  • eu-finreg:reg-feed-watcher (scheduled agent) — Monday-morning digest combining changes + deadlines + enforcement

Structure (matches the external_plugins/cocounsel-legal convention)

external_plugins/eu-finreg/
├── .claude-plugin/plugin.json
├── .mcp.json                       # MCP connector to mcp.velvoite.eu
├── CLAUDE.md                       # practice profile template
├── README.md
├── LICENSE                         # MIT
├── hooks/hooks.json
├── agents/reg-feed-watcher.md      # scheduled wrapper
└── skills/
    ├── setup/SKILL.md
    ├── obligations/SKILL.md
    ├── deadlines/SKILL.md
    ├── reg-watch/SKILL.md
    ├── enforcement/SKILL.md
    ├── search/SKILL.md
    └── reg-feed-watcher/SKILL.md

Auth

Free plugin install. Each user supplies a Velvoite API key via VELVOITE_API_KEY. Free 30-day Premium trial available at https://app.velvoite.eu/register?source=plugin — same pattern as the CoCounsel Legal connector (customer subscription).

Smoke test evidence

Tested end-to-end as a Finnish payment institution profile (TestPay Oy) against production mcp.velvoite.eu:

Command Result
/eu-finreg:obligations dora ✅ 33 DORA canonical obligations with Article references, scoped to financial_entity actor role
/eu-finreg:deadlines 90 ✅ Empty (corpus has no future-dated compliance milestones in 90-day window for payment_institution) — clean fallback message
/eu-finreg:reg-watch 30 ✅ Empty (corpus quiet) — clean fallback
/eu-finreg:enforcement ✅ 15 BaFin enforcement actions returned, dominated by AML/CDD violations (Payone GmbH €95K, SOFORT GmbH €150K, Unzer E-Com €350K)
/eu-finreg:search "outsourcing register" ✅ 3 corpus matches across EIOPA + EBA documents
/eu-finreg:reg-feed-watcher ✅ Three-section digest renders correctly; empty sections properly skipped

Also tested:

  • No API key path: setup + every other command stop with a clear VELVOITE_API_KEY is not set message + sign-up URL, before any MCP call (no raw 401 dumped at the user)
  • Invalid API key: surfaces "Invalid API key — re-create at app.velvoite.eu/account?source=plugin"
  • Non-financial entity user (SaaS company with only GDPR + AI Act): plugin works for whatever regulations are configured, adds an upfront disclaimer about corpus weighting toward finreg

Disclaimers

Every command's output ends with Drafts for compliance / legal review — not legal advice. per the established repo convention.

License

MIT. Plugin code is free; the Velvoite corpus is a separate service with its own ToS at https://velvoite.eu/legal. See external_plugins/eu-finreg/LICENSE.

Maintenance

Maintained by Silly Pilot Oy. The plugin is also distributed via a standalone marketplace at https://github.com/velvoite-eu/velvoite-plugins for users who prefer to install from the vendor directly. Both sources ship the same plugin code; this one becomes the discoverable channel inside claude-for-legal.

Test plan for reviewers

  1. Sign up for a free Velvoite trial: https://app.velvoite.eu/register?source=plugin (no credit card)
  2. Configure a test workspace as e.g. a Finnish payment institution
  3. Create an API key at https://app.velvoite.eu/account?source=plugin
  4. export VELVOITE_API_KEY=vv_... in your shell
  5. Install the plugin from this PR's branch and run each command
  6. Confirm: data returns from mcp.velvoite.eu, all 7 commands work, footer disclaimers present

Adds eu-finreg as a partner-built plugin under external_plugins/, the EU
financial regulation specialist for legal and compliance teams at
EU-regulated financial institutions. Companion to regulatory-legal —
when you need EU finreg depth (DORA, MiCA, PSD, AML/CFT, MiFID II,
CRD/CRR, etc.) with actor-role-aware scoping and entity-type-specific
enforcement intelligence.

Wraps the Velvoite corpus (mcp.velvoite.eu) covering EUR-Lex, EBA,
ESMA, EIOPA, FIN-FSA, BaFin. Requires a Velvoite API key — free
30-day Premium trial at app.velvoite.eu.

Built and maintained by Silly Pilot Oy. Standalone marketplace also
maintained at github.com/velvoite-eu/velvoite-plugins for users who
prefer to install from the vendor directly.
@github-actions

Copy link
Copy Markdown


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@Velvoite

Velvoite commented May 26, 2026 via email

Copy link
Copy Markdown
Author

@Velvoite

Copy link
Copy Markdown
Author

Friendly heads-up on the CLA flow before signing:

The CLA link in the bot's comment (https://github.com/anthropics/claude-for-legal/blob/main/CLA.md) and in CONTRIBUTING.md (source) returns HTTP 404 — the CLA.md file doesn't appear to be published yet (git log -- CLA.md confirms it has never existed in this repo's history).

The signing-comment mechanism in the bot still works mechanically, but external contributors literally can't read what they're being asked to sign today. As a small EU company shipping our first partner plugin here, we'd rather wait to sign until the actual CLA text is published — both because we want to know what we're agreeing to, and because we'd hate to set the precedent of "magic-phrase signing without text."

Couple of paths forward you might consider:

  • Publish the CLA.md text (the Apache 2.0 LICENSE at repo root is outbound — different document than the inbound contributor agreement the bot is asking us to sign)
  • Or update CONTRIBUTING.md to point to wherever the canonical CLA text actually lives
  • Or switch to a different CLA flow if the bot is no longer the intended mechanism

Happy to sign as soon as the document is available. Plugin is otherwise ready for review — happy to demo if useful (contact: matti@velvoite.eu).

cc'ing the other open partner-plugin PRs in case they hit the same wall: #45 (arguman-legal), #63 (redjudicial-legal).

@Velvoite

Velvoite commented Jun 8, 2026

Copy link
Copy Markdown
Author

Superseded by #92 (eu-legal + fi-startup-legal plugins) and #93 (Velvoite connector). Closing this earlier draft.

@Velvoite Velvoite closed this Jun 8, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant