Energetica — Argentine Oil & Gas Data
REMOTE · ENERGETICA.AR
Argentine oil & gas data — 40+ curated tables: production, wells, prices, investments, trade.
Available components
Last scanned (21 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2806 tokens (~200/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management69
- Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 1 breaking changes, 0 auth/transport breaks, 8 additions. See how to fix → Fail
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 32% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_sql" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 65 to 69.
- 28 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 69 to 65.
- 19 Oct 26 −11
- Stability: pass → fail ▼ security
- Tool “get_data_freshness” was removed ▼ security
- Tool “get_schema” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “execute_sql” rewrote its description, which is the text the model reads security
- Tool “query_production” rewrote its description, which is the text the model reads security
- Tool “query_wells” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 32% ▼ functional
- Schema quality: pass → fail ▼ functional
- “execute_sql” changed the type of “max_rows”: integer → number ▼ functional
- “query_investments” changed the type of “anio_desde”: integer → number ▼ functional
- “query_investments” changed the type of “anio_hasta”: integer → number ▼ functional
- “query_investments” changed the type of “max_rows”: integer → number ▼ functional
- “query_prices” changed the type of “max_rows”: integer → number ▼ functional
- “query_production” changed the type of “agrupar_por”: string → array ▼ functional
- “query_production” changed the type of “max_rows”: integer → number ▼ functional
- “query_trade” changed the type of “anio”: integer → number ▼ functional
- “query_trade” changed the type of “max_rows”: integer → number ▼ functional
- “query_wells” changed the type of “max_rows”: integer → number ▼ functional
- First check of Tool coverage: 100 functional
- Schema quality: excellent → good functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Server version: 2.0.0 → 3.0.0 functional
- New tool “describe_data” functional
- New tool “get_area” functional
- New tool “get_company” functional
- New tool “get_well” functional
- New tool “query_completions” functional
- New tool “query_reserves” functional
- New tool “rank_entities” functional
- New tool “resolve_entity” functional
- “query_production” added an optional parameter “area_concesion” cosmetic
- “query_production” added an optional parameter “idpozo” cosmetic
- “query_production” added an optional parameter “metricas” cosmetic
- “query_production” added an optional parameter “provincia” cosmetic
- “query_production” added an optional parameter “subtipo_recurso” cosmetic
- “query_production” added an optional parameter “tipo_pozo” cosmetic
- “query_production” added an optional parameter “tipo_recurso” cosmetic
- “query_production” added an optional parameter “yacimiento” cosmetic
- “query_wells” added an optional parameter “area_concesion” cosmetic
- “query_wells” added an optional parameter “orden” cosmetic
- “query_wells” added an optional parameter “primera_produccion_desde” cosmetic
- “query_wells” added an optional parameter “primera_produccion_hasta” cosmetic
- “query_wells” added an optional parameter “segun_padron” cosmetic
- “query_wells” added an optional parameter “subtipo_recurso” cosmetic
- “query_wells” added an optional parameter “tipo_pozo” cosmetic
- “query_wells” added an optional parameter “yacimiento” cosmetic
- “execute_sql” reworded the description of “max_rows” cosmetic
- “execute_sql” reworded the description of “sql” cosmetic
- “query_investments” reworded the description of “anio_desde” cosmetic
- “query_investments” reworded the description of “anio_hasta” cosmetic
- “query_investments” reworded the description of “cuenca” cosmetic
- “query_investments” reworded the description of “empresa” cosmetic
- “query_investments” reworded the description of “max_rows” cosmetic
- “query_prices” reworded the description of “fecha_desde” cosmetic
- “query_prices” reworded the description of “fecha_hasta” cosmetic
- “query_prices” reworded the description of “frecuencia” cosmetic
- “query_prices” reworded the description of “max_rows” cosmetic
- “query_prices” reworded the description of “provincia” cosmetic
- “query_prices” reworded the description of “serie” cosmetic
- “query_production” reworded the description of “agrupar_por” cosmetic
- “query_production” reworded the description of “cuenca” cosmetic
- “query_production” reworded the description of “empresa” cosmetic
- “query_production” reworded the description of “fecha_desde” cosmetic
- “query_production” reworded the description of “fecha_hasta” cosmetic
- “query_production” reworded the description of “formacion” cosmetic
- “query_production” reworded the description of “max_rows” cosmetic
- “query_trade” reworded the description of “anio” cosmetic
- “query_trade” reworded the description of “max_rows” cosmetic
- “query_wells” reworded the description of “con_produccion” cosmetic
- “query_wells” reworded the description of “cuenca” cosmetic
- “query_wells” reworded the description of “empresa” cosmetic
- “query_wells” reworded the description of “formacion” cosmetic
- “query_wells” reworded the description of “max_rows” cosmetic
- “query_wells” reworded the description of “provincia” cosmetic
- “query_wells” reworded the description of “tipo_estado” cosmetic
- “query_wells” reworded the description of “tipo_recurso” cosmetic
- “query_production” dropped the optional parameter “recurso” cosmetic
- 29 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://energetica.ar/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=energetica.ar | CN=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60eb7394a65f1c8ee8f0292275f81dc1b80 |
| SANs: energetica.ar | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of energetica.ar. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ar. | present | 19606 | 8 | Verified |
| energetica.ar. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' https://www.googletagmanager.com https://www.google-analytics.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://www.google-analytics.com https://www.googletagmanager.com https://*.basemaps.cartocdn.com; font-src 'self' data:; connect-src 'self' https://www.google-analytics.com https://analytics.google.com https://region1.google-analytics.com https://www.googletagmanager.com https://www.google.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://energetica.ar/api/mcp | Verified | 200 | |
| http (plaintext) | http://energetica.ar/api/mcp | HTTPS enforced | 308 | https://energetica.ar/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe_data Data catalog ~75
Start here. Every table and view: description, period, rows, tool to use, warnings, and the last complete production month. With tablas, also their columns. Example: {tablas: ['pozos']}.
| Name | Type | Req | Description |
|---|---|---|---|
| max_rows | number | – | – |
| tablas | array | – | Tables or views whose columns you need |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
execute_sql Read-only SQL ~114
Run read-only DuckDB SQL (a single SELECT or WITH) over the catalog tables and views. Prefer the curated tools when they fit; call describe_data first for tables and columns. Column names and values are in Spanish. Example: {sql: "SELECT anio, SUM(prod_petroleo_m3) FROM agg_produccion_mensual WHERE formacion = 'vaca muerta' GROUP BY 1 ORDER BY 1"}.
| Name | Type | Req | Description |
|---|---|---|---|
| max_rows | number | – | – |
| sql | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
get_area Concession area profile ~81
One concession area: 12-month production and year-on-year change, operators and shares, wells by type and state, top wells and the last 24 months. Example: {area_concesion: 'LOMA CAMPANA'}.
| Name | Type | Req | Description |
|---|---|---|---|
| area_concesion | string | yes | Area name; close names are resolved |
| max_rows | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
get_company Company profile ~84
One operator: 12-month production, national share, year-on-year change, areas, basins, wells, investments, reserves and, if listed, share price and SEC financials. Example: {empresa: 'VISTA ENERGY ARGENTINA SAU'}.
| Name | Type | Req | Description |
|---|---|---|---|
| empresa | string | yes | Company name; close names are resolved |
| max_rows | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
get_well Well profile ~103
One well by idpozo or sigla: registry data, IP30/90/180, cumulative volumes, recent GOR and water cut, last 36 months of production, fracture jobs and trajectory. Example: {sigla: 'YPF.Nq.LCa-1001(h)'}.
| Name | Type | Req | Description |
|---|---|---|---|
| idpozo | number | – | – |
| max_rows | number | – | – |
| sigla | string | – | Well code; close codes are resolved |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
query_completions Fracture jobs (completions) ~166
Fracture jobs by year, company (the one that reported the job), area, formation or well: wells, stages, stages per well, lateral length, proppant, water. Example: {formacion: 'vaca muerta', fecha_desde: '2025', agrupar_por: ['empresa']}.
| Name | Type | Req | Description |
|---|---|---|---|
| agrupar_por | array | – | Default anio |
| area_concesion | string | – | – |
| cuenca | string | – | – |
| empresa | string | – | – |
| fecha_desde | string | – | Completion (end of fracture) from |
| fecha_hasta | string | – | – |
| formacion | string | – | – |
| max_rows | number | – | – |
| subtipo_reservorio | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
query_investments Upstream investments ~165
Upstream oil & gas investments in Argentina by company, basin, year and concept, in millions of USD (drilling, workovers, pipelines, facilities, seismic…). Example: {cuenca: 'NEUQUINA', anio_desde: 2023, concepto: 'perforacion'}.
| Name | Type | Req | Description |
|---|---|---|---|
| anio_desde | number | – | Year of the sworn statement (DDJJ) |
| anio_hasta | number | – | – |
| concepto | string | – | Investment concept, partial match ignoring accents (e.g. 'perforacion', 'reparacion de pozos', 'gasoductos', 'sismica') |
| cuenca | string | – | – |
| empresa | string | – | – |
| max_rows | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
query_prices Energy prices and exchange rates ~142
International and local energy prices: WTI, Brent, Henry Hub (daily, USD), Argentine crude price used for royalties by province (monthly, USD/bbl) and ARS/USD exchange rates (daily). Most recent first. Example: {serie: 'BRENT', fecha_desde: '2024', frecuencia: 'mensual'}.
| Name | Type | Req | Description |
|---|---|---|---|
| fecha_desde | string | – | – |
| fecha_hasta | string | – | Inclusive |
| frecuencia | string | – | Average; CRUDO_LOCAL is monthly |
| max_rows | number | – | – |
| provincia | string | – | Only CRUDO_LOCAL; omit for every province |
| serie | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
query_production Monthly hydrocarbon production ~258
Oil, gas and water production (2006–present) by entity and period, grouped by up to 3 dimensions: volumes, BOE, producing/reporting wells, daily rate, GOR, water cut. Example: {area_concesion: "LOMA CAMPANA", fecha_desde: "2025", agrupar_por: ["anio"]}.
| Name | Type | Req | Description |
|---|---|---|---|
| agrupar_por | array | – | Up to 3 dimensions; default [mes] |
| area_concesion | string | – | – |
| cuenca | string | – | – |
| empresa | string | – | – |
| fecha_desde | string | – | – |
| fecha_hasta | string | – | Inclusive |
| formacion | string | – | – |
| idpozo | array | – | – |
| max_rows | number | – | – |
| metricas | array | – | Default petroleo, gas, agua (+ pozos_productores by mes); caudal_diario = volume / calendar days |
| provincia | string | – | – |
| subtipo_recurso | string | – | – |
| tipo_pozo | string | – | e.g. Petrolífero, Gasífero |
| tipo_recurso | string | – | – |
| yacimiento | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
query_reserves Hydrocarbon reserves ~147
P1/P2/P3 oil and gas reserves at Dec 31 by year, basin, company and resource type (end of useful life); oil and gas in separate columns. Default: latest year. Example: {anio: [2024], agrupar_por: ['cuenca'], categorias: ['P1']}.
| Name | Type | Req | Description |
|---|---|---|---|
| agrupar_por | array | – | Default anio |
| anio | array | – | Years; default the latest |
| categorias | array | – | Default P1, P2, P3 |
| cuenca | string | – | – |
| empresa | string | – | – |
| max_rows | number | – | – |
| tipo_recurso | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
query_trade Hydrocarbon trade balance ~103
Argentina hydrocarbon exports and imports by month: crude oil (HS 2709), refined products (HS 2710) and natural gas (HS 2711), FOB USD and kg. Example: {anio: 2025, flow: 'export', producto: 'crude'}.
| Name | Type | Req | Description |
|---|---|---|---|
| anio | number | – | – |
| flow | string | – | Trade flow direction |
| max_rows | number | – | – |
| producto | string | – | Product category |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
query_wells Wells search ~267
Wells in the registry (~86,000): location, type, current status and operator, cumulative production, first and last month with production, IP30. Example: {provincia: 'Neuquén', subtipo_recurso: 'SHALE', tipo_estado: 'activos'}.
| Name | Type | Req | Description |
|---|---|---|---|
| area_concesion | string | – | – |
| con_produccion | boolean | – | – |
| cuenca | string | – | – |
| empresa | string | – | – |
| formacion | string | – | – |
| max_rows | number | – | – |
| orden | string | – | – |
| primera_produccion_desde | string | – | First month with oil or gas > 0 (or the registry fecha_primera_prod with segun_padron) |
| primera_produccion_hasta | string | – | – |
| provincia | string | – | – |
| segun_padron | boolean | – | – |
| subtipo_recurso | string | – | – |
| tipo_estado | string | – | Exact registry status (e.g. Abandonado, Parado Transitoriamente) or 'activos' |
| tipo_pozo | string | – | e.g. Petrolífero, Gasífero |
| tipo_recurso | string | – | – |
| yacimiento | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
rank_entities Rankings ~280
Top N wells, areas, companies, fields, basins or formations by production, BOE, GOR, water cut, growth, new wells or IP30/90/180 (raw, per meter, per stage). Example: {entidad: 'pozo', metrica: 'ip30', subtipo_recurso: 'SHALE', tipo_pozo: 'Petrolífero', fecha_desde: '2025', fecha_hasta: '2025'}.
| Name | Type | Req | Description |
|---|---|---|---|
| area_concesion | string | – | – |
| cuenca | string | – | – |
| empresa | string | – | – |
| entidad | string | yes | – |
| fecha_desde | string | – | Default: 12 months to fecha_hasta |
| fecha_hasta | string | – | Inclusive; default the last complete month |
| formacion | string | – | – |
| max_rows | number | – | – |
| metrica | string | yes | ip*: wells of a first-production cohort (or their average per entity); others over the period |
| n | integer | – | Default 10 |
| orden | string | – | – |
| provincia | string | – | – |
| subtipo_recurso | string | – | – |
| tipo_pozo | string | – | e.g. Petrolífero, Gasífero |
| yacimiento | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
resolve_entity Find companies, areas, fields and wells ~82
Free text → exact names for filters (companies, areas, fields, formations, basins, provinces, wells), with context and last month with production. Example: {texto: 'palmar', tipo: 'yacimiento'}.
| Name | Type | Req | Description |
|---|---|---|---|
| max_rows | number | – | – |
| texto | string | yes | Name or part of it |
| tipo | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | yes | – |
| meta | object | yes | – |
| rows | array | yes | – |
| sections | array | – | – |
No examples provided.
How do I install the Energetica — Argentine Oil & Gas Data MCP server?
Energetica — Argentine Oil & Gas Data is a hosted endpoint at https://energetica.ar/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · energetica.ar
claude mcp add --transport http ar-energetica-data 'https://energetica.ar/api/mcp'
What is the Energetica — Argentine Oil & Gas Data MCP server?
Energetica — Argentine Oil & Gas Data is an MCP server listed in the public MCP registry as ar.energetica/data. Argentine oil & gas data, 40+ curated tables: production, wells, prices, investments, trade. This page covers its hosted endpoint (https://energetica.ar/api/mcp).
Is the Energetica — Argentine Oil & Gas Data MCP server safe to use?
Energetica — Argentine Oil & Gas Data scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Energetica — Argentine Oil & Gas Data MCP server expose?
Energetica — Argentine Oil & Gas Data exposes 14 tools: describe_data, resolve_entity, query_production, query_wells, get_well, and 9 more. Their descriptions and schemas cost roughly 2,067 tokens of context every time the server is loaded.
Does the Energetica — Argentine Oil & Gas Data MCP server require authentication?
No. We connected to Energetica — Argentine Oil & Gas Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Energetica — Argentine Oil & Gas Data MCP server still maintained?
Energetica — Argentine Oil & Gas Data is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.