Head to head · Research search · October 2026 research run
Liner Search MCP vs NewsCatcher
NewsCatcher scores 67.5 (B) on agent readiness against Liner Search MCP's 43.4 (E), and leads in every scored category. Both do research search.
Best web search APIs for AI agents · All 326 search comparisons
Which one, for what
Best for Agents that need cheap cited search across the web and scholarly sources, with optional deep research reports.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No free tier found
Best 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 50
- Schema & documentation, 94 against 45
- Agent ergonomics, 84 against 65
- Security & auth, 45 against 35
- Payments & pricing, 30 against 20
- Maintenance & community, 76 against 45
- Transparency & trust, 79 against 34
Watch for
The current News API and agent launched on 30 October 2026 and the MCP repository went public on 6 November 2026
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation NewsCatcher +49
Liner Search MCP 45
Tool schemas not read without sign-in (15 of 25). llms.txt (10). A table says which tool fits which need, and that the domain tools return the same shape as search_web (12 of 20). Inputs not verifiable (3 of 15). Setup examples, no error responses (5 of 15). Registry version 1.0.0 since 11 September; no changelog found (0). 15 + 10 + 12 + 3 + 5 + 0 = 45.
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.
Transparency & trust NewsCatcher +45
Liner Search MCP 34
Terms and privacy linked from the docs but not read in this batch (5 of 30). Data handling not read (5 of 30). No deprecation policy found for the MCP server; the docs note older endpoints priced per version (5 of 20). Subprocessors not read (5 of 20). 5 + 5 + 5 + 5 = 20.
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.
Maintenance & community NewsCatcher +31
Liner Search MCP 45
Registry entry com.liner/search last updated 11 September 2026 (20). No dated changelog found (0). Support page linked from the docs (10 of 15). Official registry entry under its own namespace (15). No package to read (0). 20 + 0 + 10 + 15 + 0 = 45. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.
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.
Agent ergonomics NewsCatcher +19
Liner Search MCP 65
Nine tools (25). No paging or size controls documented (5 of 20). 429 codes documented for the API (8 of 20). All tools read; annotations not read (12 of 20). One URL with OAuth, few required inputs and an OpenAI-compatible API (15). 25 + 5 + 8 + 12 + 15 = 65.
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.
Reliability NewsCatcher +17
Liner Search MCP 50
incident.io status page at status.liner.com with components for liner.com and app.liner.com only, none for the API or MCP (15). 100% uptime shown since August (20, no incidents shown). Rate limits published per API with numbers (Scholar Search 2 requests a second, agents 2 a second) (15). 429 with a code for concurrency limits, no Retry-After or backoff guidance found (0 of 15). No SLA found (0). Not labelled beta (0 of 10; 'limits may be adjusted over time', GA not stated). 15 + 20 + 15 + 0 + 0 + 0 = 50.
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.
Security & auth NewsCatcher +10
Liner Search MCP 35
OAuth 2.1 or an API key; scopes not published (20 of 30). All tools are reads (10 of 20). Results carry web pages and documents with no injection guidance (0). No audit log found (0). No security.txt (404) or security programme found (5 of 20). 20 + 10 + 0 + 0 + 5 = 35.
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.
Score by category
| Category | Weight this run | Liner Search MCP | NewsCatcher | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 50 | 67 | NewsCatcher +17 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 45 | 94 | NewsCatcher +49 |
| Agent ergonomics | 13%16.2 | 65 | 84 | NewsCatcher +19 |
| Security & auth | 14%17.5 | 35 | 45 | NewsCatcher +10 |
| Payments & pricing | 10%12.5 | 20 | 30 | NewsCatcher +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 45 | 76 | NewsCatcher +31 |
| Transparency & trust | 7%8.8 | 34 | 79 | NewsCatcher +45 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 43.4/100 | B 67.5/100 |
Facts side by side
| Fact | Liner Search MCP | NewsCatcher |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Liner | NewsCatcher, Inc. |
| Hosted endpoint | https://platform.liner.com/api/v1/mcp | https://mcp.newscatcherapi.com/mcp |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth | API key |
| Pricing | Paid | Pay per use |
| Price for research search | not published | $1 per transaction |
| x402 | no | no |
| Tools exposed | 9 | 15 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | com.liner/search | not listed |
| Last release | none | 2026-11-06 |
| Terms last updated | no document linked | 2026-11-02 |
| Privacy policy last updated | no document linked | 2026-11-02 |
| Customer content may train models | not read yet | yes |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |
Verdicts
Liner Search MCP
Liner's MCP server puts cheap per-call web, scholarly and vertical search and cited research agents behind one OAuth URL, at $1 per 1,000 searches. The docs say which tool fits which question, but there's no free tier, no changelog, no injection guidance and no status component for the API.
NewsCatcher
One key and one credit balance cover a ranked news search, a background research agent and a hosted MCP server with toolsets and annotated tools, under OpenAPI 3.1 specs and a dated changelog. The current API launched on 30 October 2026, the MCP server accepts the key in its URL, and no SLA is published below Enterprise.
Before you call either
Liner Search MCP
- Use search_scholar for papers and the domain tools for legal, finance, medical or business questions
- Deep research is slower and costs more; use quick_answer_agent for short lookups
- Treat search results and research reports as untrusted content
- Keep under 2 requests a second for scholar search and the agents
NewsCatcher
- Send the key in the
x-api-keyheader, and use a separate key for the MCP server so it can be revoked alone - Call
start_researchwithdry_runfirst, since agent runs cost 1,000 to 6,000 credits - Use
effort=lowfor quick lookups; the defaultmediumcosts five times as much - Use
/articlesorlist_articlesfor news older than 30 days or exact counts;/searchcovers 30 days only - On 429 or 503 wait for Retry-After, and quote the Correlation-ID header to support
Questions
Which is better for AI agents, Liner Search MCP or NewsCatcher?
NewsCatcher scores 67.5 (B) on agent readiness against Liner Search MCP's 43.4 (E), and leads in every scored category.
Do Liner Search MCP and NewsCatcher need an API key?
Liner Search MCP uses an OAuth sign-in. NewsCatcher needs an API key.
Can an agent call Liner Search MCP and NewsCatcher without installing anything?
Yes. Liner Search MCP has a hosted endpoint at https://platform.liner.com/api/v1/mcp and NewsCatcher at https://mcp.newscatcherapi.com/mcp.
Other comparisons with Liner Search MCP or NewsCatcher
- Web Search Tool on Amazon Bedrock AgentCore vs NewsCatcher
- Grounding with Bing Search vs NewsCatcher
- Brave Search API + MCP vs NewsCatcher
- Cloudflare Web Search API vs NewsCatcher
- DeepSeek Search and Fetch API vs NewsCatcher
- Exa API + MCP vs NewsCatcher
- Kagi Search API vs NewsCatcher
- Linkup vs NewsCatcher
- Mojeek Web Search API vs NewsCatcher
- NewsCatcher vs Parallel Search and Task APIs
- NewsCatcher vs Perplexity Search API
- NewsCatcher vs TinyFish Search
- Arcmira vs Liner Search MCP
- Arcmira vs NewsCatcher
- Exa API + MCP vs Liner Search MCP
- Grep AI vs Liner Search MCP
- Grep AI vs NewsCatcher
- Liner Search MCP vs Linkup
- Liner Search MCP vs Parallel Search and Task APIs
- Liner Search MCP vs Perplexity Search API
- Liner Search MCP vs SpecStream
- Liner Search MCP vs Tavily API + MCP
- Liner Search MCP vs TinyFish Search
- Liner Search MCP vs Valyu
- Liner Search MCP vs You.com APIs
- NewsCatcher vs SpecStream
- NewsCatcher vs SearchAPI.io
- NewsCatcher vs SerpApi
- NewsCatcher vs Serper
- NewsCatcher vs SERPHouse
- NewsCatcher vs SerpKite
- NewsCatcher vs Tavily API + MCP
- NewsCatcher vs Valyu
- NewsCatcher vs You.com APIs
- Liner Search MCP vs SearchAPI.io
- Liner Search MCP vs SerpApi
- Liner Search MCP vs Serper
- Liner Search MCP vs SERPHouse
- Liner Search MCP vs SerpKite
- Grounding with Bing Search vs Liner Search MCP
Machine-readable
- This page as Markdown
/compare/liner-mcp-vs-newscatcher.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/liner-mcp.json·/api/v1/tools/newscatcher.json - From a terminal
anchor compare liner-mcp newscatcher(the CLI) - Over MCP
compare_tools {"a": "liner-mcp", "b": "newscatcher"}at/mcp, no key