CatchAll
REMOTE · CATCHALL-MCP.NEWSCATCHERAPI.COM · SCANNED OCT 7
Web search API: find every relevant event across the open web, not just the top results.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 61 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 11780 tokens (~193/item across 61 items; 61 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_job" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 62 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the CatchAll MCP server?
CatchAll is a hosted endpoint at https://catchall-mcp.newscatcherapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · catchall-mcp.newscatcherapi.com
claude mcp add --transport http com-newscatcherapi-catchall 'https://catchall-mcp.newscatcherapi.com/mcp'
{
"mcpServers": {
"com-newscatcherapi-catchall": {
"url": "https://catchall-mcp.newscatcherapi.com/mcp"
}
}
} {
"servers": {
"com-newscatcherapi-catchall": {
"type": "http",
"url": "https://catchall-mcp.newscatcherapi.com/mcp"
}
}
} [mcp_servers.com-newscatcherapi-catchall] url = "https://catchall-mcp.newscatcherapi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-newscatcherapi-catchall": {
"type": "remote",
"url": "https://catchall-mcp.newscatcherapi.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-newscatcherapi-catchall --url 'https://catchall-mcp.newscatcherapi.com/mcp' --transport streamable-http
mcp_servers:
com-newscatcherapi-catchall:
url: "https://catchall-mcp.newscatcherapi.com/mcp" {
"McpServers": {
"com-newscatcherapi-catchall": {
"Transport": "http",
"Url": "https://catchall-mcp.newscatcherapi.com/mcp"
}
}
} assistant mcp add com-newscatcherapi-catchall -t streamable-http -u 'https://catchall-mcp.newscatcherapi.com/mcp'
{
"mcpServers": {
"com-newscatcherapi-catchall": {
"type": "http",
"url": "https://catchall-mcp.newscatcherapi.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Tool “update_monitor” rewrote its description, which is the text the model reads security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 3.3.1 → 4.0.5 functional
- “update_monitor” added an optional parameter “schedule” cosmetic
- “update_monitor” added an optional parameter “timezone” cosmetic
- Tool “add_dataset_entities” changed its title: Add Dataset Entities cosmetic
- Tool “add_project_resources” changed its title: Add Project Resources cosmetic
- Tool “append_csv_to_dataset” changed its title: Append Csv To Dataset cosmetic
- Tool “assign_webhook_resource” changed its title: Assign Webhook Resource cosmetic
- Tool “check_health” changed its title: Check Health cosmetic
- Tool “continue_job” changed its title: Continue Job cosmetic
- Tool “create_dataset” changed its title: Create Dataset cosmetic
- Tool “create_dataset_from_csv” changed its title: Create Dataset From Csv cosmetic
- Tool “create_entities_batch” changed its title: Create Entities Batch cosmetic
- Tool “create_entity” changed its title: Create Entity cosmetic
- Tool “create_monitor” changed its title: Create Monitor cosmetic
- Tool “create_project” changed its title: Create Project cosmetic
- Tool “create_webhook” changed its title: Create Webhook cosmetic
- Tool “delete_dataset” changed its title: Delete Dataset cosmetic
- Tool “delete_entity” changed its title: Delete Entity cosmetic
- Tool “delete_job” changed its title: Delete Job cosmetic
- Tool “delete_monitor” changed its title: Delete Monitor cosmetic
- Tool “delete_project” changed its title: Delete Project cosmetic
- Tool “delete_webhook” changed its title: Delete Webhook cosmetic
- Tool “disable_monitor” changed its title: Disable Monitor cosmetic
- Tool “enable_monitor” changed its title: Enable Monitor cosmetic
- Tool “get_dataset” changed its title: Get Dataset cosmetic
- Tool “get_dataset_status” changed its title: Get Dataset Status cosmetic
- Tool “get_entity” changed its title: Get Entity cosmetic
- Tool “get_job_status” changed its title: Get Job Status cosmetic
- Tool “get_monitor_status” changed its title: Get Monitor Status cosmetic
- Tool “get_project” changed its title: Get Project cosmetic
- Tool “get_project_overview” changed its title: Get Project Overview cosmetic
- Tool “get_user_limits” changed its title: Get User Limits cosmetic
- Tool “get_version” changed its title: Get Version cosmetic
- Tool “get_webhook” changed its title: Get Webhook cosmetic
- Tool “get_webhook_history” changed its title: Get Webhook History cosmetic
- Tool “initialize_query” changed its title: Initialize Query cosmetic
- Tool “list_dataset_entities” changed its title: List Dataset Entities cosmetic
- Tool “list_datasets” changed its title: List Datasets cosmetic
- Tool “list_entities” changed its title: List Entities cosmetic
- Tool “list_monitor_jobs” changed its title: List Monitor Jobs cosmetic
- Tool “list_monitors” changed its title: List Monitors cosmetic
- Tool “list_project_resources” changed its title: List Project Resources cosmetic
- Tool “list_projects” changed its title: List Projects cosmetic
- Tool “list_resource_webhooks” changed its title: List Resource Webhooks cosmetic
- Tool “list_source_groups” changed its title: List Source Groups cosmetic
- Tool “list_user_jobs” changed its title: List User Jobs cosmetic
- Tool “list_webhook_resources” changed its title: List Webhook Resources cosmetic
- Tool “list_webhooks” changed its title: List Webhooks cosmetic
- Tool “pull_job_csv” changed its title: Pull Job Csv cosmetic
- Tool “pull_monitor_csv” changed its title: Pull Monitor Csv cosmetic
- Tool “pull_monitor_results” changed its title: Pull Monitor Results cosmetic
- Tool “pull_results” changed its title: Pull Results cosmetic
- Tool “remove_dataset_entities” changed its title: Remove Dataset Entities cosmetic
- Tool “remove_project_resource” changed its title: Remove Project Resource cosmetic
- Tool “remove_webhook_resource” changed its title: Remove Webhook Resource cosmetic
- Tool “submit_query” changed its title: Submit Query cosmetic
- Tool “test_webhook” changed its title: Test Webhook cosmetic
- Tool “trigger_webhook” changed its title: Trigger Webhook cosmetic
- Tool “update_dataset” changed its title: Update Dataset cosmetic
- Tool “update_entity” changed its title: Update Entity cosmetic
- Tool “update_monitor” changed its title: Update Monitor cosmetic
- Tool “update_project” changed its title: Update Project cosmetic
- Tool “update_webhook” changed its title: Update Webhook cosmetic
- Tool “validate_query” changed its title: Validate Query cosmetic
- 28 Aug 26 0
- New tool “list_source_groups” functional
- “list_entities” added an optional parameter “project_id” cosmetic
- “list_webhooks” added an optional parameter “project_id” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 14 Aug 26 0
- Tool “add_project_resources” rewrote its description, which is the text the model reads security
- Tool “create_webhook” rewrote its description, which is the text the model reads security
- Tool “delete_project” rewrote its description, which is the text the model reads security
- Tool “get_webhook_history” rewrote its description, which is the text the model reads security
- Tool “remove_project_resource” rewrote its description, which is the text the model reads security
- “create_webhook” added an optional parameter “project_id” cosmetic
- “get_webhook_history” added an optional parameter “webhook_id” cosmetic
- “list_user_jobs” added an optional parameter “mode” cosmetic
- “add_project_resources” reworded the description of “resources” cosmetic
- “delete_project” reworded the description of “delete_resources” cosmetic
- “get_webhook_history” reworded the description of “resource_type” cosmetic
- “list_project_resources” reworded the description of “resource_type” cosmetic
- “remove_project_resource” reworded the description of “resource_type” cosmetic
- “get_webhook_history” made “resource_id” optional cosmetic
- “get_webhook_history” made “resource_type” optional cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Oct 2026 · Probed https://catchall-mcp.newscatcherapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=catchall-mcp.newscatcherapi.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 17 Aug 2026 | 2 Mar 2027 | RSA 2048 | SHA256-RSA | e3ddb14ca15df9d34ef72b312b110bf |
| SANs: catchall-mcp.newscatcherapi.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of catchall-mcp.newscatcherapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| newscatcherapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://catchall-mcp.newscatcherapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://catchall-mcp.newscatcherapi.com/mcp | HTTPS enforced | 301 | https://catchall-mcp.newscatcherapi.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
remove_project_resource Remove Project Resource ~147
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 any other projects).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| project_id | string | yes | The project ID to remove the resource from. |
| resource_id | string | yes | The ID of the resource to remove. |
| resource_type | string | yes | Resource type: 'job', 'monitor', 'dataset', 'monitor_group', or 'webhook'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_webhook_resource Remove Webhook Resource ~122
Unmap a resource from a webhook. Use when: - You want to stop a webhook from firing for a specific job or monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| resource_id | string | yes | The ID of the mapped job/monitor/monitor_group. |
| resource_type | string | yes | Resource type: 'job', 'monitor', or 'monitor_group'. |
| webhook_id | string | yes | The webhook ID to detach the resource from. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
submit_query Submit Query ~1,314
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.…
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| connected_dataset_ids | – | – | Optional list of dataset IDs whose entities narrow the retrieval scope. When set: (1) entity filtering is applied automatically — do NOT mention the company list or watchlist in `query`; (2) entity-r… |
| context | string | – | Optional guidance on what to prioritize (for example, target entities, event types, and specific data points you want captured in enrichments). If a company dataset will be attached, note that entity… |
| ed_association_type | string | – | Optional filter on how strongly a watchlist entity must appear in each event. Only relevant when `connected_dataset_ids` is set. - `"event_associated"`: keep only events where the entity is a **direc… |
| ed_score_min | – | – | Optional minimum entity-domain relevance score (1-10). Only relevant when `connected_dataset_ids` is set. |
| end_date | string | – | Optional ISO 8601 UTC end of search window. |
| enrichments | – | – | Optional custom enrichments (`name`, `description`, `type`), as array or JSON-string array. |
| fetch_all_watchlist_news | boolean | – | When `True`, retrieves **all** news for connected watchlist entities without applying topic filtering from `query`. Requires `connected_dataset_ids` to be set. Default: `False`. |
| limit | – | – | Optional processing cap (minimum 10); affects cost. Omit to retrieve everything up to your plan's maximum. |
| mode | string | – | Optional job processing mode: `"lite"` (faster, lower cost, less detail) or `"base"` (default, full extraction). If omitted, the API defaults to `"base"`. |
| project_id | string | – | Optional project ID to associate this job with. |
| query | string | yes | Plain text search intent (required). |
| schema | string | – | Optional advanced custom JSON schema string that overrides the default extraction schema. Use `initialize_query` to discover a suitable schema. |
| start_date | string | – | Optional ISO 8601 UTC start of search window. |
| validators | – | – | Optional custom boolean validators (`name`, `description`, `type`), as array or JSON-string array. When `connected_dataset_ids` is set, do NOT include entity-relevance validators such as `company_is_… |
| webhook_ids | – | – | Optional list of webhook IDs to notify when the job completes (max 5 per job). Use `list_webhooks` / `create_webhook` to get IDs. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
test_webhook Test Webhook ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| payload | – | – | Optional custom JSON object to send as the test body. If omitted, the API sends a default sample payload. |
| webhook_id | string | yes | The webhook ID to test. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
trigger_webhook Trigger Webhook ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| job_id | string | – | Optional job ID whose payload should be delivered (e.g. a specific monitor run's job). If omitted, the API picks the resource's payload itself. |
| resource_id | string | yes | The ID of the job/monitor/monitor_group to trigger delivery for. |
| resource_type | string | yes | Resource type: 'job', 'monitor', or 'monitor_group'. |
| webhook_id | string | yes | The webhook ID to deliver through. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_dataset Update Dataset ~77
Update a dataset's name and/or description.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| dataset_id | string | yes | The dataset ID to update. |
| description | – | – | Optional new dataset description. |
| name | – | – | Optional new dataset name. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_entity Update Entity ~137
Update an entity's name, description, external_entity_id, and/or attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| additional_attributes | – | – | Optional updated structured attributes (see `create_entity` for the company_attributes shape). |
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| description | – | – | Optional new description. |
| entity_id | string | yes | The entity ID to update. |
| external_entity_id | – | – | Optional customer-supplied identifier linking this entity to an external system's record (new in 1.6.3). |
| name | – | – | Optional new entity name. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_monitor Update Monitor ~260
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`).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| limit | – | – | Optional updated maximum records per run (minimum 10). |
| monitor_id | string | yes | The monitor ID to update |
| schedule | string | – | Optional new natural-language schedule to replace the monitor's current one (e.g. 'every day at 9 AM', 'every Monday at 6 PM EST'). Leave unset to keep the current schedule. The scheduler picks up th… |
| timezone | string | – | Optional IANA timezone for the new schedule (e.g. 'America/New_York'). Defaults to UTC. Overridden if the schedule text itself contains a timezone. Ignored if `schedule` is not set. |
| webhook_ids | – | – | Optional list of webhook IDs to assign to this monitor. Pass an empty list `[]` to clear all webhook assignments. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_project Update Project ~84
Update a project's name and/or description. Only the fields you provide are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| description | – | – | Optional new project description. |
| name | – | – | Optional new project name. |
| project_id | string | yes | The project ID to update. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_webhook Update Webhook ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| auth | – | – | Updated auth object. One of: - {"type": "bearer", "token": "..."} - {"type": "api_key", "header": "X-API-Key", "value": "..."} - {"type": "basic", "username": "...", "password": "..."} |
| delivery_mode | – | – | Updated delivery mode: 'full' or 'per_record'. |
| formatter_config | – | – | Updated formatter configuration dict. |
| headers | – | – | Updated dict of custom HTTP headers. |
| is_active | – | – | Set to false to disable the webhook (stop deliveries), true to re-enable it. |
| method | – | – | Updated HTTP method: one of GET, POST, PUT, PATCH, DELETE. |
| name | – | – | Updated webhook name. |
| params | – | – | Updated dict of query string parameters. |
| type | – | – | Updated webhook type: 'generic', 'slack', 'teams', or 'custom'. |
| url | – | – | Updated target URL. |
| webhook_id | string | yes | The webhook ID to update. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
validate_query Validate Query ~147
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`).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var. |
| query | string | yes | The natural-language query to assess (required). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the CatchAll MCP server?
CatchAll is an MCP server listed in the public MCP registry as com.newscatcherapi/catchall. Web search API: find every relevant event across the open web, not just the top results. This page covers its hosted endpoint (https://catchall-mcp.newscatcherapi.com/mcp).
Is the CatchAll MCP server safe to use?
CatchAll scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CatchAll MCP server expose?
CatchAll exposes 61 tools: submit_query, initialize_query, get_job_status, pull_results, pull_job_csv, and 56 more. Their descriptions and schemas cost roughly 9,810 tokens of context every time the server is loaded.
Does the CatchAll MCP server require authentication?
No. We connected to CatchAll without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CatchAll MCP server still maintained?
CatchAll is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.