Skip to main content
Glama
CatchAll (by NewsCatcher)

CatchAll (by NewsCatcher)

Official

Newscatcher CatchAll MCP Server

MCP server for the NewsCatcher CatchAll Web Search API.

Quick Start — Use Our Hosted Server

You don't need to clone or run this repo to use the MCP — NewsCatcher runs a hosted instance:

https://catchall-mcp.newscatcherapi.com/mcp?apiKey=YOUR_CATCHALL_API_KEY

Get a CatchAll API key at platform.newscatcherapi.com, then connect:

{
  "mcpServers": {
    "catchall": {
      "type": "http",
      "url": "https://catchall-mcp.newscatcherapi.com/mcp?apiKey=YOUR_CATCHALL_API_KEY"
    }
  }
}

Or via Claude Code CLI:

claude mcp add --transport http catchall "https://catchall-mcp.newscatcherapi.com/mcp?apiKey=YOUR_CATCHALL_API_KEY"

Full integration docs: https://www.newscatcherapi.com/docs/web-search-api/integrations/mcp

Prefer to run the server yourself (locally or self-hosted)? See Running below.

Related MCP server: Apify-Google-Events-API

Tool To Endpoint Mapping

Jobs

MCP Tool

Method

Endpoint

initialize_query

POST

/catchAll/initialize

submit_query

POST

/catchAll/submit

validate_query

POST

/catchAll/validate

continue_job

POST

/catchAll/continue

list_user_jobs

GET

/catchAll/jobs/user

get_job_status

GET

/catchAll/status/{job_id}

pull_results

GET

/catchAll/pull/{job_id}

pull_job_csv

GET

/catchAll/pull/{job_id}/csv

delete_job

DELETE

/catchAll/jobs/{job_id}

Job listing filters: list_user_jobs supports search, ownership, project_id, and mode (base or lite) filters in addition to page/page_size.

Monitors

MCP Tool

Method

Endpoint

create_monitor

POST

/catchAll/monitors/create

update_monitor

PATCH

/catchAll/monitors/{monitor_id}

delete_monitor

DELETE

/catchAll/monitors/{monitor_id}

list_monitors

GET

/catchAll/monitors/

list_monitor_jobs

GET

/catchAll/monitors/{monitor_id}/jobs

get_monitor_status

GET

/catchAll/monitors/{monitor_id}/status

pull_monitor_results

GET

/catchAll/monitors/pull/{monitor_id}

pull_monitor_csv

GET

/catchAll/monitors/pull/{monitor_id}/csv

enable_monitor

POST

/catchAll/monitors/{monitor_id}/enable

disable_monitor

POST

/catchAll/monitors/{monitor_id}/disable

Webhooks

MCP Tool

Method

Endpoint

list_webhooks

GET

/catchAll/webhooks

create_webhook

POST

/catchAll/webhooks

get_webhook

GET

/catchAll/webhooks/{webhook_id}

update_webhook

PATCH

/catchAll/webhooks/{webhook_id}

delete_webhook

DELETE

/catchAll/webhooks/{webhook_id}

test_webhook

POST

/catchAll/webhooks/{webhook_id}/test

assign_webhook_resource

POST

/catchAll/webhooks/{webhook_id}/resources

list_webhook_resources

GET

/catchAll/webhooks/{webhook_id}/resources

remove_webhook_resource

DELETE

/catchAll/webhooks/{webhook_id}/resources/{resource_type}/{resource_id}

list_resource_webhooks

GET

/catchAll/resources/{resource_type}/{resource_id}/webhooks

get_webhook_history

GET

/catchAll/webhook-history

trigger_webhook

POST

/catchAll/webhook/trigger/{resource_type}/{resource_id}

Webhook notes: create_webhook accepts an optional project_id to attach the webhook to a project on creation. list_webhooks also accepts an optional project_id to filter to webhooks belonging to a specific project. get_webhook_history queries in one of two modes — pass resource_type + resource_id for a job/monitor/monitor_group's deliveries, or pass webhook_id for everything delivered through one webhook (exactly one mode per call). Manual test deliveries (test_webhook) only appear in webhook mode and are recorded with resource_type: "test".

Projects

MCP Tool

Method

Endpoint

create_project

POST

/catchAll/projects/

list_projects

GET

/catchAll/projects/

get_project

GET

/catchAll/projects/{project_id}

update_project

PATCH

/catchAll/projects/{project_id}

delete_project

DELETE

/catchAll/projects/{project_id}

get_project_overview

GET

/catchAll/projects/{project_id}/overview

add_project_resources

POST

/catchAll/projects/{project_id}/resources

list_project_resources

GET

/catchAll/projects/{project_id}/resources

remove_project_resource

DELETE

/catchAll/projects/{project_id}/resources/{resource_type}/{resource_id}

Project resources: resource_type is one of job, monitor, dataset, monitor_group, or webhook. A webhook can belong to several projects at once. delete_project with delete_resources=true deletes the contained jobs, monitors, datasets, and monitor groups, but webhooks are only detached — never deleted — and the response's deleted_resources reports them under a webhook_unlinked count.

Datasets

MCP Tool

Method

Endpoint

create_dataset

POST

/catchAll/datasets/

list_datasets

GET

/catchAll/datasets/

get_dataset

GET

/catchAll/datasets/{dataset_id}

update_dataset

PATCH

/catchAll/datasets/{dataset_id}

delete_dataset

DELETE

/catchAll/datasets/{dataset_id}

add_dataset_entities

POST

/catchAll/datasets/{dataset_id}/entities

remove_dataset_entities

DELETE

/catchAll/datasets/{dataset_id}/entities

list_dataset_entities

POST

/catchAll/datasets/{dataset_id}/entities/list

get_dataset_status

GET

/catchAll/datasets/{dataset_id}/status

create_dataset_from_csv

POST

/catchAll/datasets/upload

append_csv_to_dataset

POST

/catchAll/datasets/{dataset_id}/upload

CSV uploads (v1.6.1): create_dataset_from_csv and append_csv_to_dataset take the CSV content in the file parameter — raw CSV text or standard base64. They never read a path from the server's filesystem, so they stay safe on a remote/hosted MCP. Inline CSV content is capped at a hard 10 MB (after base64 decoding). create_dataset_from_csv also accepts the new optional project_id field.

Entities

MCP Tool

Method

Endpoint

create_entity

POST

/catchAll/entities/

list_entities

GET

/catchAll/entities/

create_entities_batch

POST

/catchAll/entities/batch

get_entity

GET

/catchAll/entities/{entity_id}

update_entity

PATCH

/catchAll/entities/{entity_id}

delete_entity

DELETE

/catchAll/entities/{entity_id}

external_entity_id (v1.6.3): create_entity and update_entity accept an optional external_entity_id string — a customer-supplied identifier that links the entity to a record in an external system. project_id (v1.8.0): list_entities accepts an optional project_id to filter to entities belonging to a specific project.

Source Groups

MCP Tool

Method

Endpoint

list_source_groups

GET

/catchAll/source-groups

Source groups (v1.8.0): named, reusable domain allowlists (public groups plus any organization-visibility groups your organization can access). list_source_groups returns each group's slug, name, and description. submit_query accepts an optional source_groups list of slugs (max 20 per job) that scopes fetching to those domain allowlists. The attached groups are echoed back as source_groups in the job status and results.

User & Meta

MCP Tool

Method

Endpoint

get_user_limits

POST

/catchAll/user/limits

check_health

GET

/health

get_version

GET

/version

Authentication

API key precedence (highest to lowest):

  1. api_key tool parameter

  2. x-api-key request header

  3. Authorization: Bearer <key> request header

  4. URL query parameter ?apiKey=...

  5. CATCHALL_API_KEY environment variable

check_health and get_version do not require API key auth.

Hosted deployment (FastMCP Gateway)

When deployed via fastmcp.app, a stateless gateway sits in front of the server. The gateway forwards HTTP headers to the backend but not URL query parameters. Use the x-api-key header or CATCHALL_API_KEY environment variable instead of ?apiKey=.

Claude Code / Cursor:

{
  "mcpServers": {
    "catchall": {
      "type": "http",
      "url": "https://YOUR-DEPLOYMENT.fastmcp.app/mcp",
      "headers": { "x-api-key": "YOUR_API_KEY" }
    }
  }
}

Or via CLI:

claude mcp add --transport http catchall "https://YOUR-DEPLOYMENT.fastmcp.app/mcp" \
  --header "x-api-key: YOUR_API_KEY"

Direct server access (no gateway): ?apiKey=YOUR_KEY in the URL still works.

Core Workflow (Jobs)

  1. Optional: call initialize_query to preview validators/enrichments/date window.

  2. initialize_query is preview-only (it does not create a job) and suggestions are non-deterministic.

  3. Submit with submit_query (query required). You can send only query; omitted optional fields are auto-selected/generated.

  4. Optional fields are independent: provide any subset (for example, custom validators only), omitted ones are still auto-generated.

  5. start_date/end_date filter web page discovery dates, not event dates in extracted content.

  6. For event-time accuracy, use event-focused validators/enrichments and verify event_date in pulled results.

  7. Poll get_job_status: first check after ~1-2 minutes, then every 30-60 seconds, stop on completed or failed.

  8. Pull with pull_results; partial data appears during enriching.

  9. Paginate while page < total_pages to retrieve all available records.

  10. Use continue_job only to process more records (cost-affecting). It applies only to jobs originally submitted with limit.

  11. continue_job.new_limit is optional; if omitted, API defaults to your plan maximum.

  12. page/page_size/total_pages represent already-available records; use progress_validated < candidate_records to detect if more records may still appear.

Limit vs Page Size

  • limit (submit_query, continue_job) controls how many records are processed and therefore affects cost. If provided, must be >= 10. Omit to retrieve everything up to your plan's maximum.

  • page_size (pull_results, list_user_jobs) controls pagination only and does not affect processing cost.

  • pull_results.page_size default is 100.

  • page_size range is 1..1000.

  • pull_results response includes error (failed jobs) and limit (applied job limit).

API-Enforced Monitor Constraints

  • create_monitor.backfill=true: reference job end_date must be within the last 7 days.

  • create_monitor.backfill=false: reference job age constraint does not apply.

  • Monitor minimum schedule frequency depends on plan.

  • create_monitor supports optional limit (minimum 10), backfill (default true), timezone, webhook_ids, and project_id.

  • Webhooks are centralized in v1.5.3: register them with create_webhook, then attach by ID via create_monitor.webhook_ids / update_monitor.webhook_ids (no inline webhook config).

  • Monitors are only supported for base jobs (not lite).

  • enable_monitor supports optional backfill.

  • update_monitor updates webhook_ids, run limit, schedule, and/or timezone (pass webhook_ids=[] to clear assignments; timezone is ignored unless schedule is also set).

  • list_monitors supports pagination via page and page_size plus search, ownership, and project_id filters; it returns total, page, page_size, total_pages, monitors.

Enrichment Output Notes

  • enrichment.enrichment_confidence is always present.

  • Company enrichments are structured objects with:

    • source_text

    • confidence

    • metadata.name

    • metadata.domain_url

    • metadata.domain_url_confidence

Error Handling

Tools return:

  • Pretty JSON string on success.

  • (v1.8.0) An MCP tool error (isError=True) for any upstream non-2xx response (bad api_key, invalid/foreign project_id, not-found ids, validation failures, etc.) or unhandled exception. The error message carries the upstream status code and message, for example API Error (401): Api key not found. Before v1.8.0, tools swallowed these failures and returned a plain "Error: ..." string as a successful tool result — clients checking only isError would see a false success. That has been fixed: every tool now raises a ToolError instead of returning an error string, so failures are always reported as real tool errors.

Running

Install dependencies:

pip install -r requirements.txt

Run over stdio:

python server.py

Run over HTTP (if fastmcp CLI is available):

fastmcp run server.py:mcp --transport streamable-http --host 0.0.0.0 --port 8000

Available Tools

60 tools
add_dataset_entitiesCInspect

Add existing entities to a dataset.

Inputs: dataset_id (required), entity_ids (required), api_key. Returns: result

add_project_resourcesCInspect

Add one or more resources to a project.

Inputs: resources (required), project_id (required), api_key. Returns: result

append_csv_to_datasetAInspect

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 domain or description column (or both) for meaningful enrichment. Duplicate rows (by name) are skipped. To create a new dataset from a CSV, use create_dataset_from_csv instead.

Inputs: file (required), dataset_id (required), api_key. Returns: result

assign_webhook_resourceAInspect

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.

Inputs: webhook_id (required), resource_id (required), resource_type (required), api_key. Returns: result

check_healthAInspect

Check API health status.

This tool maps to GET /health and does not require an API key.

Inputs: api_key. Returns: result

continue_jobAInspect

Expand a job by processing more records beyond the initial limit.

This increases the number of records the system processes (which costs additional credits). Only use this when the user wants MORE data processed.

This only applies to jobs originally submitted with limit. If a job was submitted without limit, there is nothing to continue. The new_limit must be greater than the previous limit when provided. If omitted, API defaults to your plan maximum.

Inputs: job_id (required), api_key, new_limit. Returns: result

create_datasetAInspect

Create a new dataset.

Datasets are collections of entities (companies/people). Connect a dataset to a job via submit_query(connected_dataset_ids=[...]) to narrow retrieval scope.

Inputs: name (required), api_key, entity_ids, project_id, +1 more. Returns: result

create_dataset_from_csvAInspect

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 domain column or a description column (or both) — a row with only a name is accepted but produces lower-quality enrichment. Additional columns are mapped to entity attributes. Max file size is plan-dependent. To add CSV rows to an existing dataset, use append_csv_to_dataset instead.

Inputs: file (required), name (required), api_key, project_id, +1 more. Returns: result

create_entities_batchBInspect

Create multiple entities in one call.

Inputs: entities (required), api_key. Returns: result

create_entityAInspect

Create a single entity (a company or person).

name is required plus at least one identifying field: either description or additional_attributes.company_attributes.domain.

Inputs: name (required), api_key, description, entity_type, +2 more. Returns: result

create_monitorAInspect

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, refine until results match, then create a monitor.

The schedule is defined in natural language (e.g., 'every day at 9 AM EST'). Always include a timezone (in the schedule text or via the timezone arg). API-enforced constraints apply:

  • If backfill=true, reference job end_date must be within the last 7 days

  • If backfill=false, reference job age does not matter

  • Minimum schedule frequency depends on your plan

Webhooks are now centralized: register them with create_webhook, then pass their IDs here via webhook_ids (there is no inline webhook config anymore).

Inputs: schedule (required), reference_job_id (required), limit, api_key, +4 more. Returns: result

create_projectAInspect

Create a new project.

Projects group related resources (jobs, monitors, datasets, monitor_groups) so you can organize work and filter listings by project_id.

Inputs: name (required), api_key, description. Returns: result

create_webhookAInspect

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 monitor (via webhook_ids) or a job submission.

Inputs: url (required), name (required), auth, type, +6 more. Returns: result

delete_datasetAInspect

Permanently delete a dataset.

The entities the dataset referenced are not deleted; only the dataset and its entity associations are removed.

Inputs: dataset_id (required), api_key. Returns: result

delete_entityBInspect

Permanently delete an entity.

Inputs: entity_id (required), api_key. Returns: result

delete_jobAInspect

Permanently delete a job and its results.

Use when:

  • You want to remove a job you no longer need from your account.

Inputs: job_id (required), api_key. Returns: result

delete_monitorAInspect

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).

Inputs: monitor_id (required), api_key. Returns: result

delete_projectAInspect

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 resources.

Inputs: project_id (required), api_key, delete_resources. Returns: result

delete_webhookAInspect

Permanently delete a webhook endpoint.

Use when:

  • You want to remove a webhook from your account.

Inputs: webhook_id (required), api_key. Returns: result

disable_monitorAInspect

Disable a monitor to stop its scheduled runs.

The monitor can be re-enabled later with enable_monitor.

Inputs: monitor_id (required), api_key. Returns: result

enable_monitorAInspect

Enable a previously disabled monitor to resume its scheduled runs.

Inputs: monitor_id (required), api_key, backfill. Returns: result

get_datasetBInspect

Get a single dataset's details.

Inputs: dataset_id (required), api_key. Returns: result

get_dataset_statusAInspect

Get the status history of a dataset (e.g. its enrichment progress over time).

Inputs: dataset_id (required), api_key. Returns: result

get_entityAInspect

Get a single entity's details.

Inputs: entity_id (required), api_key. Returns: result

get_job_statusAInspect

Check the status of a submitted job.

Call this after submit_query to see if your job is ready. Status progression: submitted -> analyzing -> fetching -> clustering -> enriching -> completed/failed

IMPORTANT: Jobs take several minutes to process. First check after ~1-2 minutes, then poll every 30-60 seconds. Broad searches can take 10-30+ minutes; for long jobs, poll every 60-120 seconds. Do NOT call this tool in a tight loop. Stop polling when status is completed or failed. Treat submitted, analyzing, fetching, clustering, and enriching as active states and continue polling.

You don't need to wait for completion to pull results. Partial results are available during enriching — call pull_results after ~2 minutes, then poll status every 30-60 seconds and pull again for fresher results. Do not stop pulling just because an intermediate pull is empty/unchanged. Use progress_validated vs candidate_records to track whether more results may still appear (progress_validated < candidate_records). If transport/session fails, resume using the same job_id.

Inputs: job_id (required), api_key. Returns: result

get_monitor_statusAInspect

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 details.

Inputs: monitor_id (required), api_key. Returns: result

get_projectBInspect

Get a single project's details.

Inputs: project_id (required), api_key. Returns: result

get_project_overviewAInspect

Get a project's resource overview (counts grouped by resource type and status).

Inputs: project_id (required), api_key. Returns: result

get_user_limitsAInspect

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 check current usage against plan limits before running a large job.

Inputs: api_key. Returns: result

get_versionAInspect

Get current API version.

This tool maps to GET /version and does not require an API key.

Inputs: api_key. Returns: result

get_webhookAInspect

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.

Inputs: webhook_id (required), api_key. Returns: result

get_webhook_historyAInspect

Get the webhook delivery history for a resource (job/monitor/monitor_group).

Use when:

  • You want to see past webhook delivery attempts and their outcomes for a specific job or monitor.

Inputs: resource_id (required), resource_type (required), page, api_key, +1 more. Returns: result

initialize_queryAInspect

Preview suggested validators, enrichments, and date ranges before submitting.

Use when:

  • You want to inspect/edit auto-generated validators/enrichments before submitting.

  • You want to preview date adjustments via date_modification_message.

Do not use when:

  • You want to start processing immediately with final inputs (use submit_query).

Key behavior:

  • Preview-only endpoint: does not create a job and does not start processing.

  • Suggestions are LLM-generated and not deterministic across calls.

  • To reuse suggestions, pass them explicitly to submit_query.

Inputs: query (required), api_key, context, fetch_all_watchlist_news. Returns: result

list_dataset_entitiesBInspect

List the entities contained in a dataset.

Inputs: dataset_id (required), page, search, status, +5 more. Returns: result

list_datasetsCInspect

List your datasets.

Inputs: page, search, api_key, sort_by, +5 more. Returns: result

list_entitiesCInspect

List your entities.

Inputs: page, search, status, api_key, +4 more. Returns: result

list_monitor_jobsAInspect

List all jobs spawned by a monitor.

Returns the history of scheduled runs for a monitor.

Inputs: monitor_id (required), sort, api_key. Returns: result

list_monitorsAInspect

List all your monitors.

Returns all monitors with their schedule, status, reference query, and webhook config.

Inputs: page, search, api_key, ownership, +2 more. Returns: result

list_project_resourcesAInspect

List the resources contained in a project.

Inputs: project_id (required), page, api_key, page_size, +1 more. Returns: result

list_projectsCInspect

List your projects.

Inputs: page, search, api_key, ownership, +1 more. Returns: result

list_resource_webhooksAInspect

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 for it.

Inputs: resource_id (required), resource_type (required), page, api_key, +2 more. Returns: result

list_user_jobsAInspect

List all jobs submitted by you.

Returns your job history with IDs, queries, statuses, and timestamps.

Inputs: page, search, api_key, ownership, +2 more. Returns: result

list_webhook_resourcesAInspect

List the resources mapped to a webhook.

Use when:

  • You want to see which jobs/monitors a webhook is attached to.

Inputs: webhook_id (required), page, api_key, page_size, +1 more. Returns: result

list_webhooksAInspect

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 webhook_ids) or jobs.

Inputs: page, api_key, page_size. Returns: result

pull_job_csvAInspect

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 the consumer needs spreadsheet/CSV format.

Inputs: job_id (required), api_key. Returns: result

pull_monitor_csvAInspect

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.

  • Prefer this over pull_monitor_results when the consumer needs spreadsheet/CSV format.

Inputs: monitor_id (required), api_key. Returns: result

pull_monitor_resultsAInspect

Retrieve the latest results from a monitor.

Returns the most recent run's results including run_info, records, and all_records.

Inputs: monitor_id (required), api_key. Returns: result

pull_resultsAInspect

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 enriched web results. While job status is active, call this repeatedly (typically page=1) to refresh partial output. When job reaches completed, iterate all pages. If job fails, call once more to capture any partial output.

Inputs: job_id (required), page, api_key, page_size. Returns: result

remove_dataset_entitiesAInspect

Remove entities from a dataset (the entities themselves are not deleted).

Inputs: dataset_id (required), entity_ids (required), api_key. Returns: result

remove_project_resourceBInspect

Remove a single resource from a project.

Inputs: project_id (required), resource_id (required), resource_type (required), api_key. Returns: result

remove_webhook_resourceAInspect

Unmap a resource from a webhook.

Use when:

  • You want to stop a webhook from firing for a specific job or monitor.

Inputs: webhook_id (required), resource_id (required), resource_type (required), api_key. Returns: result

submit_queryAInspect

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 the API to fetch/process sources and then return structured results.

Do not use when:

  • You want status for an existing job (use get_job_status).

  • You want records for an existing job (use pull_results).

Key rules:

  • query is required.

  • You can submit with only query; omitted optional fields (validators, enrichments, start_date, end_date) are auto-selected/generated by the API.

  • Optional fields are independent: you can pass any subset (for example, custom validators but no enrichments), and omitted fields are still auto-selected/generated.

  • When connected_dataset_ids is set, the query must describe the topic or event type only (e.g. "M&A activity", "regulatory filings", "executive changes"). Do NOT write things like "for my companies", "for the selected list of companies", or "news about my watchlist" — the entity filtering is applied automatically by the connected dataset. Mentioning companies in the query when a dataset is attached is redundant and degrades retrieval quality.

  • When connected_dataset_ids is set, entity-relevance validators (e.g. company_is_primary_subject) are generated automatically by the API. Do NOT add them manually to validators — they are redundant and may conflict with the auto-generated ones. Only pass validators that describe the event or topic, not entity filtering.

  • start_date and end_date filter by web page discovery date, not event date.

  • Discovery dates and extracted event dates can differ. For event-time accuracy, use event-focused validators/enrichments and verify event_date in pulled results.

  • end_date must be after start_date.

  • Dates outside your plan lookback limits return API 400.

  • limit controls processed record count (cost-affecting). Omit it to retrieve everything up to your plan's maximum. If provided, must be >= 10.

  • validators / enrichments may be passed either as arrays or as JSON-string arrays (for client compatibility).

  • validators[].type must be boolean (if omitted, it defaults to boolean).

  • enrichments[].type supported values: text, number, date, option, url, company.

Basic examples:

  • validators: [{"name":"is_acquisition_event","description":"true if page describes an acquisition","type":"boolean"}]

  • enrichments: [{"name":"acquiring_company","description":"Extract acquiring company","type":"company"},{"name":"deal_value","description":"Extract announced deal value","type":"number"}]

Next step:

  • Save the returned job_id.

  • Poll get_job_status and call pull_results (partial results can appear before completion).

Inputs: query (required), mode, limit, schema, +12 more. Returns: result

test_webhookAInspect

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 or job.

Inputs: webhook_id (required), api_key, payload. Returns: result

trigger_webhookAInspect

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 for the automatic dispatch — e.g. to replay a missed or failed delivery.

Inputs: webhook_id (required), resource_id (required), resource_type (required), job_id, +1 more. Returns: result

update_datasetBInspect

Update a dataset's name and/or description.

Inputs: dataset_id (required), name, api_key, description. Returns: result

update_entityBInspect

Update an entity's name, description, external_entity_id, and/or attributes.

Inputs: entity_id (required), name, api_key, description, +2 more. Returns: result

update_monitorAInspect

Update a monitor's webhook assignments and per-run limit.

Note: schedule and reference_job_id cannot be modified through this endpoint. Webhooks are centralized — pass webhook IDs (from create_webhook/list_webhooks).

Inputs: monitor_id (required), limit, api_key, webhook_ids. Returns: result

update_projectAInspect

Update a project's name and/or description.

Only the fields you provide are changed.

Inputs: project_id (required), name, api_key, description. Returns: result

update_webhookAInspect

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 a webhook (set is_active).

  • Only the fields you provide are updated; omitted fields remain unchanged.

Inputs: webhook_id (required), url, auth, name, +8 more. Returns: result

validate_queryAInspect

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 before spending credits on a job.

  • You want concrete suggestions to improve a vague or overly broad query.

Do not use when:

  • You want to preview auto-generated validators/enrichments (use initialize_query).

  • You want to actually run a search (use submit_query).

Inputs: query (required), api_key. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 60 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Live 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.
      19
      10
      240 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      91 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      307 npm
      MIT