Skip to content
Energética logo

Energética MCP server

Which servers in the official MCP registry are Energética's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to Energética

Whose server it is
  • Registry namear.energetica/dataverified in the MCP registry

The registry name sits under energetica.ar. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24
  • Stateanswerschecked 2026-10-24
  • Tools14
  • Server calls itselfenergetica-data
  • Server version3.0.0
  • Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 198 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: compare initial well productivity across operators and areas; ask production questions in plain language and get charts.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "ask production questions in plain language and get charts", the likely first call is describe_data.
  • Parameters are untyped or undescribed in 14 of 14 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-24
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer598 ms
  • Space in an agent's context≈ 2,984 tokensthe definitions of all its tools (14), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results14 of 14 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 14 of 14

What an agent can do with it

  • can do · compare initial well productivity across operators and areas
  • can do · ask production questions in plain language and get charts
  • not sure · export well data to Excel or CSV for outside analysis

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers14 tools · read 2026-10-24
  • describe_data

    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']}.

  • resolve_entity

    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'}.

  • query_production

    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"…

  • query_wells

    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'}.

  • get_well

    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)'}.

  • get_area

    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'}.

  • get_company

    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'}.

  • rank_entities

    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…

  • query_completions

    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']}.

  • query_reserves

    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']}.

  • query_investments

    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'}.

  • query_prices

    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'…

  • query_trade

    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'}.

  • execute_sql

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "data": {
      "type": "http",
      "url": "https://energetica.ar/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http energetica https://energetica.ar/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://energetica.ar/api/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.