List your agent

CatchAll

MCP server● Hosted · onlinev1.6.5

Web search API: find every relevant event across the open web, not just the top results

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: find influencers.
All AI agents to find influencers, ranked →

Similar tools

Listed for the same task: find influencers

Reviews

No review yet. Used CatchAll? Be the first to help others choose.

What it does

CatchAll is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: web research. That makes it a candidate for tasks such as find influencers or find leads.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.6.5
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://catchall-mcp.newscatcherapi.com/mcp streamable-http

Required: x-api-key (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "catchall": {
      "url": "https://catchall-mcp.newscatcherapi.com/mcp",
      "headers": {
        "x-api-key": "<your x-api-key>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE CatchAll answered an MCP connection on 15 Nov 2026 and introduced itself as Newscatcher CatchAll API 4.1.3 (MCP protocol 2025-06-18).

61 tools offered to AI assistants

  • 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 the API to fetch/process sources and then return structured results. Do not use
  • initialize_query · 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_messag
  • 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 -> clustering -> enriching -> completed/failed IMPORTANT: Jobs take several minutes to pro
  • 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 enriched web results. While job status is active, call this repeatedly (typically pa
  • 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 the consumer needs spreadsheet/CSV format.
  • 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). Only use this when the user wants MORE data processed. This only applies to jobs o
  • list_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 well-formed for CatchAll before spending credits on a job. - You want concrete suggestions to improve a
  • 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-visibility groups your organization can access). - You need a group's `slug` to attac
  • 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, refine until results match, then create a monitor. The schedule is defined in natural
  • list_monitors · List all your monitors. Returns all monitors with their schedule, status, reference query, and webhook config.
Show 49 more
  • 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 analysis or export. - Prefer this over `pull_monitor_results` when the consumer needs spreadsheet/CSV form
  • list_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 endpoint. Webhooks are centralized — pass webhook IDs (from `create_webhook`/`list_webhooks`).
  • 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).
  • 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 details.
  • 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 webhook_ids) or jobs.
  • 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 monitor (via webhook_ids) or a job submission. - You want the webhook associated with
  • 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.
  • 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 a webhook (set `is_active`). - Only the fields you provide are updated; omitted
  • delete_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 attaching it to a monitor or job.
  • 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.
  • list_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 which webhooks will fire for it.
  • 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 see deliveries made for a specific job/monitor/monitor_group. - By webhook: pass
  • 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 for the automatic dispatch — e.g. to replay a missed or failed delivery.
  • 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 narrow retrieval scope.
  • list_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.
  • get_dataset_status · Get the status history of a dataset (e.g. its enrichment progress over time).
  • 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 `domain` column or a `description` column (or both) — a row with only a name is accept
  • 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 `domain` or `description` column (or both) for meaningful enrichment. Duplicate ro
  • create_entity · 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``.
  • list_entities · List your entities.
  • create_entities_batch · Create multiple entities in one call.
  • get_entity · Get a single entity's details.
  • update_entity · Update an entity's name, description, external_entity_id, and/or attributes.
  • delete_entity · Permanently delete an entity.
  • 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`.
  • list_projects · List your projects.
  • get_project · Get a single project's details.
  • update_project · Update a project's name and/or description. Only the fields you provide are changed.
  • 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, monitors, datasets, and monitor groups. Webhooks are the exception: they are n
  • get_project_overview · Get a project's resource overview (counts grouped by resource type and status).
  • 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 project only detaches its webhooks — it never deletes them.
  • list_project_resources · List the resources contained in a project.
  • 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 membership in this project; the webhook keeps existing and stays attached to an
  • 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 check current usage against plan limits before running a large job.
  • check_health · Check API health status. This tool maps to GET /health and does not require an API key.
  • get_version · Get current API version. This tool maps to GET /version and does not require an API key.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://catchall-mcp.newscatcherapi.com/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Repositoryhttps://github.com/Newscatcher/catchall-mcpDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version1.6.5DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run CatchAll? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor CatchAllLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of CatchAll?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/catchall?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/catchall/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about CatchAll

How do I connect CatchAll?

Use the hosted endpoint https://catchall-mcp.newscatcherapi.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does CatchAll need an API key or token?

Yes. The registry entry lists a required value: x-api-key. Get it from the publisher.

What tools does CatchAll offer?

When Electra Index connected on 15 Nov 2026, it listed 61 tools: submit_query, initialize_query, get_job_status, pull_results, pull_job_csv, continue_job, list_user_jobs, delete_job and more. The full list is in "Live check" above.

Is CatchAll online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use CatchAll for?

Based on its description, it is most relevant to: find influencers, find leads, fact-check a document, monitor news on a topic.