Jupiter Broadcasting Podcast Data MCP Server
Related Servers
Alternatives to Jupiter Broadcasting Podcast Data MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP hosts to search public job listings from tt3labs.com by keyword, location, remote preference, and posting date, then fetch details and apply URLs for individual postings. It wraps the board's public API/RSS as read-only, host-neutral tools usable from Cursor, Claude, Codex, and similar agents.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI hosts to search and retrieve remote Java job listings from remotejavajobs.com, which offers no official seeker API, RSS feed, or seeker MCP. Supports keyword, location, remote-only, and date filtering for job search, plus fetching full detail and apply URLs for individual postings.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search a public job board by keyword, location, remote preference, and posting date, then fetch full details and apply links for individual listings. It wraps the board's public API/RSS as read-only stdio tools usable from any MCP host.MIT
- AlicenseNot gradedqualityCmaintenanceEnables any MCP host to search job postings on hashtagweb3.com by keyword, location, remote preference, and posting date, and to fetch full details for a specific listing. It exposes the board's public API/RSS as the read-only, rate-limited tools search_jobs and get_job.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search Web3 job listings and retrieve job details through the web3jobs.io public API/RSS, supporting keyword, location, remote-only, and date filters.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agent hosts to search and retrieve job listings from a public job board via standard MCP tools, supporting keyword, location, remote, date, and limit filters plus job detail lookup by URL.MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_episode retrieves metadata for a specific episode, get_transcript fetches the transcript text, list_shows enumerates available shows, and search_episodes performs filtered searches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent verb_noun naming pattern (get_episode, get_transcript, list_shows, search_episodes). The verbs are appropriate and descriptive, and the snake_case style is uniformly applied throughout the tool set.
With 4 tools, the server is well-scoped for podcast data retrieval, covering key operations like listing shows, searching episodes, and fetching episode details and transcripts. However, it might benefit from additional tools for broader podcast management (e.g., update or delete operations), but the count is reasonable for the stated purpose.
The tool set provides comprehensive read-only access to podcast data, including listing shows, searching episodes, and retrieving episode metadata and transcripts. Minor gaps exist, such as the lack of create, update, or delete operations, but for a data retrieval server, the coverage is solid and allows agents to perform essential queries without dead ends.