Skip to content
Energy Podcast Digest logo

Energy Podcast Digest MCP server

Which MCP servers are Energy Podcast Digest's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-21

← Back to Energy Podcast Digest

Whose server it is
  • Registry nameio.energypod/energypodverified in the MCP registry

The registry name sits under energypod.io. 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-21
  • Stateanswerschecked 2026-10-21
  • Tools5
  • Server calls itselfenergypod.io
  • Server version1.1.0
  • Protocol version2025-06-18

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

Should an agent connect itConnect it
  • Its tools do every use case we checked: Read weekly digests of energy podcast episodes; Search past digests and episodes for specific energy topics.

Once connected

  • For "Read weekly digests of energy podcast episodes", the likely first call is list_digests.
  • For "Search past digests and episodes for specific energy topics", the likely first call is search.

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: 7, the first on 2026-10-21
  • INITE MCP score100 of 100answers 100 · does the job 100 · definitions 100 · context 100 · connects 100
  • What an agent can do with it2 of 2 use cases
  • Answered100% of days7 of 7 daily checks
  • Median first answer108 ms
  • Space in an agent's context≈ 910 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results5 of 5 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Read weekly digests of energy podcast episodes
  • can do · Search past digests and episodes for specific energy topics
  • not sure · Connect an AI agent to digest data through the API

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 (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). 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 offers5 tools · read 2026-10-21
  • list_digests

    Newest-first list of every published energypod.io edition (weekly energy-industry digests): slug (YYYY-MM-DD), week label, and episode count. Call this FIRST — the first entry is the latest week, and its slug feeds get_digest /…

  • get_digest

    Full briefing markdown + metadata for one edition. ``slug`` is the YYYY-MM-DD edition date from list_digests; omitting it returns the LATEST edition. The payload also carries ``export_html_url`` and ``export_pdf_url`` — pregenerated…

  • list_digest_episodes

    The episodes a given edition references (title + show + published date + episode ids) — the cheapest way to map a week. Omitting ``slug`` returns the latest edition's episodes. Pass ``region`` for a region's reading list (the regional…

  • get_episode

    One episode's title, show, summary, and full transcript. Scoped to episodes referenced by a published digest. Pass ``digest`` when an episode spans more than one week. Pass ``lang`` (es / zh) for the episode's translated title, summary…

  • search

    Typo-tolerant search across digests, episodes, people, companies, and channels (same ranking + excerpts as the site's /search). Use for ad-hoc discovery when you don't know which edition or episode id you need.

How to connect

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

{
  "mcpServers": {
    "energypod": {
      "type": "http",
      "url": "https://energypod.io/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http energypod https://energypod.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://energypod.io/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.