# NewsCatcher vs Serper (slim)

> NewsCatcher scores 67.5 (B) to Serper's 24.2 (F) for search news. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/newscatcher-vs-serper.md (~5,150 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/newscatcher-vs-serper.json · canonical https://www.anchorterminal.com/compare/newscatcher-vs-serper
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

NewsCatcher scores 67.5 (B) on agent readiness against Serper's 24.2 (F), and leads in 6 of 7 scored categories. Serper leads on payments & pricing. Both do search news.

- NewsCatcher: B 67.5, rank #321 of 1486 · https://www.anchorterminal.com/tools/newscatcher.min.md
- Serper: F 24.2, rank #1418 of 1486 · https://www.anchorterminal.com/tools/serper.min.md
- NewsCatcher, good for Agents that need current news across languages, grouped into stories, or tables of events and company news on a schedule. Ahead on Reliability, 67 against 30; Schema & documentation, 94 against 6; Agent ergonomics, 84 against 35; Security & auth, 45 against 20; Maintenance & community, 76 against 3; Transparency & trust, 79 against 32.
- Serper, good for High-volume Google SERP lookups on a tight budget where the agent already has a fetcher. Ahead on Payments & pricing, 40 against 30. Also Free to start without a card.

| Category | NewsCatcher | Serper |
| --- | --- | --- |
| Reliability (16%) | 67 | 30 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 94 | 6 |
| Agent ergonomics (13%) | 84 | 35 |
| Security & auth (14%) | 45 | 20 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 76 | 3 |
| Transparency & trust (7%) | 79 | 32 |

| Fact (where they differ) | NewsCatcher | Serper |
| --- | --- | --- |
| Vendor | NewsCatcher, Inc. | Serper |
| Hosted endpoint | `https://mcp.newscatcherapi.com/mcp` | `https://google.serper.dev/search` |
| Transports | Streamable HTTP | HTTP |
| Pricing | Pay per use | Freemium |
| Price for search news | $1 per 1,000 requests | not published |
| Tools exposed | 15 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-11-06 | none |
| Terms last updated | 2026-11-02 | 2024-05-29 |
| Privacy policy last updated | 2026-11-02 | 2025-11-05 |
| Customer content may train models | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | none | 2.5/5 (2) |

Why the edge:
- Schema & documentation, NewsCatcher +88: NewsCatcher 94 (OpenAPI 3.1 for the News API (version 1.3.9, 4 paths) and the agent (version 1.5.1, 33 paths), linked from llms.txt, and typed JSON Schema on every MCP tool through Pydantic (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). MCP tool descriptions say when to use each and which tool to use instead, such as `list_articles` for older news; the REST reference explains each endpoint and the 'Choose an API' page compares them (17 of 20). Inputs are typed with enums for effort, mode and dimensions, length and range limits such as a 500-character query and limit 1 to 100, and required fields marked (13 of 15). Runnable examples in curl, Python and JavaScript, and an error table with retry advice for every status. The agent spec carries no response examples (14 of 15). Versioned APIs with a dated changelog, the latest entries on 4 November 2026, and separate changelogs for the v3 News API and CatchAll (15). 25 + 10 + 17 + 13 + 14 + 15 = 94.); Serper 6 (No OpenAPI or other spec (0). serper.dev/llms.txt returns 404 and there are no Markdown docs (0). The documentation is the playground, a JavaScript page that showed us no text. Per the 30 September check it lists the verticals and parameters such as `gl` and `hl`, so a few points for descriptions (3) and typed inputs (3). No examples or error responses we could read (0). No changelog or API versioning (0).)
- Maintenance & community, NewsCatcher +73: NewsCatcher 76 (Read for a closed service, with the MCP repository read as code. News API 1.1.0 and Agent 1.5.0 on 4 November 2026, MCP server 0.1.0 on 6 November and v3 News API 3.25.0 on 6 November (30). In the 90 days from 8 August, the 30 October launch, News API 1.1.0, Agent 1.5.0, MCP 0.1.0 and v3 releases 3.19.0 to 3.25.0 (20). Public dated changelogs, support by email and Pylon, and a security policy with a 3-business-day target. The MCP repository is a day old, so there are no issues to judge (10 of 15). The CatchAll MCP server is in the official registry under the verified namespace com.newscatcherapi, but the new server isn't, and no official SDK for the current API was found; the Enterprise APIs list libraries (8 of 15). The MCP repository runs its test suite in CI with a read-only token; pass state not read (8 of 10). 30 + 20 + 10 + 8 + 8 = 76.); Serper 3 (No changelog, release notes, SDK or package found, so no dated release or API change to count (0, 0). No public changelog. Support is by email per the privacy policy (3). No official SDKs (0). No packages or CI to assess (0).)
- Agent ergonomics, NewsCatcher +49: NewsCatcher 84 (15 MCP tools in four toolsets, chosen per connection with `?tools=`, and tools return compact text rather than the full JSON. 15 for 11 to 30 tools plus 7 for toolsets (22 of 25). `limit`, `search_window`, effort, language, country, publisher, coverage and content-type filters, sorting, and paging on `/articles`; agent tables come back up to 200 rows at a time over MCP (20). Every status is documented with whether to retry; the agent returns stable `code` values, while the News API body has a `status_code` and a message meant for people (17 of 20). Every tool carries readOnlyHint and idempotentHint, writes carry destructiveHint, `start_research` has a free `dry_run`, and refused or failed calls aren't charged. No idempotency key for starting runs (17 of 20). Only `q` is required, with medium effort and a 7-day window as defaults. No official SDK for the current API was found; the docs show raw HTTP in three languages (8 of 15). 22 + 20 + 17 + 17 + 8 = 84.); Serper 35 (Responses are compact SERP JSON with no field selection or Markdown option found (10). Country and language parameters per the 30 September check, and ten separate verticals. We couldn't confirm pagination or result-count parameters from the docs (8). No documented error responses (0). Searches are read-only and only successful queries use credits, per the 30 September check of the home page (10). One required field (`q`) and no official SDK (7).)
- Transparency & trust, NewsCatcher +47: NewsCatcher 79 (The API is closed under terms of 2 November 2026 naming NewsCatcher, Inc., and the MCP server is MIT, so between the two bands (20 of 30). The terms say inputs and generated data are not used to train models, a DPA applies automatically, and the privacy policy gives retention periods (server logs 7 days, API logs with query text 90 days, then archived indefinitely, billing records about seven years). They agree with each other, but indefinite archives of query logs hold it back (22 of 30). The terms promise 30 days' email notice before a paid product or API version is discontinued, with refunds of unused credits, and the v3 News API has a migration guide (15 of 20). A sub-processor list dated 2 November 2026 with each provider's location and the data it handles. The MCP repository deploys to Vercel and can send pseudonymised analytics to PostHog, and neither appears on the list (16 of 20). 20 + 22 + 15 + 16 = 73.); Serper 32 (Closed service. The terms exist (last updated 29 May 2024, UK law) but name no legal entity, only 'Serper' (8). The privacy policy (5 November 2025) says the service 'should normally not lead to the processing of personal data' and keeps account data for the life of the account, but states no retention period for queries or results (10). No deprecation policy or dated notices (0). Subprocessors are described by category (payments, email, hosting) without names, with transfers outside the EEA under Standard Contractual Clauses (5).)
- Reliability, NewsCatcher +37: NewsCatcher 67 (Read with the hosted lines, for the News API, the agent and the hosted MCP server. status.newscatcherapi.com (Hyperping) shows one News API component with 99.820% uptime from August to November 2026 and an incident history. The agent and the MCP server have no component of their own (20). In the 90 days from 8 August, one incident, on 1 September 2026, when the vendor wrote that for about four hours a higher-than-usual number of requests to the production News API timed out because of one client's queries. Read as one major (10). Rate limits published per plan, 1 request a second free and up to 10 on pay as you go, with exact limits from the free `GET /subscription` (15). 429 carries Retry-After with instructions to retry the same request, 503 carries Retry-After, and failed or refused requests are not charged. Agent runs and monitor creation have no idempotency keys (12 of 15). An uptime SLA exists only in signed Enterprise agreements; none is published (0). Generally available since 30 October 2026, with OAuth for the MCP server announced as coming soon (10). 20 + 10 + 15 + 12 + 0 + 10 = 67.); Serper 30 (No status page. status.serper.dev answers with a 302 to Atlassian's Statuspage marketing site (0). No readable incident history (5). Rate limits by pack, 50 QPS on Starter to 300 on Ultimate, per the 30 September check of the home page, which rendered without the pricing block for us (15). No 429 or retry guidance found (0). No SLA in the terms (0). GA (10).)
- Security & auth, NewsCatcher +25: NewsCatcher 45 (API keys in the `x-api-key` header, several per account, revocable in the platform, with advice to keep one per application. A 403 for 'a key that may not use this API' suggests per-key API access, but no scopes are documented (20). The MCP server documents `?apiKey=` on the server URL for Claude.ai custom connectors, with a warning, so less 10 (10 of 30). The MCP repository's SECURITY.md says URL keys are rejected unless the operator enables them, which the hosted server does per the docs. Toolsets let an operator load only the read-only `news` tools, write tools carry destructiveHint, and the server tells the assistant to confirm large or hourly agent jobs (14 of 20). Results are third-party article text and summaries, and no prompt-injection guidance was found in the docs or the MCP server's instructions (0 of 15). Every response carries a Correlation-ID, `GET /subscription` shows usage and balance, and runs are listed in the platform. No per-call audit log for the customer was found (7 of 15). The security page and footer claim SOC 2 Type II and link a trust centre on Oneleet, which wasn't read. A vulnerability disclosure policy covers the MCP server. No security.txt (404) and no bug bounty found (14 of 20). 10 + 14 + 0 + 7 + 14 = 45.); Serper 20 (API key in the `X-API-KEY` header, never in the URL. No scopes, multiple keys or rotation found (10). Read-only search with no write surface, but no MCP annotations or least-privilege mode (10). Returns third-party titles and snippets with no prompt-injection guidance (0). No per-call log or audit trail found outside the logged-in dashboard, which we couldn't see (0). serper.dev/.well-known/security.txt returns 404, and we found no disclosure policy, bug bounty or certification (0).)