Skip to content
PodLexicon logo

PodLexicon MCP server

Which MCP servers are PodLexicon'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-25

← Back to PodLexicon

Whose server it is
  • Registry namecom.podlexicon/podlexiconverified in the MCP registry

The registry name sits under podlexicon.com. 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-25
  • Stateanswerschecked 2026-10-25
  • Tools6
  • Server calls itselfPodLexicon
  • Server version1.28.1
  • Protocol version2025-06-18

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

Should an agent connect itConnect it
  • Its tools do every use case we checked: search summaries of podcast episodes by topic; query podcast summaries through the REST API.

Once connected

  • For "search summaries of podcast episodes by topic", the likely first call is search_episodes.
  • For "query podcast summaries through the REST API", the likely first call is search_episodes.
  • Parameters are untyped or undescribed in 6 of 6 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: 11, the first on 2026-10-25
  • INITE MCP score93 of 100answers 100 · does the job 100 · definitions 67 · context 100 · connects 100
  • What an agent can do with it2 of 2 use cases
  • Answered100% of days11 of 11 daily checks
  • Median first answer628 ms
  • Space in an agent's context≈ 597 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsC · 67 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 6 of 6
  • Not saying whether it only reads or can destroy: 6 of 6

What an agent can do with it

  • can do · search summaries of podcast episodes by topic
  • not sure · connect an AI agent to episode search via MCP
  • can do · query podcast summaries through the REST 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 offers6 tools · read 2026-10-25
  • search_episodes

    Find podcast episodes about a topic. Returns a ranked shortlist with a one-line hook per episode - call `get_episode_summary` to read one in full.

  • get_episode_summary

    Read an AI-generated summary of one episode. `detail` is "brief" (~400 tokens), "detailed" (~2,500 tokens), or "topics".

  • get_episode

    Get an episode's metadata: title, show, date, duration, audio URL.

  • find_similar_episodes

    Find episodes covering similar ground to a given one. Nearest-neighbour over the episodes' summary embeddings.

  • browse_catalogue

    List what PodLexicon covers. `kind` is "podcasts", "topics", or "guests". `query` filters by name.

  • get_episodes_by

    List the episodes belonging to one podcast, topic, or guest. `kind` is "podcast", "topic", or "guest"; `slug` comes from `browse_catalogue`.

How to connect

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

{
  "mcpServers": {
    "podlexicon": {
      "type": "http",
      "url": "https://podlexicon.com/mcp/"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http podlexicon https://podlexicon.com/mcp/

Add to CursorAdd to VS Code

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