Is the Avivcha Pody MCP server down?

mcp-registry/io.github.avivcha/pody-mcp · v1.0.0

healthy
Last checked 2026-10-22 23:41 UTC · handshake 138ms

As of 2026-10-22 23:41 UTC, the Avivcha Pody MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 4 minutes.

uptime (30d checks)
100%
checks observed
4,320
outages (90d)
5
tools
7

Israeli podcast & content marketplace MCP — 7 tools: studios, podcasts, glossary, industry report.

Install Avivcha Pody MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http avivcha-pody-mcp-server https://pody.io/api/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "avivcha-pody-mcp-server": {
      "type": "http",
      "url": "https://pody.io/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (65/100)

D (65/100): 0 error(s), 5 warning(s) across 7 tool(s); ~482 tokens of tool definitions.
Scores higher than 1% of 15,575 MCP servers Glimind has audited.
Its tool list costs an agent ~482 tokens per session — lighter than 90% of servers.
65 → 65 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions40
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability85
Stability36

What to fix (6)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: citation_pulse, glossary_lookup, industry_report_query, podcasts_get, podcasts_search and 2 more

6 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: glossary_lookup, industry_report_query, podcasts_get, podcasts_search, studios_get

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

Handshake + tools/list takes ~1,941 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 6 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.avivcha%2Fpody-mcp/fixes

glossary_lookup 1 change
{
  "name": "glossary_lookup",
  "description": "Look up a podcasting term definition. Returns definition + related terms + Pody URL.",
  "inputSchema": {
    "type": "object",
    "required": [
      "term"
    ],
    "properties": {
      "term": {
        "type": "string"
      },
      "language": {
        "enum": [
          "he",
          "en",
          "ar",
          "ru"
        ],
        "type": "string",
        "default": "en"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
industry_report_query 1 change
{
  "name": "industry_report_query",
  "description": "Query podcast-market figures that carry an opened primary source and date. Available metrics: youtube_podcast_users. For live studio data use studios_search.",
  "inputSchema": {
    "type": "object",
    "required": [
      "metric"
    ],
    "properties": {
      "metric": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
podcasts_get 1 change
{
  "name": "podcasts_get",
  "description": "Get full podcast profile by slug.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.avivcha/pody-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.avivcha/pody-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.avivcha%2Fpody-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.avivcha%2Fpody-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.avivcha%2Fpody-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.avivcha%2Fpody-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.avivcha%2Fpody-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.avivcha%2Fpody-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ddfc154730d13ed5…, first seen 2026-10-17, included at leaf 13645 of 48,797. Version history · verify what your client received.

Tools (7)

Compare: most reliable other servers · most reliable knowledge servers · most reliable data servers · most reliable retrieval servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

FAQ

Is the Avivcha Pody MCP server down right now?

As of 2026-10-22 23:41 UTC, the Avivcha Pody MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 4 minutes.

How many tools does Avivcha Pody MCP server provide?

Avivcha Pody MCP server advertises 7 tools, including citation_pulse, glossary_lookup, industry_report_query, podcasts_get, podcasts_search.

How do I install Avivcha Pody MCP server?

Point your MCP client at this streamable-http endpoint: https://pody.io/api/mcp

Is the Avivcha Pody MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Avivcha Pody MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve