# Newscatcherapi Catchall MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.newscatcherapi%2Fcatchall
Registry id: `mcp-registry/com.newscatcherapi/catchall`
Status: live (checked 2026-10-27T01:23:05.855Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 4961
- Outages (90 days): 1

## Install

```json
{
  "mcpServers": {
    "newscatcherapi-catchall-mcp-server": {
      "type": "http",
      "url": "https://catchall-mcp.newscatcherapi.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http newscatcherapi-catchall-mcp-server https://catchall-mcp.newscatcherapi.com/mcp
```

## Tools (61)

- `add_dataset_entities`: Add existing entities to a dataset.
- `add_project_resources`: Add one or more resources to a project. Webhooks are first-class project resources: a webhook can belong to several projects at the same time, and deleting a pr
- `append_csv_to_dataset`: Append entities from a CSV file to an existing dataset. Parses the CSV and appends its entities to the dataset. Each row must have a `name` column; include a `d
- `assign_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 deliveries.
- `check_health`: Check API health status. This tool maps to GET /health and does not require an API key.
- `continue_job`: Expand a job by processing more records beyond the initial limit. This increases the number of records the system processes (which costs additional credits). On
- `create_dataset`: Create a new dataset. Datasets are collections of entities (companies/people). Connect a dataset to a job via `submit_query(connected_dataset_ids=[...])` to nar
- `create_dataset_from_csv`: Create a new dataset by uploading a CSV file. The CSV must have at least a `name` column. For meaningful entity enrichment each row should also include a `domai
- `create_entities_batch`: Create multiple entities in one call.
- `create_entity`: Create a single entity (a company or person). ``name`` is required plus at least one identifying field: either ``description`` or ``additional_attributes.compan
- `create_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: submit a job, refin
- `create_project`: Create a new project. Projects group related resources (jobs, monitors, datasets, monitor_groups) so you can organize work and filter listings by `project_id`.
- `create_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 to attach to a monito
- `delete_dataset`: Permanently delete a dataset. The entities the dataset referenced are not deleted; only the dataset and its entity associations are removed.
- `delete_entity`: Permanently delete an entity.
- `delete_job`: Permanently delete a job and its results. Use when: - You want to remove a job you no longer need from your account.
- `delete_monitor`: Permanently delete a monitor and stop its scheduled runs. Use when: - You want to remove a monitor entirely (use `disable_monitor` to only pause it).
- `delete_project`: Delete a project. By default the project's resources (jobs, monitors, etc.) are detached but kept. Set `delete_resources=true` to also delete the contained jobs
- `delete_webhook`: Permanently delete a webhook endpoint. Use when: - You want to remove a webhook from your account.
- `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.
- `get_dataset`: Get a single dataset's details.
- `get_dataset_status`: Get the status history of a dataset (e.g. its enrichment progress over time).
- `get_entity`: Get a single entity's details.
- `get_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 -> fetching -> cluster
- `get_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) and any related deta
- `get_project`: Get a single project's details.
- `get_project_overview`: Get a project's resource overview (counts grouped by resource type and status).
- `get_user_limits`: Retrieve plan features and current usage limits for your API key. Use when: - You want to know how many records/jobs/monitors your plan allows. - You want to ch
- `get_version`: Get current API version. This tool maps to GET /version and does not require an API key.
- `get_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 ID.
- `get_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` + `resource_id` to 
- `initialize_query`: Preview suggested validators, enrichments, and date ranges before submitting. Use when: - You want to inspect/edit auto-generated validators/enrichments before 
- `list_dataset_entities`: List the entities contained in a dataset.
- `list_datasets`: List your datasets.
- `list_entities`: List your entities.
- `list_monitor_jobs`: List all jobs spawned by a monitor. Returns the history of scheduled runs for a monitor.
- `list_monitors`: List all your monitors. Returns all monitors with their schedule, status, reference query, and webhook config.
- `list_project_resources`: List the resources contained in a project.
- `list_projects`: List your projects.
- `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 which webhooks will fire 
- `list_source_groups`: List source groups (named domain allowlists). Use when: - You want to discover reusable, named sets of source domains (public groups plus any organization-visib
- `list_user_jobs`: List all jobs submitted by you. Returns your job history with IDs, queries, statuses, and timestamps.
- `list_webhook_resources`: List the resources mapped to a webhook. Use when: - You want to see which jobs/monitors a webhook is attached to.
- `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 pass to monitors (via w
- `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 over `pull_results` when
- `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 analysis or export. - Pref
- `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_results`: Retrieve the results of a job. Can be called before completion for partial results, or after completion for the full set. Returns clustered, validated, and enri
- `remove_dataset_entities`: Remove entities from a dataset (the entities themselves are not deleted).
- `remove_project_resource`: Remove a single resource from a project. This detaches the resource from the project without deleting the resource itself (e.g. removing a webhook only ends its
- `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.
- `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 user query. - You want 
- `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 attaching it to a monitor 
- `trigger_webhook`: Manually trigger webhook delivery for a resource (job/monitor/monitor_group). Use when: - You want to (re-)send a webhook delivery on demand instead of waiting 
- `update_dataset`: Update a dataset's name and/or description.
- `update_entity`: Update an entity's name, description, external_entity_id, and/or attributes.
- `update_monitor`: Update a monitor's schedule, timezone, webhook assignments, and per-run limit. Note: reference_job_id cannot be modified through this endpoint. Webhooks are cen
- `update_project`: Update a project's name and/or description. Only the fields you provide are changed.
- `update_webhook`: Update an existing webhook's configuration. Use when: - You want to change a webhook's URL, method, headers, or other settings. - You want to enable or disable 
- `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 well-formed for CatchAll

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.