{ "data": { "a": { "slug": "liner-mcp", "name": "Liner Search MCP", "vendor": "Liner", "vendorUrl": "https://liner.com", "kind": "mcp", "category": "search", "summary": "Liner Search MCP is a hosted server with web, scholarly, legal, finance, medical and business search tools and three agent tools for quick cited answers, search answers and deep research reports, over OAuth 2.1 or an API key.", "url": "https://www.anchorterminal.com/tools/liner-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/liner-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/liner-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/liner-mcp.json", "dns": "liner-mcp.grade.anchorterminal.com", "transports": [ "streamable-http" ], "remoteUrl": "https://platform.liner.com/api/v1/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.1 sign-in in a browser, or a Bearer token with a Liner API key (LINER_API_KEY) for CI and headless use.", "pricing": "paid", "pricingNotes": "Search and Agent APIs are billed per call. Web search, scholar search and visualisation $1 per 1,000 requests; Quick Answer Agent $3 per 1,000 requests; the other agents' prices weren't readable. No free allowance found (checked 2026-11-07).", "priceSummary": "$1 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://liner.com/developers/docs/mcp", "llmsTxt": "https://liner.com/llms.txt", "registryName": "com.liner/search", "capabilities": [ "search.serp", "search.research", "search.answer", "search.scholar" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "oauth", "api-key", "paid", "pay-per-call", "status-page", "llms-txt", "mcp-registry" ], "graded": true, "anchor": { "graded": true, "score": 43.4, "grade": "E", "agentReady": false, "rank": 1252, "ranked": true, "rankOf": 1510, "categoryRank": 23, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 45, "payments": 20, "reliability": 50, "schema": 45, "security": 35, "transparency": 34 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "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.", "bestFor": "Agents that need cheap cited search across the web and scholarly sources, with optional deep research reports.", "strengths": [ "Web, scholarly, legal, finance, medical and business search plus three cited-answer agents", "Search at $1 per 1,000 requests, published", "Nine tools with a table saying which fits which need", "Rate limits published per API", "OAuth for people, API keys for CI" ], "weaknesses": [ "No free tier found", "No changelog; registry entry unchanged since September", "Status page covers the app, not the API or MCP", "Web content reaches the model with no injection guidance" ], "agentNotes": [ "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.4 } ], "editorialScores": { "ergonomics": 65, "maintenance": 45, "payments": 20, "reliability": 50, "schema": 45, "security": 35, "transparency": 20 }, "provenanceScore": 48, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add liner --transport http https://platform.liner.com/api/v1/mcp", "config": { "mcpServers": { "liner": { "url": "https://platform.liner.com/api/v1/mcp" } } } }, "letme": { "capability": "https://letme.dev/search.serp", "tool": "https://letme.dev/liner-mcp" }, "area": "web-data", "unitPrices": [ { "item": "Web search", "unit": "1k-requests", "usd": 1, "note": "Also scholar search and visualisation" }, { "item": "Quick Answer Agent", "unit": "1k-requests", "usd": 3 } ], "provenance": { "legalEntity": "Liner", "domain": "liner.com", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "https://status.liner.com", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "Terms and privacy weren't read in this batch.", "security.txt answered 404." ], "score": 48 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/liner-mcp.json", "live": { "slug": "liner-mcp", "probe": { "target": "https://platform.liner.com/api/v1/mcp", "method": "mcp-initialize", "lastAt": "2026-11-07T23:14:34.139886163Z", "lastOk": true, "lastStatus": 401, "lastMs": 207, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 207, "p95ms24h": 420, "samples24h": 46, "samples30d": 46, "days": [ { "date": "2026-11-07", "probes": 46, "ok": 46 } ] }, "vendorStatus": { "page": "https://status.liner.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T23:08:03.305040872Z" }, "updatedAt": "2026-11-07T23:14:34.139886163Z" } }, "answer": "Perplexity Search API scores 70.2 (BB) on agent readiness against Liner Search MCP's 43.4 (E), and leads in every scored category.", "b": { "slug": "perplexity-search-api", "name": "Perplexity Search API", "vendor": "Perplexity", "vendorUrl": "https://www.perplexity.ai/", "kind": "http-api", "category": "search", "summary": "Perplexity's Search API returns ranked web results with extracted page text as JSON from Perplexity's own index, through `POST /search`. The same key reaches the Agent API's web_search tool for cited answers, and a hosted MCP server wraps both.", "url": "https://www.anchorterminal.com/tools/perplexity-search-api", "markdownUrl": "https://www.anchorterminal.com/tools/perplexity-search-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/perplexity-search-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json", "dns": "perplexity-search-api.grade.anchorterminal.com", "repo": "https://github.com/perplexityai/modelcontextprotocol", "license": "Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://api.perplexity.ai/mcp", "packages": [ { "registry": "pypi", "name": "perplexityai" }, { "registry": "npm", "name": "@perplexity-ai/perplexity_ai" }, { "registry": "npm", "name": "@perplexity-ai/mcp-server" } ], "auth": "mixed", "authNotes": "Bearer Perplexity API key in the `Authorization` header. Keys belong to a project in the API console, are shown once, and can be generated and revoked through `/generate_auth_token` and `/revoke_auth_token`, with a rotation guide. No per-key scopes found. The hosted MCP server also accepts Sign in with Perplexity (OAuth), where the user picks the organisation to bill.", "pricing": "usage", "pricingNotes": "$5 per 1,000 successful Search API requests, or $1 with Fast Search, with up to five queries per request billed once. Invalid, rate-limited and failed requests are not billed. Agent API web_search is $2.50 per 1,000 calls plus model tokens. Prepaid credits with a card. No free allowance found.", "priceSummary": "$5 / 1k req", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Search API docs, the pricing page, the OpenAPI description or llms.txt (checked 2026-11-06). An empty balance returns 402 Payment Required with no payment requirements, per the FAQ.", "endpoints": [] }, "toolCount": 4, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.perplexity.ai/docs/search/overview", "llmsTxt": "https://docs.perplexity.ai/llms.txt", "openapi": "https://docs.perplexity.ai/openapi.json", "registryName": "ai.perplexity/mcp-server", "capabilities": [ "web.search", "search.answer", "search.research" ], "tags": [ "hosted", "usage-priced", "prepaid", "card-required", "closed-source", "openapi", "llms-txt", "mcp", "remote-mcp", "mcp-registry", "python", "typescript", "status-page", "soc2" ], "lastRelease": "2026-10-23", "graded": true, "anchor": { "graded": true, "score": 70.2, "grade": "BB", "agentReady": true, "rank": 211, "ranked": true, "rankOf": 1510, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 85, "maintenance": 82, "payments": 25, "reliability": 80, "schema": 89, "security": 56, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found.", "bestFor": "Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.", "strengths": [ "OpenAPI 3.1 description of `POST /search` with enums and limits, llms.txt and a Markdown twin of every docs page", "`max_tokens`, `max_tokens_per_page` and `max_results` cap what reaches the model, and up to five queries share one billed request", "Per-request prices published without login, and invalid, rate-limited and failed requests are not billed", "Hosted MCP server with OAuth or a key; the local server is in the official registry under the verified ai.perplexity namespace", "security.txt valid to 31 December 2027, a SOC 2 Type II report and a SECURITY.md that takes private reports" ], "weaknesses": [ "The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA", "No free allowance and prepaid credits with a card; Stripe Projects still needs a $10 purchase", "Project keys have no scopes or spending limits, so any key can run every API on the account", "No guidance on treating returned snippets as untrusted text was found in the docs or the MCP server", "The DPA says Perplexity Search may follow different data terms, and no retention period for search queries is stated" ], "agentNotes": [ "Set `max_tokens_per_page` and `max_tokens` before calling; extracted text otherwise fills the context, and the price does not change with size", "Skip results with an empty `snippet` and dedupe by `url` when sending a `query` array; each query costs one rate-limit unit", "Use `search_type: \"fast\"` for $1 per 1,000 when latency and cost matter more than depth", "On 429 wait for Retry-After, then back off; on 402 stop and ask the user to add credits", "Use the Search API for sources and the Agent API's web_search tool for a written answer with citations" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 70.2 } ], "editorialScores": { "ergonomics": 85, "maintenance": 82, "payments": 25, "reliability": 80, "schema": 89, "security": 56, "transparency": 51 }, "provenanceScore": 80, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install perplexityai", "http": "curl -X POST https://api.perplexity.ai/search \\\n -H \"Authorization: Bearer $PERPLEXITY_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"query\": \"renewable energy technologies\", \"max_results\": 10, \"max_tokens\": 50000, \"max_tokens_per_page\": 4096}'", "claudeCode": "claude mcp add --transport http perplexity https://api.perplexity.ai/mcp", "config": { "mcpServers": { "perplexity": { "url": "https://api.perplexity.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/perplexity-search-api" }, "sameCompany": [ "perplexity-space", "pplx-decider", "pplx-decider-flash" ], "area": "web-data", "unitPrices": [ { "item": "Search API request", "unit": "1k-requests", "usd": 5, "note": "Up to five queries in one request billed once; failed and rate-limited requests not billed" }, { "item": "Search API request with Fast Search", "unit": "1k-requests", "usd": 1, "note": "`search_type: \"fast\"`" }, { "item": "Agent API web_search call", "unit": "1k-calls", "usd": 2.5, "note": "Plus model tokens; $1.00 with Fast Search" }, { "item": "Agent API fetch_url call", "unit": "1k-calls", "usd": 0.5, "note": "Plus model tokens" } ], "provenance": { "legalEntity": "Perplexity AI, Inc.", "domain": "perplexity.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.perplexity.ai/hub/legal/perplexity-api-terms-of-service", "privacy": "https://www.perplexity.ai/hub/legal/privacy-notice", "statusPage": "https://status.perplexity.com/", "changelog": "https://docs.perplexity.ai/docs/resources/changelog", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The API Terms of Service (last updated 23 January 2026) name Perplexity AI, Inc. and California law. The Data Processing Addendum (last updated 13 August 2026) deletes personal data within 30 days of the service ending and notes that Perplexity Search may follow different data terms.", "www.perplexity.ai/.well-known/security.txt is valid until 31 December 2027 and links www.perplexity.ai/security.", "The status page moved to incident.io on 10 September 2026 and has Website, App, Computer and API components, with no separate Search component.", "docs.perplexity.ai/robots.txt allows the docs and carries Content-Signal ai-train=yes, search=yes, ai-input=yes. The terms have no clause on automated access to the website.", "The changelog dates entries by month only. Domain registration was not checked." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/perplexity-search-api.json", "live": { "slug": "perplexity-search-api", "probe": { "target": "https://api.perplexity.ai/mcp", "method": "get", "lastAt": "2026-11-07T23:14:42.701374975Z", "lastOk": true, "lastStatus": 401, "lastMs": 230, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 167, "p95ms24h": 279, "samples24h": 244, "samples30d": 249, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 236, "ok": 236 } ] }, "vendorStatus": { "page": "https://status.perplexity.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T23:08:36.009937213Z" }, "versions": [ { "registry": "mcp-registry", "name": "ai.perplexity/mcp-server", "version": "1.2.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@perplexity-ai/mcp-server", "version": "1.3.0", "seenAt": "2026-11-06T23:55:31.394431614Z" }, { "registry": "npm", "name": "@perplexity-ai/perplexity_ai", "version": "0.41.0", "seenAt": "2026-11-06T23:55:30.575713692Z" }, { "registry": "pypi", "name": "perplexityai", "version": "0.46.1", "released": "2026-10-23", "seenAt": "2026-11-06T23:55:30.34668899Z" } ], "githubStars": 2612, "npmWeekly": 97298, "pypiWeekly": 401537, "securityTxt": { "url": "https://perplexity.ai/.well-known/security.txt", "state": "valid", "expires": "2027-12-31T00:00:00Z", "checkedAt": "2026-11-07T16:01:03.917430365Z" }, "llmsTxt": { "url": "https://docs.perplexity.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:36.681222085Z" }, "pages": [ { "url": "https://docs.perplexity.ai/docs/resources/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:27.675707255Z", "changedAt": "2026-11-06T13:29:48.535494355Z", "fingerprint": "a52a171e1f1f" }, { "url": "https://www.perplexity.ai/hub/legal/privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:32:54.875760985Z", "changedAt": "2026-11-06T13:53:25.792168971Z", "fingerprint": "29c9dd01613d" }, { "url": "https://www.perplexity.ai/hub/legal/perplexity-api-terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:32:50.897959644Z", "changedAt": "2026-11-06T13:53:22.592031411Z", "fingerprint": "6a7e4a95f45b" } ], "mcpTools": { "url": "https://api.perplexity.ai/mcp", "checkedAt": "2026-11-07T01:46:49.011542458Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:49.011542458Z" }, "updatedAt": "2026-11-07T23:14:42.701374975Z" } }, "edges": [ { "by": 44, "category": "schema", "leads": "perplexity-search-api", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "OpenAPI 3.1.0 at docs.perplexity.ai/openapi.json describes `POST /search` with typed request and response schemas, listed in llms.txt (25). llms.txt indexes every page, each with a Markdown twin (10). The overview says what a result holds, that snippets can be empty, when to use the Search API instead of the Agent API, and that it takes queries not URLs and does not re-fetch pages (19 of 20). `search_type` is an enum, `max_results`, `max_tokens` and `max_tokens_per_page` carry minimum and maximum, country and language codes carry lengths, and `query` is a string or an array. The recency filter is an enum in the docs, and date filters are `MM/DD/YYYY` strings (14 of 15). Python, TypeScript and cURL examples with a recorded response. The spec documents only 200 and 422 for `/search`, and status codes are listed on the SDK error-handling page and the rate-limit page rather than for Search (11 of 15). A public changelog with several entries a month, dated by month only, and an unversioned `/search` path (10 of 15). 25 + 10 + 19 + 14 + 11 + 10 = 89." }, "scores": { "a": 45, "b": 89 } }, { "by": 37, "category": "maintenance", "leads": "perplexity-search-api", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "Read as a closed service with official SDKs and an open-source MCP server. perplexityai 0.46.1 on PyPI on 23 October 2026 and the MCP server's last commit on 21 October, with changelog entries into November 2026 (30). In the 90 days from 8 August, perplexityai 0.43.7 to 0.46.1 (six releases from 2 October), MCP server 1.2.1 (27 August) and 1.3.0 (25 September, Fast Search on perplexity_search), and Fast Search itself in September (20). A changelog with several entries a month, a community forum with a bug-report category, a GitHub discussion repository and api@perplexity.ai. MCP issue reply times weren't read (10 of 15). The MCP server is in the official registry under the domain-verified ai.perplexity namespace, and the Python and TypeScript SDKs are current (15). The MCP repository runs tests in CI and validates its plugin manifests. Its 1.4.0, prepared on 16 October, is not on npm, which still serves 1.3.0, and the registry's latest entry is 1.2.1 of 27 August (7 of 10). 30 + 20 + 10 + 15 + 7 = 82." }, "scores": { "a": 45, "b": 82 } }, { "by": 32, "category": "transparency", "leads": "perplexity-search-api", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service under terms naming Perplexity AI, Inc. and California law. The MCP server is MIT and the SDKs Apache-2.0 (18 of 30). The terms and DPA say Customer Content and personal data don't train Perplexity's models, the DPA deletes personal data within 30 days of the service ending, and the Privacy and Security page says retention varies by API and zero data retention is not the default. The DPA also says Perplexity Search may follow different data terms, which weren't found, and no retention period for search queries is stated (15 of 30). Sonar Chat Completions support ended on 27 September 2026 with a migration guide and requests reformulated rather than refused, and sonar-reasoning was removed on 15 December 2025 with a named replacement. Notices are dated by month and there is no standing notice period beyond the terms' 30 days for termination (10 of 20). A sub-processor list on the trust centre, which is drawn by script and wasn't read, ten business days' notice of new non-model subprocessors, and SCCs for EU and UK transfers. No data location is stated (8 of 20). 18 + 15 + 10 + 8 = 51." }, "scores": { "a": 34, "b": 66 } }, { "by": 30, "category": "reliability", "leads": "perplexity-search-api", "name": "Reliability", "reasons": { "a": "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.", "b": "Graded on the hosted lines, for `POST /search` and the hosted MCP server. status.perplexity.com, on incident.io since 10 September 2026, has an API component with an RSS feed and a JSON summary. There is no separate Search component (20). In the 90 days from 8 August the feed lists 'Investigating API issue' on 13 August, resolved with no detail, a usage-based billing issue on 3 September, and on 9 October elevated errors on the website, app and Computer, where the API 'remained operational throughout'. Minor only, with the caveat that history before the migration may be incomplete (20). The Search API is limited to 50 query units a second with a burst of 50 on every tier, and the other APIs publish QPS and token limits per tier (15). 429 carries Retry-After and an `error.type`, the SDKs retry 429 and 5xx twice honouring Retry-After, the Search best-practices page shows backoff, and failed or rate-limited searches are not billed. Searches have no side effects (15). The FAQ says Perplexity does not guarantee uptime, failure frequency or recovery time, and the terms carry no SLA (0). No beta label on the Search API, launched on 25 September 2025 (10). 20 + 20 + 15 + 15 + 0 + 10 = 80." }, "scores": { "a": 50, "b": 80 } }, { "by": 21, "category": "security", "leads": "perplexity-search-api", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Project API keys, shown once, revocable, and generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found. The hosted MCP server also takes Sign in with Perplexity (OAuth). Keys go in the Authorization header only (22 of 30, as on the Decisions API listing). Search only reads, and MCP clients can disable tools, but any key reaches every API on the account, including the Agent API's sandbox and MCP tools (8 of 20). Snippets are third-party page text, and no guidance on treating them as untrusted was found in the docs, the MCP server or its SECURITY.md (0 of 15). Responses carry a request `id`, and the console shows usage by key. The Audit API covers enterprise organisations' web app events with its own keys, not API calls (8 of 15). security.txt valid until 31 December 2027 linking a security page, a SOC 2 Type II report, a 2025 HIPAA gap assessment and a CAIQlite listed on the trust centre, and a SECURITY.md on the MCP server that takes private reports through GitHub advisories or security@perplexity.ai. The trust centre is drawn by script and wasn't read (18 of 20). 22 + 8 + 0 + 8 + 18 = 56." }, "scores": { "a": 35, "b": 56 } }, { "by": 20, "category": "ergonomics", "leads": "perplexity-search-api", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "`max_results` 1 to 20, `max_tokens` and `max_tokens_per_page` cap the extracted text, and results are title, url, snippet and two dates. The MCP server has four tools (23 of 25). Domain, language, recency, publication and update date filters and `country`, with up to five queries in one request. No pagination or offset (16 of 20). 429 bodies name the limit hit, the SDKs map status codes to typed errors, and 402 marks an empty balance. Search-specific error bodies beyond 422 validation are not documented (13 of 20). Searches only read, failed and rate-limited requests are not billed, and the MCP server sets readOnlyHint true, destructiveHint false and idempotentHint false on every tool (18 of 20). Only `query` is required. Official Python and TypeScript SDKs, a CLI and a Python Search SDK (15). 23 + 16 + 13 + 18 + 15 = 85." }, "scores": { "a": 65, "b": 85 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Liner", "b": "Perplexity", "name": "Vendor" }, { "a": "https://platform.liner.com/api/v1/mcp", "b": "https://api.perplexity.ai/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0", "name": "Licence" }, { "a": "9", "b": "4", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.liner/search", "b": "ai.perplexity/mcp-server", "name": "MCP registry" }, { "a": "none", "b": "2026-10-23", "name": "Last release" }, { "a": "no document linked", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "no document linked", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "couldn't be read", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Perplexity Search API scores 70.2 (BB) on agent readiness against Liner Search MCP's 43.4 (E), and leads in every scored category.", "question": "Which is better for AI agents, Liner Search MCP or Perplexity Search API?" }, { "answer": "Liner Search MCP uses an OAuth sign-in. Perplexity Search API takes an API key or an OAuth sign-in.", "question": "Do Liner Search MCP and Perplexity Search API need an API key?" }, { "answer": "Yes. Liner Search MCP has a hosted endpoint at https://platform.liner.com/api/v1/mcp and Perplexity Search API at https://api.perplexity.ai/mcp.", "question": "Can an agent call Liner Search MCP and Perplexity Search API without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Agents that need cheap cited search across the web and scholarly sources, with optional deep research reports.", "slug": "liner-mcp", "watchFor": "No free tier found" }, { "aheadOn": [ "Reliability, 80 against 50", "Schema \u0026 documentation, 89 against 45", "Agent ergonomics, 85 against 65", "Security \u0026 auth, 56 against 35", "Payments \u0026 pricing, 25 against 20", "Maintenance \u0026 community, 82 against 45", "Transparency \u0026 trust, 66 against 34" ], "also": [ "Agent-ready, a grade of BB or better", "Runs on your own machine" ], "goodFor": "Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.", "slug": "perplexity-search-api", "watchFor": "The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA" } ], "history": null, "job": { "capability": "search.research", "name": "Research search" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.json", "title": "Grounding with Bing Search vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-perplexity-search-api.json", "title": "Brave Search API + MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-search-api.json", "title": "Cloudflare Web Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api.json", "title": "DeepSeek Search and Fetch API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-perplexity-search-api.json", "title": "Exa API + MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api.json", "title": "Firecrawl MCP vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api.json", "title": "Kagi Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.json", "title": "Linkup vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api.json", "title": "Mojeek Web Search API vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.json", "title": "NewsCatcher vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.json", "title": "Parallel Search and Task APIs vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io.json", "title": "Perplexity Search API vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi.json", "title": "Perplexity Search API vs SerpApi", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper.json", "title": "Perplexity Search API vs Serper", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse.json", "title": "Perplexity Search API vs SERPHouse", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite.json", "title": "Perplexity Search API vs SerpKite", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream.json", "title": "Perplexity Search API vs SpecStream", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp.json", "title": "Perplexity Search API vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search.json", "title": "Perplexity Search API vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu.json", "title": "Perplexity Search API vs Valyu", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api.json", "title": "Perplexity Search API vs You.com APIs", "url": "https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-liner-mcp.json", "title": "Arcmira vs Liner Search MCP", "url": "https://www.anchorterminal.com/compare/arcmira-vs-liner-mcp" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api.json", "title": "Arcmira vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-liner-mcp.json", "title": "Exa API + MCP vs Liner Search MCP", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-liner-mcp" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-liner-mcp.json", "title": "Grep AI vs Liner Search MCP", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-liner-mcp" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api.json", "title": "Grep AI vs Perplexity Search API", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-linkup.json", "title": "Liner Search MCP vs Linkup", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-newscatcher.json", "title": "Liner Search MCP vs NewsCatcher", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-newscatcher" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-parallel-search-api.json", "title": "Liner Search MCP vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-specstream.json", "title": "Liner Search MCP vs SpecStream", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-tavily-mcp.json", "title": "Liner Search MCP vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-tinyfish-search.json", "title": "Liner Search MCP vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-valyu.json", "title": "Liner Search MCP vs Valyu", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-you-com-api.json", "title": "Liner Search MCP vs You.com APIs", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-searchapi-io.json", "title": "Liner Search MCP vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-serpapi.json", "title": "Liner Search MCP vs SerpApi", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-serper.json", "title": "Liner Search MCP vs Serper", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-serphouse.json", "title": "Liner Search MCP vs SERPHouse", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-serphouse" }, { "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-serpkite.json", "title": "Liner Search MCP vs SerpKite", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-liner-mcp.json", "title": "Grounding with Bing Search vs Liner Search MCP", "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-liner-mcp" } ], "panel": null, "scores": [ { "by": 30, "edge": "perplexity-search-api", "key": "reliability", "liner-mcp": 50, "name": "Reliability", "perplexity-search-api": 80, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 44, "edge": "perplexity-search-api", "key": "schema", "liner-mcp": 45, "name": "Schema \u0026 documentation", "perplexity-search-api": 89, "weight": 13 }, { "by": 20, "edge": "perplexity-search-api", "key": "ergonomics", "liner-mcp": 65, "name": "Agent ergonomics", "perplexity-search-api": 85, "weight": 13 }, { "by": 21, "edge": "perplexity-search-api", "key": "security", "liner-mcp": 35, "name": "Security \u0026 auth", "perplexity-search-api": 56, "weight": 14 }, { "by": 5, "edge": "perplexity-search-api", "key": "payments", "liner-mcp": 20, "name": "Payments \u0026 pricing", "perplexity-search-api": 25, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 37, "edge": "perplexity-search-api", "key": "maintenance", "liner-mcp": 45, "name": "Maintenance \u0026 community", "perplexity-search-api": 82, "weight": 7 }, { "by": 32, "edge": "perplexity-search-api", "key": "transparency", "liner-mcp": 34, "name": "Transparency \u0026 trust", "perplexity-search-api": 66, "weight": 7 } ], "summary": "Perplexity Search API scores 70.2 (BB) on agent readiness against Liner Search MCP's 43.4 (E), and leads in every scored category. Both do research search.", "tasks": null, "tutorials": [], "verdicts": { "liner-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.", "perplexity-search-api": "Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api", "json": "https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api.min.md" }, "markdown": "Perplexity Search API scores 70.2 (BB) on agent readiness against Liner Search MCP's 43.4 (E), and leads in every scored category. Both do research search.\n\n- Liner Search MCP: grade E, 43.4/100, rank #1252 of 1510. Markdown https://www.anchorterminal.com/tools/liner-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/liner-mcp.json\n- Perplexity Search API: grade BB, 70.2/100, rank #211 of 1510. Markdown https://www.anchorterminal.com/tools/perplexity-search-api.md · JSON https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 326 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### Liner Search MCP (E)\n\nGood for: Agents that need cheap cited search across the web and scholarly sources, with optional deep research reports.\n\nWatch for: No free tier found\n\n### Perplexity Search API (BB)\n\nGood for: Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.\n\nAhead on:\n- Reliability, 80 against 50\n- Schema \u0026 documentation, 89 against 45\n- Agent ergonomics, 85 against 65\n- Security \u0026 auth, 56 against 35\n- Payments \u0026 pricing, 25 against 20\n- Maintenance \u0026 community, 82 against 45\n- Transparency \u0026 trust, 66 against 34\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Runs on your own machine\n\nWatch for: The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Perplexity Search API +44\n\n- 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.\n- Perplexity Search API (89): OpenAPI 3.1.0 at docs.perplexity.ai/openapi.json describes `POST /search` with typed request and response schemas, listed in llms.txt (25). llms.txt indexes every page, each with a Markdown twin (10). The overview says what a result holds, that snippets can be empty, when to use the Search API instead of the Agent API, and that it takes queries not URLs and does not re-fetch pages (19 of 20). `search_type` is an enum, `max_results`, `max_tokens` and `max_tokens_per_page` carry minimum and maximum, country and language codes carry lengths, and `query` is a string or an array. The recency filter is an enum in the docs, and date filters are `MM/DD/YYYY` strings (14 of 15). Python, TypeScript and cURL examples with a recorded response. The spec documents only 200 and 422 for `/search`, and status codes are listed on the SDK error-handling page and the rate-limit page rather than for Search (11 of 15). A public changelog with several entries a month, dated by month only, and an unversioned `/search` path (10 of 15). 25 + 10 + 19 + 14 + 11 + 10 = 89.\n\n### Maintenance \u0026 community: Perplexity Search API +37\n\n- 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.\n- Perplexity Search API (82): Read as a closed service with official SDKs and an open-source MCP server. perplexityai 0.46.1 on PyPI on 23 October 2026 and the MCP server's last commit on 21 October, with changelog entries into November 2026 (30). In the 90 days from 8 August, perplexityai 0.43.7 to 0.46.1 (six releases from 2 October), MCP server 1.2.1 (27 August) and 1.3.0 (25 September, Fast Search on perplexity_search), and Fast Search itself in September (20). A changelog with several entries a month, a community forum with a bug-report category, a GitHub discussion repository and api@perplexity.ai. MCP issue reply times weren't read (10 of 15). The MCP server is in the official registry under the domain-verified ai.perplexity namespace, and the Python and TypeScript SDKs are current (15). The MCP repository runs tests in CI and validates its plugin manifests. Its 1.4.0, prepared on 16 October, is not on npm, which still serves 1.3.0, and the registry's latest entry is 1.2.1 of 27 August (7 of 10). 30 + 20 + 10 + 15 + 7 = 82.\n\n### Transparency \u0026 trust: Perplexity Search API +32\n\n- 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.\n- Perplexity Search API (66): Closed service under terms naming Perplexity AI, Inc. and California law. The MCP server is MIT and the SDKs Apache-2.0 (18 of 30). The terms and DPA say Customer Content and personal data don't train Perplexity's models, the DPA deletes personal data within 30 days of the service ending, and the Privacy and Security page says retention varies by API and zero data retention is not the default. The DPA also says Perplexity Search may follow different data terms, which weren't found, and no retention period for search queries is stated (15 of 30). Sonar Chat Completions support ended on 27 September 2026 with a migration guide and requests reformulated rather than refused, and sonar-reasoning was removed on 15 December 2025 with a named replacement. Notices are dated by month and there is no standing notice period beyond the terms' 30 days for termination (10 of 20). A sub-processor list on the trust centre, which is drawn by script and wasn't read, ten business days' notice of new non-model subprocessors, and SCCs for EU and UK transfers. No data location is stated (8 of 20). 18 + 15 + 10 + 8 = 51.\n\n### Reliability: Perplexity Search API +30\n\n- 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.\n- Perplexity Search API (80): Graded on the hosted lines, for `POST /search` and the hosted MCP server. status.perplexity.com, on incident.io since 10 September 2026, has an API component with an RSS feed and a JSON summary. There is no separate Search component (20). In the 90 days from 8 August the feed lists 'Investigating API issue' on 13 August, resolved with no detail, a usage-based billing issue on 3 September, and on 9 October elevated errors on the website, app and Computer, where the API 'remained operational throughout'. Minor only, with the caveat that history before the migration may be incomplete (20). The Search API is limited to 50 query units a second with a burst of 50 on every tier, and the other APIs publish QPS and token limits per tier (15). 429 carries Retry-After and an `error.type`, the SDKs retry 429 and 5xx twice honouring Retry-After, the Search best-practices page shows backoff, and failed or rate-limited searches are not billed. Searches have no side effects (15). The FAQ says Perplexity does not guarantee uptime, failure frequency or recovery time, and the terms carry no SLA (0). No beta label on the Search API, launched on 25 September 2025 (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.\n\n### Security \u0026 auth: Perplexity Search API +21\n\n- 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.\n- Perplexity Search API (56): Project API keys, shown once, revocable, and generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found. The hosted MCP server also takes Sign in with Perplexity (OAuth). Keys go in the Authorization header only (22 of 30, as on the Decisions API listing). Search only reads, and MCP clients can disable tools, but any key reaches every API on the account, including the Agent API's sandbox and MCP tools (8 of 20). Snippets are third-party page text, and no guidance on treating them as untrusted was found in the docs, the MCP server or its SECURITY.md (0 of 15). Responses carry a request `id`, and the console shows usage by key. The Audit API covers enterprise organisations' web app events with its own keys, not API calls (8 of 15). security.txt valid until 31 December 2027 linking a security page, a SOC 2 Type II report, a 2025 HIPAA gap assessment and a CAIQlite listed on the trust centre, and a SECURITY.md on the MCP server that takes private reports through GitHub advisories or security@perplexity.ai. The trust centre is drawn by script and wasn't read (18 of 20). 22 + 8 + 0 + 8 + 18 = 56.\n\n### Agent ergonomics: Perplexity Search API +20\n\n- 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.\n- Perplexity Search API (85): `max_results` 1 to 20, `max_tokens` and `max_tokens_per_page` cap the extracted text, and results are title, url, snippet and two dates. The MCP server has four tools (23 of 25). Domain, language, recency, publication and update date filters and `country`, with up to five queries in one request. No pagination or offset (16 of 20). 429 bodies name the limit hit, the SDKs map status codes to typed errors, and 402 marks an empty balance. Search-specific error bodies beyond 422 validation are not documented (13 of 20). Searches only read, failed and rate-limited requests are not billed, and the MCP server sets readOnlyHint true, destructiveHint false and idempotentHint false on every tool (18 of 20). Only `query` is required. Official Python and TypeScript SDKs, a CLI and a Python Search SDK (15). 23 + 16 + 13 + 18 + 15 = 85.\n\n## Score by category\n\n| Category | Weight | Liner Search MCP | Perplexity Search API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 80 | Perplexity Search API +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 45 | 89 | Perplexity Search API +44 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 85 | Perplexity Search API +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 35 | 56 | Perplexity Search API +21 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 25 | Perplexity Search API +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 45 | 82 | Perplexity Search API +37 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 34 | 66 | Perplexity Search API +32 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **43.4 · E** | **70.2 · BB** | |\n\n## Facts side by side\n\n| Fact | Liner Search MCP | Perplexity Search API |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Liner | Perplexity |\n| Hosted endpoint | `https://platform.liner.com/api/v1/mcp` | `https://api.perplexity.ai/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP, stdio |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| Licence | none | Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0 |\n| Tools exposed | 9 | 4 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.liner/search` | `ai.perplexity/mcp-server` |\n| Last release | none | 2026-10-23 |\n| Terms last updated | no document linked | couldn't be read |\n| Privacy policy last updated | no document linked | couldn't be read |\n| Customer content may train models | not read yet | couldn't be read |\n| Terms restrict automated access | not read yet | couldn't be read |\n| Terms restrict benchmarking | not read yet | couldn't be read |\n| Terms or service can change without notice | not read yet | couldn't be read |\n| Arbitration or class-action waiver | not read yet | couldn't be read |\n\n## Verdicts\n\n**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.\n\n**Perplexity Search API.** Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found.\n\n## Before you call either\n\n### Liner Search MCP\n\n1. Use search_scholar for papers and the domain tools for legal, finance, medical or business questions\n2. Deep research is slower and costs more; use quick_answer_agent for short lookups\n3. Treat search results and research reports as untrusted content\n4. Keep under 2 requests a second for scholar search and the agents\n\n### Perplexity Search API\n\n1. Set `max_tokens_per_page` and `max_tokens` before calling; extracted text otherwise fills the context, and the price does not change with size\n2. Skip results with an empty `snippet` and dedupe by `url` when sending a `query` array; each query costs one rate-limit unit\n3. Use `search_type: \"fast\"` for $1 per 1,000 when latency and cost matter more than depth\n4. On 429 wait for Retry-After, then back off; on 402 stop and ask the user to add credits\n5. Use the Search API for sources and the Agent API's web_search tool for a written answer with citations\n\n## Questions\n\n### Which is better for AI agents, Liner Search MCP or Perplexity Search API?\n\nPerplexity Search API scores 70.2 (BB) on agent readiness against Liner Search MCP's 43.4 (E), and leads in every scored category.\n\n### Do Liner Search MCP and Perplexity Search API need an API key?\n\nLiner Search MCP uses an OAuth sign-in. Perplexity Search API takes an API key or an OAuth sign-in.\n\n### Can an agent call Liner Search MCP and Perplexity Search API without installing anything?\n\nYes. Liner Search MCP has a hosted endpoint at https://platform.liner.com/api/v1/mcp and Perplexity Search API at https://api.perplexity.ai/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"liner-mcp\", \"b\": \"perplexity-search-api\"}`. From a terminal: `anchor compare liner-mcp perplexity-search-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/liner-mcp.json and https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json\n\n## Other comparisons with Liner Search MCP or Perplexity Search API\n\n- [Web Search Tool on Amazon Bedrock AgentCore vs Perplexity Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api.md)\n- [Grounding with Bing Search vs Perplexity Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.md)\n- [Brave Search API + MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-perplexity-search-api.md)\n- [Cloudflare Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-search-api.md)\n- [DeepSeek Search and Fetch API vs Perplexity Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api.md)\n- [Exa API + MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/exa-mcp-vs-perplexity-search-api.md)\n- [Firecrawl MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api.md)\n- [Kagi Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api.md)\n- [Linkup vs Perplexity Search API](https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.md)\n- [Mojeek Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api.md)\n- [NewsCatcher vs Perplexity Search API](https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.md)\n- [Parallel Search and Task APIs vs Perplexity Search API](https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.md)\n- [Perplexity Search API vs SearchAPI.io](https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io.md)\n- [Perplexity Search API vs SerpApi](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi.md)\n- [Perplexity Search API vs Serper](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper.md)\n- [Perplexity Search API vs SERPHouse](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse.md)\n- [Perplexity Search API vs SerpKite](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite.md)\n- [Perplexity Search API vs SpecStream](https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream.md)\n- [Perplexity Search API vs Tavily API + MCP](https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp.md)\n- [Perplexity Search API vs TinyFish Search](https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search.md)\n- [Perplexity Search API vs Valyu](https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu.md)\n- [Perplexity Search API vs You.com APIs](https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api.md)\n- [Arcmira vs Liner Search MCP](https://www.anchorterminal.com/compare/arcmira-vs-liner-mcp.md)\n- [Arcmira vs Perplexity Search API](https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api.md)\n- [Exa API + MCP vs Liner Search MCP](https://www.anchorterminal.com/compare/exa-mcp-vs-liner-mcp.md)\n- [Grep AI vs Liner Search MCP](https://www.anchorterminal.com/compare/grep-ai-vs-liner-mcp.md)\n- [Grep AI vs Perplexity Search API](https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api.md)\n- [Liner Search MCP vs Linkup](https://www.anchorterminal.com/compare/liner-mcp-vs-linkup.md)\n- [Liner Search MCP vs NewsCatcher](https://www.anchorterminal.com/compare/liner-mcp-vs-newscatcher.md)\n- [Liner Search MCP vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/liner-mcp-vs-parallel-search-api.md)\n- [Liner Search MCP vs SpecStream](https://www.anchorterminal.com/compare/liner-mcp-vs-specstream.md)\n- [Liner Search MCP vs Tavily API + MCP](https://www.anchorterminal.com/compare/liner-mcp-vs-tavily-mcp.md)\n- [Liner Search MCP vs TinyFish Search](https://www.anchorterminal.com/compare/liner-mcp-vs-tinyfish-search.md)\n- [Liner Search MCP vs Valyu](https://www.anchorterminal.com/compare/liner-mcp-vs-valyu.md)\n- [Liner Search MCP vs You.com APIs](https://www.anchorterminal.com/compare/liner-mcp-vs-you-com-api.md)\n- [Liner Search MCP vs SearchAPI.io](https://www.anchorterminal.com/compare/liner-mcp-vs-searchapi-io.md)\n- [Liner Search MCP vs SerpApi](https://www.anchorterminal.com/compare/liner-mcp-vs-serpapi.md)\n- [Liner Search MCP vs Serper](https://www.anchorterminal.com/compare/liner-mcp-vs-serper.md)\n- [Liner Search MCP vs SERPHouse](https://www.anchorterminal.com/compare/liner-mcp-vs-serphouse.md)\n- [Liner Search MCP vs SerpKite](https://www.anchorterminal.com/compare/liner-mcp-vs-serpkite.md)\n- [Grounding with Bing Search vs Liner Search MCP](https://www.anchorterminal.com/compare/bing-grounding-vs-liner-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Liner Search MCP vs Perplexity Search API", "url": "" } ], "description": "Perplexity Search scores 70.2 (BB) to Liner Search MCP's 43.4 (E) for research search. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Liner Search MCP E 43.4", "Perplexity Search API BB 70.2", "scores" ], "h1": "Liner Search MCP vs Perplexity Search API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/liner-mcp-vs-perplexity-search-api", "published": "2026-10-01", "section": "tools", "title": "Liner Search MCP vs Perplexity Search for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-search-api" }, "tokens": { "markdown": 5350, "slim": 3030 }, "version": 1 }