_ registry / mcp http-sse · checked 1h ago

energetica-data

https://energetica.ar

Registry code: fe15b0314ce8bf46

api record

Argentine oil & gas data — 40+ curated tables: production, wells, prices, investments, trade.

from a public catalogue that lists it, not from the operator

endpoint
https://energetica.ar/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is energetica-data live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is energetica-data free to use?
Yes — the hub reached it with no key and no payment.
What tools does energetica-data have?
8 tools: execute_sql, query_prices, query_wells, query_trade, query_investments, query_production, get_schema, get_data_freshness.
Is energetica-data safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
973ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 638 checks · signed record
  • degraded → live
_ what it is for
topic
energy & utilities oil & gas
used for
  • query argentine oil and gas production
  • search oil and gas wells
  • query energy prices
  • query hydrocarbon trade data
  • run sql on energy data
takes → gives
text → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
6 open 2 never probed 6 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • query_wells reads open 18h ago

    Search and filter Argentine oil & gas wells. Returns well location, type, status, cumulative production, and technical data. ~50,000 wells available.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "number",
      "maximum": 1000,
      "minimum": 1,
      "description": "Max results, default 100"
    },
    "cuenca": {
      "type": "string",
      "description": "Basin filter (NEUQUINA, GOLFO SAN JORGE, etc.)"
    },
    "empresa": {
      "type": "string",
      "description": "Operating company filter"
    },
    "formacion": {
      "type": "string",
      "description": "Geological formation"
    },
    "provincia": {
      "type": "string",
      "description": "Province filter (NEUQUEN, CHUBUT, MENDOZA, etc.)"
    },
    "tipo_estado": {
      "type": "string",
      "description": "Well status (e.g. Activo, Inactivo, Abandonado)"
    },
    "tipo_recurso": {
      "enum": [
        "PETROLEO",
        "GAS",
        "AMBOS"
      ],
      "type": "string",
      "description": "Resource type"
    },
    "con_produccion": {
      "type": "boolean",
      "description": "Only wells with cumulative production > 0"
    }
  }
}
    arguments 45 lines
  • query_trade reads open 18h ago

    Query Argentina hydrocarbon trade balance (exports/imports). Covers crude oil (HS 2709), refined products (HS 2710), and natural gas (HS 2711). Values in FOB USD.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "anio": {
      "type": "number",
      "description": "Filter by year"
    },
    "flow": {
      "enum": [
        "export",
        "import"
      ],
      "type": "string",
      "description": "Trade flow direction"
    },
    "producto": {
      "enum": [
        "crude",
        "refined",
        "gas"
      ],
      "type": "string",
      "description": "Product category"
    }
  }
}
    arguments 27 lines
  • query_investments reads open 9h ago

    Query upstream oil & gas investments in Argentina by company, basin, and year. Data includes drilling, completion, and infrastructure expenditure in millions USD.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "cuenca": {
      "type": "string",
      "description": "Basin filter"
    },
    "empresa": {
      "type": "string",
      "description": "Company filter"
    },
    "concepto": {
      "type": "string",
      "description": "Investment concept (e.g. perforacion, terminacion, infraestructura)"
    },
    "anio_desde": {
      "type": "number",
      "description": "Start year"
    },
    "anio_hasta": {
      "type": "number",
      "description": "End year"
    }
  }
}
    arguments 26 lines
  • query_production reads open 9h ago

    Query monthly oil, gas, and water production data from Argentine hydrocarbon wells. Data covers 2006-present with ~18M records. Can be filtered and grouped by basin, company, geological formation, and time period.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "cuenca": {
      "type": "string",
      "description": "Basin name filter (e.g. NEUQUINA, GOLFO SAN JORGE, CUYANA, AUSTRAL, NOROESTE)"
    },
    "empresa": {
      "type": "string",
      "description": "Operating company filter (e.g. YPF, PAN AMERICAN ENERGY, VISTA, TECPETROL)"
    },
    "recurso": {
      "enum": [
        "petroleo",
        "gas",
        "agua",
        "todos"
      ],
      "type": "string",
      "description": "Resource type filter. Default: todos"
    },
    "formacion": {
      "type": "string",
      "description": "Geological formation filter (e.g. VACA MUERTA, D-129, CENTENARIO)"
    },
    "agrupar_por": {
      "enum": [
        "mes",
        "anio",
        "cuenca",
        "empresa",
        "formacion"
      ],
      "type": "string",
      "description": "Group results by dimension. Default: mes"
    },
    "fecha_desde": {
      "type": "string",
      "description": "Start date YYYY-MM (e.g. 2020-01)"
    },
    "fecha_hasta": {
      "type": "string",
      "description": "End date YYYY-MM (e.g. 2025-12)"
    }
  }
}
    arguments 47 lines
  • get_schema reads open 18d ago

    Get the database schema and metadata. Returns table names, columns, types, descriptions, units, and example values. Use this to understand what data is available before querying.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "tabla": {
      "type": "string",
      "description": "Specific table name. Omit to get all tables."
    }
  }
}
    arguments 10 lines
  • get_data_freshness reads open 17d ago

    Get the latest data available in each table — last period, date range, and total records. Use this to understand how current the data is.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • execute_sql reads unknown never probed

    Execute arbitrary read-only SQL against the DuckDB database. Only SELECT and WITH statements are allowed. Use get_schema first to understand available tables and columns. Available on Professional tier and above.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "sql"
  ],
  "properties": {
    "sql": {
      "type": "string",
      "description": "SQL query (SELECT or WITH only)"
    }
  }
}
    arguments 13 lines
  • query_prices reads unknown 9h ago

    Query international and local energy prices. Includes WTI, Brent, Henry Hub (daily), Argentine crude prices (Escalante, Medanito), and exchange rates (official, blue, MEP, CCL).

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "serie"
  ],
  "properties": {
    "serie": {
      "enum": [
        "WTI",
        "BRENT",
        "HENRY_HUB",
        "ESCALANTE",
        "MEDANITO",
        "USD_OFICIAL",
        "USD_BLUE",
        "USD_MEP",
        "USD_CCL"
      ],
      "type": "string",
      "description": "Price series to query"
    },
    "frecuencia": {
      "enum": [
        "diario",
        "mensual",
        "anual"
      ],
      "type": "string",
      "description": "Frequency aggregation. Default: diario for intl prices, mensual for local"
    },
    "fecha_desde": {
      "type": "string",
      "description": "Start date YYYY-MM-DD"
    },
    "fecha_hasta": {
      "type": "string",
      "description": "End date YYYY-MM-DD"
    }
  }
}
    arguments 41 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id fe15b0314ce8bf46.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fe15b0314ce8bf46/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fe15b0314ce8bf46/badge.svg)](https://brick.blue/agent/fe15b0314ce8bf46?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.