A
licenseA
qualityC
maintenanceFinData MCP gives AI agents access to market data, company fundamentals, and macroeconomic indicators via MCP. It covers stocks, ETFs, crypto, forex, commodities, and economic time series.
5
1
MIT
NexusForge EU Finance
OfficialNexusForge EU Finance
European financial data for AI agents ECB rates · Eurostat inflation · GDP · Unemployment · Zero API key needed
Quick Start
Claude Code — one command:
claude mcp add eu-finance -- npx -y @nexusforgetools/eu-financeClaude Desktop / Cursor / Windsurf — add to your MCP config:
{
"mcpServers": {
"eu-finance": {
"command": "npx",
"args": ["-y", "@nexusforgetools/eu-finance"]
}
}
}Related MCP server: ecb-mcp
What You Can Ask
"What's the current ECB deposit facility rate and how does it compare to last year?"
"Compare inflation across Germany, France, Spain, and Italy — who's closest to the 2% target?"
"Show me Q4 GDP growth for the Eurozone vs the EU-27 average."
"What's the EUR/USD rate today? What was it on 2024-01-15?"
In Action
Tools
Tool | Description | Source |
| ECB key interest rates: deposit facility, main refinancing, marginal lending | ECB SDW |
| EUR exchange rates vs any currency — latest or historical by date | ECB / Frankfurter |
| HICP inflation rates for all EU countries — annual % change | Eurostat |
| Quarterly GDP data — growth rate or absolute value, all EU countries | Eurostat |
| Monthly unemployment rates — seasonally adjusted, by age group | Eurostat |
| Side-by-side snapshot: inflation + GDP + unemployment for 2-10 countries | Eurostat |
Free vs Pro
eu-finance is free during beta. Pro is coming in Month 2 with higher rate limits and all NexusForge servers bundled.
More NexusForge Servers
Package | Description | Status |
| Scraping & structured data enrichment | Coming soon |
| Market sizing, competitors, trends | Coming soon |
Available Tools
6 toolscompare_eu_economiesARead-onlyIdempotent
Fetches the latest inflation, GDP growth, and unemployment for 2-10 EU countries in a single parallel call to Eurostat. Returns a JSON object with: countries (array of per-country snapshots, each containing country as full name, country_code, inflation as {rate, period} or null, gdp_growth as {rate, period} or null, unemployment as {rate, period} or null), source, and retrieved_at as ISO 8601. Each indicator returns the single most recent available value. Inflation period is YYYY-MM; GDP period is YYYY-Qq; unemployment period is YYYY-MM. Data is cached 24 hours. USAGE: Prefer this tool over calling get_eu_inflation, get_eu_gdp, and get_eu_unemployment separately when building dashboards or running multi-indicator comparisons — it reduces latency by parallelizing the three Eurostat requests. Each indicator's period may differ due to different Eurostat release schedules (inflation lags ~30 days, GDP ~90 days). An indicator field is null when Eurostat has not published recent data — always handle null gracefully. Use the indicators parameter to skip unneeded metrics and reduce API calls.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| countries | Yes | 2-10 EU country codes to compare (e.g. ["DE", "FR", "ES", "IT"]). Use "EA20" for Eurozone. | |
| indicators | No | Which indicators to include. Default: all three. |
TDQS
A4.6/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint etc. The description adds caching (24h), period formats, and release lag, which are useful beyond annotations. No contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Well-structured with front-loaded purpose and detailed sections. Slightly longer than minimal, but every sentence adds value—clear and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description fully explains the return format, null handling, caching, and usage context, making it complete for an agent to invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and includes clear descriptions for both parameters. The description adds context like using 'EA20' for Eurozone and that indicators can be filtered, enhancing but not duplicating schema info.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Fetches') and resource ('latest inflation, GDP growth, and unemployment for 2-10 EU countries'), and distinguishes from sibling tools by noting it replaces three separate calls, making purpose crystal clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit guidance: 'Prefer this tool over calling get_eu_inflation, get_eu_gdp, and get_eu_unemployment separately' and advice to handle null gracefully, directly addressing when and how to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_ecb_ratesARead-onlyIdempotent
Fetches the three ECB key interest rates from the ECB Statistical Data Warehouse (SDMX). Returns a JSON object with rates containing three entries — deposit_facility, main_refinancing, and marginal_lending — each with date (YYYY-MM-DD of the last rate change) and value (percentage as a number). Also includes source and retrieved_at as ISO 8601. Results are cached for 1 hour. USAGE: These are ECB policy rates, not real-time market rates — they only change at Governing Council meetings (roughly every 6 weeks). The date field indicates when the current rate was set, not today's date. For currency conversion use get_euro_exchange; these rates are not applicable for forex calculations. Use get_eu_inflation alongside this tool to assess the real interest rate (nominal rate minus inflation).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
A4.8/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds behavioral context beyond annotations: caching for 1 hour, meaning of the date field, and that rates only change every 6 weeks. Annotations already indicate read-only and idempotent traits; no contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured with sections, front-loads the purpose, and adds necessary context. Slightly verbose but each sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, the description fully covers what the tool returns, caching behavior, usage notes, and relationship to sibling tools. Complete for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters, so the description does not need to add parameter meanings. Baseline is 4 for zero parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool fetches the three ECB key interest rates from the ECB Statistical Data Warehouse. It explicitly lists the returned rates and distinguishes from siblings like get_euro_exchange and get_eu_inflation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit when to use (ECB policy rates), when not to use (not for real-time market rates or forex), and suggests using with inflation for real interest rate calculation. It also mentions the update frequency.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_eu_gdpARead-onlyIdempotent
Fetches quarterly GDP data for EU/Eurozone countries from Eurostat (dataset: namq_10_gdp). Returns a JSON object with: data (array of objects, each containing country as a full name string, period in YYYY-Qq format e.g. "2024-Q3", value as a number, and unit as a string label), source, and retrieved_at as ISO 8601. Defaults to year-on-year growth rate (%) for EA20, EU27_2020, DE, FR, IT, ES over the last 4 quarters. Data is cached 24 hours. Missing periods are omitted from the array (not returned as null). USAGE: Use unit=CLV_PCH_SM (default) for cross-country growth comparisons. Use unit=CP_MEUR to compare absolute GDP size. Use unit=CLV_PCH_PRE for quarter-on-quarter momentum. Use unit=CLV10_MEUR for real GDP volume excluding price effects. Typical Eurostat data lag is 60-90 days after quarter end — the most recent quarter may be absent. Request quarters=8 or more for recession analysis or multi-year trend charts.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| countries | No | List of EU country codes (e.g. ["DE", "FR"]). Use "EA20" for Eurozone, "EU27_2020" for EU-27. | |
| unit | No | Unit: CLV_PCH_SM = growth rate vs same quarter previous year (default), CLV_PCH_PRE = growth rate vs previous quarter, CP_MEUR = current prices in million EUR, CLV10_MEUR = chain-linked volumes in million EUR | CLV_PCH_SM |
| quarters | No | Number of recent quarters to return (1-20). Default: 4 (1 year). |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds key behavioral traits: data is cached for 24 hours, missing periods are omitted (not returned as null), and typical Eurostat data lag is 60-90 days. This provides rich context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured with a clear opening sentence stating the tool's purpose. It then covers output format, defaults, caching, and usage in a logical order. While it is detailed, every sentence serves a purpose; minor verbosity could be trimmed.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of an output schema, the description thoroughly explains the returned data structure (array of objects with country, period, value, unit), plus source and retrieved_at fields. It covers all parameters, default behavior, caching, data lag, and missing period handling. Complete for a data retrieval tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the semantic meaning of each unit (e.g., CLV_PCH_SM for year-on-year growth) and giving examples of country codes (EA20, EU27_2020). It also clarifies defaults and parameter effects.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches quarterly GDP data for EU/Eurozone countries from Eurostat, specifying the dataset (namq_10_gdp). It distinguishes from siblings which cover other economic indicators like inflation, unemployment, and exchange rates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes explicit guidance on when to use each unit parameter (e.g., use CLV_PCH_SM for cross-country growth comparisons, CP_MEUR for absolute GDP size). It also mentions typical data lag and suggests using more quarters for recession analysis. However, it does not directly compare with sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_eu_inflationARead-onlyIdempotent
Fetches HICP (Harmonised Index of Consumer Prices) annual inflation rates for EU countries from Eurostat (dataset: prc_hicp_manr). Returns a JSON object with: data (array of objects containing country as full name, period in YYYY-MM format, and rate as a numeric annual percentage change), unit ("Annual rate of change (%)"), source, and retrieved_at as ISO 8601. Defaults to the latest single month for all 29 EU members and aggregates. Data is cached 24 hours. USAGE: HICP is the EU-harmonised inflation standard used by the ECB for monetary policy — use it (not national CPI) for cross-country comparisons. Use country code EA for the Eurozone aggregate or EU27_2020 for the full EU-27 aggregate. Typical data lag is 30-45 days after the reference month. Set periods=12 to retrieve a 12-month trend. Pair with get_ecb_rates to contextualize how the ECB policy rate relates to current inflation.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| countries | No | List of EU country codes (e.g. ["DE", "FR", "ES"]) or "EA" for Eurozone / "EU27_2020" for EU-27. Omit for all EU countries. | |
| periods | No | Number of recent months to return per country (1-24). Default: 1 (latest only). |
TDQS
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and idempotentHint=true. Description adds significant behavioral details: data is cached for 24 hours, typical data lag is 30-45 days, and output structure is JSON with specific fields. No contradictions with annotations. Adds valuable context beyond what annotations provide.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is well-structured: first sentence explains core function, then output format, defaults, caching, usage guidelines, and additional tips. Every sentence serves a purpose with no fluff. Length is appropriate given the complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's moderate complexity and simple schema (2 parameters, no nested objects, no output schema), the description fully covers what an agent needs: data source, output structure, default behavior, caching, data lag, and usage recommendations. Complete enough for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both parameters (countries and periods). Description adds value by explaining that omitting countries returns all EU members, and provides usage examples for EA and EU27_2020. Also mentions that periods=12 gives 12-month trend. While schema already covers defaults, description reinforces and adds context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it fetches HICP annual inflation rates for EU countries from Eurostat, specifying the dataset code. The verb 'Fetches' and resource 'HICP annual inflation rates' are specific, and it is distinct from sibling tools like get_ecb_rates or get_eu_gdp which cover different economic indicators.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit guidance on when to use: 'HICP is the EU-harmonised inflation standard used by the ECB for monetary policy — use it (not national CPI) for cross-country comparisons.' Also explains typical data lag, how to retrieve trends with periods=12, and recommends pairing with get_ecb_rates for context. Clearly states when to use vs alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_euro_exchangeARead-onlyIdempotent
Fetches EUR exchange rates against other currencies from the ECB via Frankfurter API. Returns a JSON object with: base ("EUR"), date (YYYY-MM-DD of the rate), rates (object mapping 3-letter currency codes to numeric values representing how many units of that currency equal 1 EUR), source, and retrieved_at as ISO 8601. Latest rates are cached 1 hour; historical rates are cached permanently. USAGE: Supports 33 currencies including USD, GBP, JPY, CHF, CNY, SEK, PLN, and others. Omit date for the latest available rates. Provide date in YYYY-MM-DD format for historical rates (available from 1999-01-04). These are ECB reference rates published at ~16:00 CET — not real-time mid-market rates; expect small spreads vs live quotes. Requests for weekends or ECB holidays return the previous business day's rates. Returns an error for dates before 1999-01-04 or future dates.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| currencies | No | List of 3-letter currency codes (e.g. ["USD", "GBP", "JPY"]). Omit for all available currencies. | |
| date | No | Historical date in YYYY-MM-DD format. Omit for latest rates. |
TDQS
A4.3/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds significant behavioral context beyond annotations: caching delays (1 hour for latest, permanent for historical), non-real-time nature (published ~16:00 CET), weekend/holiday fallback, and date range constraints. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Well-structured: starts with purpose, then output format, caching, usage, limitations. Informative but slightly verbose; could be tightened without losing substance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema, the description fully explains the return JSON structure, parameters, caching, and edge cases. Complete for a tool with 2 optional parameters.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and description adds meaning: explains 'currencies' is a list of 3-letter codes (omit for all) and 'date' format/range, plus behavior when omitted. Adds value beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it fetches EUR exchange rates from the ECB via Frankfurter API, specifying the source and output structure. It distinguishes itself from sibling tools by focusing on exchange rates, but does not explicitly differentiate from 'get_ecb_rates' which might overlap.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides clear usage guidance: omit 'date' for latest rates, provide YYYY-MM-DD for historical, lists supported currencies, and explains caching behavior. However, it lacks explicit when-not-to-use guidance or alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_eu_unemploymentARead-onlyIdempotent
Fetches monthly unemployment rates for EU countries from Eurostat (dataset: une_rt_m), seasonally adjusted, as a percentage of the active population. Returns a JSON object with: data (array of objects containing country as full name, period in YYYY-MM format, rate as a numeric percentage, age_group, and sex), unit ("Percentage of active population (%)"), source, and retrieved_at as ISO 8601. Defaults to TOTAL age group for EA20, EU27_2020, DE, FR, IT, ES, PL, NL over the last 3 months. Data is cached 24 hours. USAGE: Use age=Y15-24 for youth unemployment, which is typically 2-3x the overall rate. Data is seasonally adjusted (SA) — do not apply additional seasonal correction. Typical Eurostat lag is 30-60 days after the reference month. Set months=12 or more for trend and cyclical analysis. Non-EU countries (e.g. US, UK) are not available — use this tool only for EU member states and EA20/EU27_2020 aggregates.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| countries | No | List of EU country codes (e.g. ["DE", "FR", "ES"]). Use "EA20" for Eurozone. Omit for main EU countries. | |
| months | No | Number of recent months to return (1-24). Default: 3. | |
| age | No | Age group: TOTAL (all ages), Y15-24 (youth), Y25-74 (adults). Default: TOTAL. | TOTAL |
TDQS
A4.9/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds valuable behavioral context: data cached 24 hours, typical lag 30-60 days, seasonally adjusted, and default parameters. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Approximately 10 sentences, well-structured: begins with core purpose, then output format, defaults, caching, and usage advice. Every sentence adds meaningful information without repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has three parameters and no output schema, the description fully covers output format, source, caching, lag, and usage scenarios like youth unemployment and trend analysis. It leaves no critical gaps for an agent to understand proper invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for all three parameters. The description enriches semantics by explaining default countries, providing usage tips for each parameter (e.g., using age for youth) and clarifying that countries list can include aggregates like EA20. It adds value beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches monthly unemployment rates for EU countries from Eurostat (dataset: une_rt_m), seasonally adjusted, and specifies the output structure. It distinguishes from siblings by noting it is only for EU member states and EA20/EU27_2020 aggregates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit guidance: when to use age=Y15-24 for youth unemployment, setting months=12+ for trend analysis, and warns that non-EU countries are not available. It also notes the data is seasonally adjusted so no additional correction is needed, and mentions typical Eurostat lag.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
6 tool updates
v1.0.0- First observed
compare_eu_economies - First observed
get_ecb_rates - First observed
get_eu_gdp - First observed
get_eu_inflation - First observed
get_eu_unemployment - First observed
get_euro_exchange
TDQS
A4.6/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose. The `compare_eu_economies` tool is designed for multi-country, multi-indicator comparisons, while the individual getter tools allow for more detailed, single-indicator queries. Their descriptions clearly delineate when to use each, preventing confusion.
Naming Consistency5/5
All tool names follow a consistent `verb_noun` pattern using lowercase and underscores (e.g., `compare_eu_economies`, `get_ecb_rates`, `get_eu_gdp`). The verbs are specific and the nouns precisely describe the resource, making the naming predictable and easy to understand.
Tool Count5/5
With 6 tools, the set is well-scoped for a server focused on EU economic data and exchange rates. It provides sufficient functionality without being overwhelming, covering the core indicators requested by users interested in European finance.
Completeness4/5
The tool set covers the major EU economic indicators (inflation, GDP, unemployment, ECB rates, exchange rates) and offers a convenient multi-indicator comparison. Minor gaps exist, such as the absence of tools for other ECB policy tools or more granular GDP components, but the essential lifecycle is covered for its stated purpose.
Maintenance
ActivityInactive
ResponsivenessUnresponsive
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Macro data for AI agents: GDP, inflation, unemployment and more (World Bank, US BLS). No keys.
Macro data for AI agents: GDP, inflation, unemployment and more (World Bank, US BLS). No keys.
51Utility data for AI agents: IBAN, EU holidays, VAT rates, time zones, ECB FX. Pay per call.
Macroeconomic and FX time-series data for AI agents: indicators, calendars, COT, forex, commodities.
Related MCP Servers
- AlicenseAqualityFmaintenanceECB data for AI agents — rates, yields, inflation, money supply, and 100+ datasets. No API key.8693MIT
- AlicenseAqualityDmaintenanceEnables AI agents to access SEC EDGAR filings, US Treasury rates, BLS labor statistics, and economic indicators without API keys.632MIT
- AlicenseAqualityCmaintenanceQuery 2,500+ verified public datasets (World Bank, IMF, Eurostat, OECD, WHO) from your AI agent. Search, analyze, and visualize data, and publish charts — with verified SEC + official source data.284101MIT
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nexusforge-tools/mcp-eu-finance'
If you have feedback or need assistance with the MCP directory API, please join our Discord server