CatchAll (by NewsCatcher)
OfficialRelated Servers
Alternatives to CatchAll (by NewsCatcher)
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables natural-language event searches through Google Events, returning structured JSON with dates, venues, ticket links, and map details, plus support for localization, filters, and pagination.2-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to browse public event listings from explore pages and fetch full detail for a single event — titles, descriptions, times, locations, host display names, and aggregate RSVP counts — across eight supported city regions. Keyless and read-only, with no guest lists, contact info, or authentication required.73 npmMIT

OpenSERPofficial
AlicenseAqualityBmaintenanceLive search on six engines (Google, Bing, Yandex, Baidu, DuckDuckGo, Ecosia), image search and single/batch page extraction for AI agents. Keeps source engine and rank. Runs against a self-hosted OpenSERP server or OpenSERP Cloud.810246 npm3MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search event calendars by keyword and list upcoming or date-filtered events from a chosen calendar, returning titles, dates, venues, coordinates, and keywords.9 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search public Luma events near a geographic coordinate within a time window and fetch full public details for a single event. Results are returned as provider-neutral open event records with attendee data stripped, and read-only access keeps registration on the official event page.MIT
- FlicenseBqualityDmaintenanceEnables querying and retrieving structured event data from the Informa Connect event directory, with support for various filters, pagination, and speaker extraction.9-
TDQS
Scored across 60 tools
Most tools have distinct purposes, and descriptions clearly differentiate similar ones (e.g., initialize_query vs submit_query, pull_results vs pull_monitor_results). However, the high number of tools (60) may cause some confusion, especially for webhook and resource mapping tools.
Tool names generally follow a verb_noun pattern, but the verbs are inconsistent (pull, get, list, check) and there is a mix of 'list' and 'get' for similar retrieval operations. While readable, the pattern is not uniform.
With 60 tools, the surface is very large for an MCP server. Although the domain (news monitoring with datasets, entities, projects, monitors, webhooks) might justify the number, many CRUD operations could be consolidated to reduce cognitive load.
The tool set covers the full lifecycle: job submission, monitoring, webhooks, datasets, entities, projects, and health. All major CRUD operations are present, and there are no obvious gaps for the stated purpose.