Is the Newscatcherapi Catchall MCP server down?

mcp-registry/com.newscatcherapi/catchall · v4.0.5

Also listed as awesome/newscatcher/catchall-mcp, glama/newscatcher/catchall-by-newscatcher-

healthy
Last checked 2026-10-26 23:13 UTC · handshake 553ms

As of 2026-10-26 23:13 UTC, the Newscatcherapi Catchall MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 11 minutes.

uptime (30d checks)
100%
checks observed
4,950
outages (90d)
1
tools
61

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

Point your MCP client at this streamable-http endpoint: https://catchall-mcp.newscatcherapi.com/mcp

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 6 warning(s) across 61 tool(s); ~15,583 tokens of tool definitions.
Scores higher than 11% of 15,780 MCP servers Glimind has audited.
Its tool list costs an agent ~15,583 tokens per session — more than 85% of servers.
70 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions88
Safety hints0
Token cost64
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (6)

1 tool definition(s) exceed ~1,200 tokens each (largest: submit_query, ~1,385).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~785 tokens every session. How to fix →

Tools: submit_query · saves ~785 tokens/session

61 of 61 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: add_dataset_entities, add_project_resources, append_csv_to_dataset, assign_webhook_resource, check_health and 56 more

61 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

21 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_dataset, create_dataset_from_csv, create_entities_batch, create_entity, create_monitor and 16 more

3 tool(s) have descriptions under 20 characters.

Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →

Tools: list_datasets, list_entities, list_projects

Handshake + tools/list takes ~1,742 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

Auto-fix: 53 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.newscatcherapi%2Fcatchall/fixes

add_dataset_entities 1 change
{
  "name": "add_dataset_entities",
  "description": "Add existing entities to a dataset.",
  "inputSchema": {
    "type": "object",
    "required": [
      "dataset_id",
      "entity_ids"
    ],
    "properties": {
      "api_key": {
        "type": "string",
        "default": "",
        "description": "CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var."
      },
      "dataset_id": {
        "type": "string",
        "description": "The dataset ID to add entities to."
      },
      "entity_ids": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "List of entity IDs to add (required)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add Dataset Entities"
}
add_project_resources 1 change
{
  "name": "add_project_resources",
  "description": "Add one or more resources to a project.\n\nWebhooks are first-class project resources: a webhook can belong to several\nprojects at the same time, and deleting a project only detaches its\nwebhooks — it never deletes them.",
  "inputSchema": {
    "type": "object",
    "required": [
      "project_id",
      "resources"
    ],
    "properties": {
      "api_key": {
        "type": "string",
        "default": "",
        "description": "CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var."
      },
      "resources": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "object",
              "additionalProperties": {
                "type": "string"
              }
            }
          },
          {
            "type": "string"
          }
        ],
        "description": "A list of resource objects, each `{\"resource_type\": ..., \"resource_id\": ...}`.\n`resource_type` is one of: 'job', 'monitor', 'dataset', 'monitor_group', 'webhook'.\nMay also be passed as a JSON-string array for client compatibility."
      },
      "project_id": {
        "type": "string",
        "description": "The project ID to add resources to."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add Project Resources"
}
assign_webhook_resource 1 change
{
  "name": "assign_webhook_resource",
  "description": "Map a resource (job, monitor, or monitor_group) to a webhook.\n\nUse when:\n- You want a webhook to fire for a specific job or monitor's deliveries.",
  "inputSchema": {
    "type": "object",
    "required": [
      "webhook_id",
      "resource_type",
      "resource_id"
    ],
    "properties": {
      "api_key": {
        "type": "string",
        "default": "",
        "description": "CatchAll API key. Optional if provided via x-api-key header or CATCHALL_API_KEY env var."
      },
      "webhook_id": {
        "type": "string",
        "description": "The webhook ID to attach the resource to."
      },
      "resource_id": {
        "type": "string",
        "description": "The ID of the job/monitor/monitor_group to map."
      },
      "resource_type": {
        "type": "string",
        "description": "Resource type: 'job', 'monitor', or 'monitor_group'."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Assign Webhook Resource"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.newscatcherapi/catchall"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.newscatcherapi/catchall"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.newscatcherapi%2Fcatchall.svg)](https://glimind.com/server/mcp-registry%2Fcom.newscatcherapi%2Fcatchall?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.newscatcherapi%2Fcatchall?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.newscatcherapi%2Fcatchall.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.newscatcherapi%2Fcatchall.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.newscatcherapi%2Fcatchall?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:aece6d74f8e99a5d…, first seen 2026-10-17, included at leaf 3732 of 76,031. Version history · verify what your client received.

Tools (61)

Compare: most reliable data servers · most reliable communication servers · most reliable devops servers · most reliable other servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Newscatcherapi Catchall MCP server down right now?

As of 2026-10-26 23:13 UTC, the Newscatcherapi Catchall MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 11 minutes.

How many tools does Newscatcherapi Catchall MCP server provide?

Newscatcherapi Catchall MCP server advertises 61 tools, including add_dataset_entities, add_project_resources, append_csv_to_dataset, assign_webhook_resource, check_health.

How do I install Newscatcherapi Catchall MCP server?

Point your MCP client at this streamable-http endpoint: https://catchall-mcp.newscatcherapi.com/mcp

Is the Newscatcherapi Catchall MCP server safe to connect to an AI agent?

Glimind scanned all 61 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Newscatcherapi Catchall MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve