Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PodMule

REMOTE · APP.PODMULE.COM · SCANNED SEP 21

Search, draft and manage your podcast workspace from your agent.

Available components

+1 this week 89 Trust /100
Trust breakdown (7 categories)

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 Security97
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 532 tokens (~177/item across 3 items; 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 4 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
Install

How do I install the PodMule MCP server?

PodMule is a hosted endpoint at https://app.podmule.com/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 · app.podmule.com

# add to Claude Code
claude mcp add --transport http com-podmule-podmule 'https://app.podmule.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-podmule-podmule": {
      "url": "https://app.podmule.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-podmule-podmule": {
      "type": "http",
      "url": "https://app.podmule.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-podmule-podmule]
url = "https://app.podmule.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-podmule-podmule": {
      "type": "remote",
      "url": "https://app.podmule.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-podmule-podmule --url 'https://app.podmule.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-podmule-podmule:
    url: "https://app.podmule.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-podmule-podmule": {
      "Transport": "http",
      "Url": "https://app.podmule.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-podmule-podmule -t streamable-http -u 'https://app.podmule.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-podmule-podmule": {
      "type": "http",
      "url": "https://app.podmule.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 21 Sept 2026 · Probed https://app.podmule.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.podmule.com CN=YR1,O=Let's Encrypt,C=US 10 Sept 2026 9 Dec 2026 RSA 2048 SHA256-RSA 553ec9e374566b18eec06a4715385ae2a7a
SANs: app.podmule.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.podmule.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
podmule.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", resource_metadata="https://app.podmule.com/.well-known/oauth-protected-resource/mcp"

Bearer error="invalid_token", resource_metadata="https://app.podmule.com/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://va.vercel-scripts.com; style-src 'self' 'unsafe-inline'; img-src 'self' blob: data: https://*.squaredlemons.com https://*.podmule.com https://*.widowedaf.com https://*.ytimg.com https://*.ggpht.com; media-src 'self' https: blob: data:; connect-src 'self' https://*.squaredlemons.com https://*.podmule.com https://*.widowedaf.com https://*.r2.cloudflarestorage.com https://va.vercel-scripts.com https://*.sentry.io https://*.ingest.sentry.io; font-src 'self' data:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests; block-all-mixed-content
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=(), payment=(), usb=(), bluetooth=(), accelerometer=(), gyroscope=(), magnetometer=()

Protected resource metadata

Document https://app.podmule.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://app.podmule.com/mcp
Authorisation server https://app.podmule.com/api/auth

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.podmule.com/mcp Verified 200
http (plaintext) http://app.podmule.com/mcp HTTPS enforced 301 https://app.podmule.com/mcp
MCP tools · 3 exposed · ~263 tokens

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 →

Tool Tokens
ask_podmule ~100

Ask PodMule for a concise read-only domain answer or an advisory route plan. Use this for quick questions, summaries, diagnostics, drafting, "what should I do?" prompts, and ambiguous action requests. This tool never performs writes. For exact capability contracts use search; for one selected action (read or write) use execute.

NameTypeReqDescription
contextobject
requeststringyes
response_formatstring
NameTypeReqDescription
answerstring
citationsarray
errorobject
linksarray
routeobject
statusstringyes
suggested_actionsarray

No examples provided.

execute ~96

Execute one OAuth-visible PodMule capability. Reads run directly. Modern MCP 2026 clients with MRTR support may preview and affirm the allowlisted update_episode pilot; legacy clients and every other MCP write remain read-only. Dangerous writes are always blocked — do those in the PodMule app. Use ask_podmule for ambiguous requests and search for exact schemas.

NameTypeReqDescription
inputobject
namestringyes
NameTypeReqDescription
errorobject
invocation_id
linksarray
result
statusstringyes
writes_enabledbooleanyes

No examples provided.

search ~67

Search available PodMule capabilities for this OAuth token. Use this when you need the exact capability name or schema before calling execute. For ambiguous domain requests, call ask_podmule first.

NameTypeReqDescription
detailstring
limitinteger
querystring
NameTypeReqDescription
matchesarrayyes
totalintegeryes
writes_enabledbooleanyes

No examples provided.

Common questions

What is the PodMule MCP server?

PodMule is an MCP server listed in the public MCP registry as com.podmule/podmule. Search, draft and manage your podcast workspace from your agent. This page covers its hosted endpoint (https://app.podmule.com/mcp).

Is the PodMule MCP server safe to use?

PodMule scores 89 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 PodMule MCP server expose?

PodMule exposes 3 tools: ask_podmule, search, execute. Their descriptions and schemas cost roughly 263 tokens of context every time the server is loaded.

Does the PodMule MCP server require authentication?

Yes. PodMule asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the PodMule MCP server still maintained?

PodMule is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.