Categories › Web & Browser › Web search engines & search APIs
Web search API: find every relevant event across the open web, not just the top results.
Remote server: your requests and data go to catchall-mcp.newscatcherapi.com. Claude Code: claude mcp add --transport http catchall https://catchall-mcp.newscatcherapi.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
submit_query — Create a new CatchAll processing job from a natural-language query. Use when: - You want to start a new CatchAll web research run from a useinitialize_query — Preview suggested validators, enrichments, and date ranges before submitting. Use when: - You want to inspect/edit auto-generated validatorsget_job_status — Check the status of a submitted job. Call this after submit_query to see if your job is ready. Status progression: submitted -> analyzing ->pull_results — Retrieve the results of a job. Can be called before completion for partial results, or after completion for the full set. Returns clustered,pull_job_csv — Download a job's results as a CSV file. Use when: - You want the full job output as a CSV for offline analysis or export. - Prefer this overcontinue_job — Expand a job by processing more records beyond the initial limit. This increases the number of records the system processes (which costs addlist_user_jobs — List all jobs submitted by you. Returns your job history with IDs, queries, statuses, and timestamps.delete_job — Permanently delete a job and its results. Use when: - You want to remove a job you no longer need from your account.validate_query — Check the quality of a query before submitting a job ("Check Query Quality"). Use when: - You want quick feedback on whether a query is welllist_source_groups — List source groups (named domain allowlists). Use when: - You want to discover reusable, named sets of source domains (public groups plus ancreate_monitor — Create a recurring monitor from a completed job. Monitors re-run a job's query on a schedule. Use the explore -> refine -> automate pattern:list_monitors — List all your monitors. Returns all monitors with their schedule, status, reference query, and webhook config.pull_monitor_results — Retrieve the latest results from a monitor. Returns the most recent run's results including run_info, records, and all_records.pull_monitor_csv — Download the latest monitor run's results as a CSV file. Use when: - You want the most recent monitor run output as a CSV for offline analyslist_monitor_jobs — List all jobs spawned by a monitor. Returns the history of scheduled runs for a monitor.disable_monitor — Disable a monitor to stop its scheduled runs. The monitor can be re-enabled later with enable_monitor.enable_monitor — Enable a previously disabled monitor to resume its scheduled runs.update_monitor — Update a monitor's schedule, timezone, webhook assignments, and per-run limit. Note: reference_job_id cannot be modified through this endpoidelete_monitor — Permanently delete a monitor and stop its scheduled runs. Use when: - You want to remove a monitor entirely (use `disable_monitor` to only pget_monitor_status — Get the status history of a monitor. Use when: - You want to see the timeline of a monitor's state changes (e.g. active, disabled, errored) list_webhooks — List all your webhooks. Use when: - You want to see all webhook endpoints configured in your account. - You need to find a webhook_id to pascreate_webhook — Create a new webhook endpoint. Use when: - You want to register a URL to receive job or monitor result deliveries. - You need a webhook_id tget_webhook — Retrieve the full configuration of a specific webhook. Use when: - You want to inspect a webhook's URL, method, headers, or status by its IDupdate_webhook — Update an existing webhook's configuration. Use when: - You want to change a webhook's URL, method, headers, or other settings. - You want tdelete_webhook — Permanently delete a webhook endpoint. Use when: - You want to remove a webhook from your account.test_webhook — Send a test delivery to a webhook endpoint. Use when: - You want to verify a webhook URL is reachable and correctly configured before attachassign_webhook_resource — Map a resource (job, monitor, or monitor_group) to a webhook. Use when: - You want a webhook to fire for a specific job or monitor's deliverlist_webhook_resources — List the resources mapped to a webhook. Use when: - You want to see which jobs/monitors a webhook is attached to.remove_webhook_resource — Unmap a resource from a webhook. Use when: - You want to stop a webhook from firing for a specific job or monitor.list_resource_webhooks — List the webhooks mapped to a specific resource (job/monitor/monitor_group). Use when: - You have a job or monitor ID and want to know whichget_webhook_history — Get webhook delivery history, either for a resource or for a webhook. Query in exactly one of two modes: - By resource: pass `resource_type`trigger_webhook — Manually trigger webhook delivery for a resource (job/monitor/monitor_group). Use when: - You want to (re-)send a webhook delivery on demandcreate_dataset — Create a new dataset. Datasets are collections of entities (companies/people). Connect a dataset to a job via `submit_query(connected_dataselist_datasets — List your datasets.get_dataset — Get a single dataset's details.update_dataset — Update a dataset's name and/or description.delete_dataset — Permanently delete a dataset. The entities the dataset referenced are not deleted; only the dataset and its entity associations are removed.add_dataset_entities — Add existing entities to a dataset.remove_dataset_entities — Remove entities from a dataset (the entities themselves are not deleted).list_dataset_entities — List the entities contained in a dataset.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.