Server Details
EU financial regulatory monitoring: DORA, MiCA, MiFID II, AML, Solvency II and more.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
9 toolsget_deadlinesInspect
Get upcoming regulatory deadlines for compliance calendar tracking.
Returns obligations with deadlines in chronological order, annotated
with days remaining or days overdue. Essential for compliance planning.
Args:
entity_type: Filter by entity type code (e.g. 'credit_institution').
regulation: Filter by regulation code (e.g. 'dora').
days_ahead: How many days ahead to look (default 90, max 730).
include_overdue: Include past-due obligations (default true).| Name | Required | Description | Default |
|---|---|---|---|
| days_ahead | No | ||
| regulation | No | ||
| entity_type | No | ||
| include_overdue | No |
get_documentInspect
Get full details of a specific regulatory document by its ID.
Returns the document metadata, AI summary, all classification tags,
inline obligations (up to 50 with total count), and a link to the original source.
Use the URL to access the full text on the official regulatory website (EUR-Lex, EBA, ESMA, FIN-FSA).
Get the document_id from search_regulations or list_documents results.
Args:
document_id: The Velvoite document ID (integer from search/list results).| Name | Required | Description | Default |
|---|---|---|---|
| document_id | Yes |
get_obligationsInspect
Get regulatory obligations - specific requirements extracted from regulations.
Each obligation includes the requirement text, applicable article reference,
deadline, which entity types it applies to, and current status.
Results are paginated (max 50 per page).
Supports keyword search via the query parameter (trigram + ILIKE matching on obligation text).
Combine with regulation and entity_type filters for precise results.
Args:
entity_type: Filter by entity type code (e.g. 'credit_institution', 'payment_institution').
regulation: Filter by regulation code (e.g. 'dora', 'mica', 'aml').
status: Filter by status: 'upcoming', 'active', 'overdue', or 'expired'.
query: Keyword search on obligation text (e.g. 'ICT risk', 'strong customer authentication').
page: Page number (default 1).
per_page: Results per page (default 20, max 50).| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| query | No | ||
| status | No | ||
| per_page | No | ||
| regulation | No | ||
| entity_type | No |
get_obligation_summaryInspect
Get obligation counts grouped by regulation_code.
Returns total count and per-regulation breakdown with status counts
(active, upcoming, overdue, expired) plus verified and with_deadline counts.
No full obligation text — just counts for a quick overview.
Args:
entity_type: Filter to obligations applying to this entity type (e.g. 'credit_institution', 'payment_institution').| Name | Required | Description | Default |
|---|---|---|---|
| entity_type | No |
get_recent_changesInspect
Get recently published or updated regulatory documents.
Shortcut for 'what is new this week' - returns documents from the last N days,
sorted by publication date (newest first). Useful for weekly regulatory briefings.
Args:
days: Look back N days (default 7).
entity_type: Filter by entity type code.
regulation: Filter by regulation family code.
urgency_max: Only include items at or above this urgency (1=critical, 2=high, etc.).| Name | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| regulation | No | ||
| entity_type | No | ||
| urgency_max | No |
get_statsInspect
Get an overview of the Velvoite regulatory corpus.
Returns document counts by source, regulation family, entity type, urgency distribution, obligation summary, and date range.
Call this FIRST to orient yourself before running queries. No parameters needed.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_verification_statsInspect
Get verification progress for obligations across all regulations.
Returns total, verified, unverified counts overall and per regulation, with percentage verified. Use this to track human review progress. No parameters needed.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_documentsInspect
Browse regulatory documents with filters and pagination.
Returns a paginated list of documents with summaries and tags.
Use this for filtered browsing (e.g. all DORA documents from the last 30 days).
Use search_regulations instead when you have specific keywords to search for.
Args:
source: Filter by data source code: eur_lex, eba, esma, eiopa, finfsa, bafin.
regulation: Filter by regulation family code: dora, mica, aml, mifid2, crd_crr, psd, csrd, sfdr, ai_act, emir, solvency, idd, gdpr.
entity_type: Filter by entity type: credit_institution, payment_institution, e_money, investment_firm, fund_manager, aifm, insurance, pension, crypto_service, crowdfunding, credit_servicer.
urgency_max: Max urgency level (1=critical, 2=high, 3=medium, 4=low, 5=informational). E.g. 2 returns only critical and high urgency items.
days: Only return documents from the last N days (1-365).
page: Page number (default 1).
per_page: Results per page (default 20, max 100).| Name | Required | Description | Default |
|---|---|---|---|
| days | No | ||
| page | No | ||
| source | No | ||
| per_page | No | ||
| regulation | No | ||
| entity_type | No | ||
| urgency_max | No |
search_regulationsInspect
Search the regulatory corpus using keyword / trigram matching.
Uses PostgreSQL trigram similarity on document titles and summaries.
Returns documents ranked by relevance with summaries and classification tags.
Prefer list_documents with filters (regulation, entity_type, source) first.
Only use this for free-text keyword search when structured filters aren't sufficient.
Args:
query: Search terms (e.g. 'strong customer authentication', 'ICT risk', 'AML reporting').
per_page: Number of results (default 20, max 100).| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| per_page | No |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Sign in to verify ownershipControl your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!