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

podmule-mcp

https://app.podmule.com

Registry code: b6ca8c0efda94341

api record

PodMule gives you read and write access to a podcast workspace: shows, episodes, transcripts, knowledge pages, clips, contacts, interviews and campaigns.

How to work with it:

endpoint
https://app.podmule.com/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 podmule-mcp live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is podmule-mcp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does podmule-mcp have?
3 tools: search, ask_podmule, execute.
Is podmule-mcp 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
157ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 329 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
productivity & business
used for
  • search podcast episodes and transcripts
  • manage a podcast workspace
  • ask questions about podcast content
takes → gives
text, data → data, text
tools
2 reads1 changes data
_ 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 3 tools
3 auth-required 3 of 3 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.

  • search reads auth-required 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
    },
    "detail": {
      "enum": [
        "summary",
        "schema"
      ],
      "type": "string"
    }
  }
}
    arguments 23 lines
  • ask_podmule reads auth-required 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "request"
  ],
  "properties": {
    "context": {
      "type": "object",
      "properties": {
        "show_id": {
          "type": "string",
          "maxLength": 160,
          "minLength": 1
        },
        "timeframe": {
          "type": "string",
          "maxLength": 160,
          "minLength": 1
        },
        "contact_id": {
          "type": "string",
          "maxLength": 160,
          "minLength": 1
        },
        "episode_id": {
          "type": "string",
          "maxLength": 160,
          "minLength": 1
        },
        "conversation_id": {
          "type": "string",
          "maxLength": 160,
          "minLength": 1
        },
        "organization_id": {
          "type": "string",
          "maxLength": 160,
          "minLength": 1
        }
      }
    },
    "request": {
      "type": "string",
      "maxLength": 4000,
      "minLength": 1
    },
    "response_format": {
      "enum": [
        "answer",
        "route_plan",
        "json"
      ],
      "type": "string"
    }
  }
}
    arguments 57 lines
  • execute changes data auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 160,
      "minLength": 1
    },
    "input": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  }
}
    arguments 21 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 b6ca8c0efda94341.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b6ca8c0efda94341/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/b6ca8c0efda94341/badge.svg)](https://brick.blue/agent/b6ca8c0efda94341?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
70%

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.