{
  "data": {
    "a": {
      "slug": "hyperresearch",
      "name": "Hyperresearch",
      "vendor": "Hyperresearch",
      "vendorUrl": "https://hyperresearch.ai",
      "company": "hyperresearch.ai",
      "kind": "http-api",
      "category": "search",
      "summary": "Hyperresearch is a deep research API from Thalient Labs Inc. that turns a question into a cited, checked report, with a source vault, citation verification and per-call Answers search, through REST and two remote MCP servers.",
      "url": "https://www.anchorterminal.com/tools/hyperresearch",
      "markdownUrl": "https://www.anchorterminal.com/tools/hyperresearch.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/hyperresearch.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/hyperresearch.json",
      "dns": "hyperresearch.grade.anchorterminal.com",
      "repo": "https://github.com/jordan-gibbs/hyperresearch",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://answers.hyperresearch.ai/mcp",
      "packages": [
        {
          "registry": "pypi",
          "name": "hyperresearch"
        },
        {
          "registry": "pypi",
          "name": "langchain-hyperresearch"
        },
        {
          "registry": "npm",
          "name": "@hyperresearch/ai-sdk"
        },
        {
          "registry": "npm",
          "name": "@hyperresearch/langchain"
        }
      ],
      "auth": "mixed",
      "authNotes": "Self-serve scoped bearer keys (`hr_live_` billed, `hr_test_` free fixture mode) created in the console after a browser signup, with rotation, revocation and IP allowlists. MCP servers use OAuth with PKCE and a scope consent screen. A client that asks for no scopes gets read-only access.",
      "pricing": "usage",
      "pricingNotes": "Answers per call from a prepaid wallet: ask 2 cents (fast), 10 cents (standard, 20 when it digs deeper), 50 cents (max). Search 5 or 15 cents. Research runs flat: Light $9, Deep $49. $5 of Answers credit and one Light report free, no card. Top-ups from $10.",
      "priceSummary": "$0.02 / call",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in llms.txt, the pricing page, the Answers page or the docs (checked 2026-11-18). Payment is a Stripe wallet or monthly invoice.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://hyperresearch.ai/docs",
      "llmsTxt": "https://hyperresearch.ai/llms.txt",
      "openapi": "https://api.hyperresearch.ai/v1/openapi.json",
      "registryName": "ai.hyperresearch/answers",
      "capabilities": [
        "search.research",
        "search.answer",
        "web.search",
        "web.fetch"
      ],
      "tags": [
        "hosted",
        "remote-mcp",
        "mcp",
        "mcp-registry",
        "oauth",
        "api-key",
        "llms-txt",
        "openapi",
        "usage-priced",
        "prepaid",
        "no-card",
        "free-tier",
        "async-jobs",
        "webhooks",
        "python",
        "typescript",
        "beta",
        "no-status-page"
      ],
      "lastRelease": "2026-11-16",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 68.1,
        "grade": "B",
        "agentReady": false,
        "rank": 407,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 13,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 83,
          "maintenance": 88,
          "payments": 60,
          "reliability": 35,
          "schema": 76,
          "security": 79,
          "transparency": 71
        },
        "assessment": {
          "confidence": "medium",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet.",
        "bestFor": "Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.",
        "strengths": [
          "Answers MCP prices are public per call: ask 2 cents (fast), 10 cents (standard), 50 cents (max), search 5 or 15 cents, with not-found calls charged less",
          "$5 of Answers credit and one free Light report on every account, no card needed. `hr_test_` keys run free fixture-mode runs",
          "Keys carry scopes (runs, vault, verify, mcp, admin), rotate with a 24-hour overlap and revoke at once. MCP uses OAuth with PKCE and a scope consent screen",
          "One error envelope with a stable `code`, `retryable` and `retry_after`, per-key rate limits by bucket, and `Idempotency-Key` on writes",
          "Fetched pages reach models inside `\u003cuntrusted-source\u003e` fences, with tool allowlists per role and private network ranges refused"
        ],
        "weaknesses": [
          "No status page, and the terms say there is no SLA and no uptime figure",
          "The terms call the service 'a beta from a young company'",
          "No SOC 2 report, no DPA on the shelf, no formal disclosure policy or bug bounty. Vulnerabilities go to the support address",
          "The research MCP server's tool schemas aren't published on a page we could read, and the OpenAPI host refused our reader",
          "Signup and MCP authorisation need a person in a browser. There is no machine payment protocol"
        ],
        "agentNotes": [
          "Use Answers (`data_and_web_answer` with mode `auto`) for one fact, and start a Light or Deep run only when the user wants a written report",
          "Send an `Idempotency-Key` on every write and reuse it only with an unchanged body, so a retried run or answer is charged once",
          "Poll a run with `GET /v1/runs/{id}` about once a minute, or stream its events. A Light run takes about 30 to 40 minutes",
          "If a response has `retryable: false`, change the request rather than retrying. Branch on `error.code`, never on the message",
          "Use a key that starts `hr_test_` to build and test an integration without spending"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "B",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 68.1
          }
        ],
        "editorialScores": {
          "ergonomics": 83,
          "maintenance": 88,
          "payments": 60,
          "reliability": 35,
          "schema": 76,
          "security": 79,
          "transparency": 84
        },
        "provenanceScore": 58,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "http": "curl -X POST https://api.hyperresearch.ai/v1/answers -H \"Authorization: Bearer $HYPERRESEARCH_KEY\" -H \"Idempotency-Key: $(uuidgen)\" -H 'Content-Type: application/json' -d '{\"question\":\"How old must a US senator be?\",\"mode\":\"fast\"}'",
        "claudeCode": "claude mcp add hyperresearch-answers --transport http https://answers.hyperresearch.ai/mcp",
        "config": {
          "mcpServers": {
            "hyperresearch": {
              "url": "https://mcp.hyperresearch.ai/mcp"
            },
            "hyperresearch-answers": {
              "url": "https://answers.hyperresearch.ai/mcp"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/search.research",
        "tool": "https://letme.dev/hyperresearch"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Answers ask, fast",
          "unit": "call",
          "usd": 0.02,
          "note": "1 to 2 cents if not found"
        },
        {
          "item": "Answers ask, standard",
          "unit": "call",
          "usd": 0.1,
          "note": "20 cents when it digs deeper"
        },
        {
          "item": "Answers ask, max",
          "unit": "call",
          "usd": 0.5,
          "note": "10 to 50 cents if not found"
        },
        {
          "item": "Answers search, standard",
          "unit": "call",
          "usd": 0.05
        },
        {
          "item": "Answers search, max",
          "unit": "call",
          "usd": 0.15
        },
        {
          "item": "Light research run",
          "unit": "tx",
          "usd": 9,
          "note": "one report"
        },
        {
          "item": "Deep research run",
          "unit": "tx",
          "usd": 49,
          "note": "one report"
        }
      ],
      "provenance": {
        "legalEntity": "Thalient Labs Inc.",
        "domain": "hyperresearch.ai",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://hyperresearch.ai/legal/terms",
        "privacy": "https://hyperresearch.ai/legal/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "The about page names Thalient Labs Inc., a Delaware corporation incorporated on 16 March 2026, at 1001 S. Main St., Suite 500, Kalispell, MT 59901, and says the terms, privacy policy and Stripe receipts carry the same details. The terms choose Delaware law and have no arbitration clause.",
          "Terms version 1.7, effective 23 September 2026, last updated 4 October 2026. Privacy policy version 1.7, effective 17 September 2026, per the about page.",
          "hyperresearch.ai/robots.txt allows ClaudeBot, anthropic-ai and Claude-Web and disallows /api/, with Content-Signal search=yes, ai-input=yes, ai-train=yes. mcp. and answers.hyperresearch.ai publish comment-only robots files with no rules. api.hyperresearch.ai's robots.txt asked for a sign-in, so that host wasn't read.",
          "/.well-known/security.txt answers 404. No status page found.",
          "The about page asks directories to copy its product descriptions verbatim. We wrote our own."
        ],
        "score": 58
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/hyperresearch.json",
      "live": {
        "slug": "hyperresearch",
        "probe": {
          "target": "https://answers.hyperresearch.ai/mcp",
          "method": "get",
          "lastAt": "2026-11-18T22:43:33.50023008Z",
          "lastOk": true,
          "lastStatus": 406,
          "lastMs": 233,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 328,
          "p95ms24h": 813,
          "samples24h": 11,
          "samples30d": 11,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 11,
              "ok": 11
            }
          ],
          "since": "2026-11-18T21:38:05.612316973Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "ai.hyperresearch/answers",
            "version": "1.0.1",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "mcpTools": {
          "url": "https://mcp.hyperresearch.ai/mcp",
          "checkedAt": "2026-10-01T21:59:49.591132636Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-10-01T21:59:49.591132636Z"
        },
        "updatedAt": "2026-11-18T22:45:57.054523297Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "answer": "Hyperresearch scores 68.1 (B) on agent readiness against Liner Search MCP's 44.7 (E), and leads in 6 of 7 scored categories. Liner Search MCP leads on reliability.",
    "b": {
      "slug": "liner-mcp",
      "name": "Liner Search MCP",
      "vendor": "Liner",
      "vendorUrl": "https://liner.com",
      "company": "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": 44.7,
        "grade": "E",
        "agentReady": false,
        "rank": 1295,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 25,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 65,
          "maintenance": 45,
          "payments": 30,
          "reliability": 50,
          "schema": 45,
          "security": 35,
          "transparency": 34
        },
        "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": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 44.7
          }
        ],
        "editorialScores": {
          "ergonomics": 65,
          "maintenance": 45,
          "payments": 30,
          "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",
          "lastMoved": "2026-11-13",
          "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-18T22:43:38.738701366Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 281,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 201,
          "p95ms24h": 497,
          "samples24h": 241,
          "samples30d": 2710,
          "days": [
            {
              "date": "2026-11-07",
              "probes": 53,
              "ok": 53
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 228,
              "ok": 228
            }
          ],
          "since": "2026-11-07T00:00:00Z"
        },
        "vendorStatus": {
          "page": "https://status.liner.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-11-18T22:38:08.78105555Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "com.liner/search",
            "version": "1.0.0",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "securityTxt": {
          "url": "https://liner.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:31:04.329293776Z"
        },
        "llmsTxt": {
          "url": "https://liner.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:14:54.115864188Z"
        },
        "domain": {
          "domain": "liner.com",
          "registered": "1996-07-12",
          "source": "https://rdap.verisign.com/com/v1/domain/liner.com",
          "checkedAt": "2026-11-15T15:25:07.417746548Z"
        },
        "mcpTools": {
          "url": "https://platform.liner.com/api/v1/mcp",
          "checkedAt": "2026-11-18T04:25:17.759214804Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-08T01:59:22.872265979Z"
        },
        "updatedAt": "2026-11-18T22:45:57.054523297Z"
      },
      "streak": {
        "days": 11,
        "from": "2026-11-07",
        "sinceWatching": true,
        "best": 11
      }
    },
    "edges": [
      {
        "by": 44,
        "category": "security",
        "leads": "hyperresearch",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Bearer keys of 32 random bytes stored as salted hashes, shown once, scoped to `runs:read`, `runs:write`, `vault:read`, `vault:write`, `verify`, `mcp` and `admin`, with a last-used time, rotation with a 24-hour overlap and instant revocation, plus an IP allowlist. MCP uses OAuth with PKCE and a consent screen that lists each scope. The docs say never to put keys in URLs (30). A client that requests no scopes gets read-only access, billed scopes are marked on the consent screen, and every workspace has a spend cap. No confirmation step for deletes was found (16 of 20). The trust page documents `\u003cuntrusted-source\u003e` fences on every fetched body, forged fence tags neutralised, per-role tool allowlists, schema-validated arguments and private address ranges refused (15). A workspace audit log exportable as NDJSON, a 365-day default window, and a list of agent connections that can be revoked (15). No security.txt (404), no formal disclosure policy and no bug bounty, and the trust page says there is no SOC 2 report. Vulnerabilities go to support@hyperresearch.ai (3 of 20). 30+16+15+15+3 = 79.",
          "b": "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."
        },
        "scores": {
          "a": 79,
          "b": 35
        }
      },
      {
        "by": 43,
        "category": "maintenance",
        "leads": "hyperresearch",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "The pricing and about pages were updated on 17 November 2026, and the open-source CLI that the hosted service runs was tagged v0.13.3 on 16 November (30). Four tagged CLI releases in the 90 days to this check: v0.13.0 (27 October), v0.13.1 (9 November), v0.13.2 (12 November), v0.13.3 (16 November) (20). The CLI changelog credits fixes to issues and pull requests from outside contributors (#71, #201 to #206). We didn't read the issue threads (15 of 25). `ai.hyperresearch/hyperresearch` and `ai.hyperresearch/answers` are in the official MCP registry under the vendor's domain namespace (15). The repository has CI and publish workflows, and AI SDK and LangChain packages are published (8 of 10). 30+20+15+15+8 = 88.",
          "b": "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."
        },
        "scores": {
          "a": 88,
          "b": 45
        }
      },
      {
        "by": 37,
        "category": "transparency",
        "leads": "hyperresearch",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "The hosted service is closed with terms from Thalient Labs Inc. (version 1.7), and the CLI that runs the same pipeline is MIT (20 of 30). The trust page states retention per record type (content kept until deleted, verification inputs 7 days, billing at least 7 years, audit log 365 days by default), names the known gaps (the run index and questions are kept indefinitely, no automatic expiry), says customer content isn't used for training, and says it matches the privacy policy. No DPA on the shelf (26 of 30). A written deprecation policy: at least six months' notice, `Deprecation` and `Sunset` headers and a list of deprecations, plus 30 days' notice by email before a shutdown (20). Subprocessors are listed with what each receives and their countries, and the trust page says there is no data residency guarantee on Cloudflare's network (18 of 20). 20+26+20+18 = 84.",
          "b": "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."
        },
        "scores": {
          "a": 71,
          "b": 34
        }
      },
      {
        "by": 31,
        "category": "schema",
        "leads": "hyperresearch",
        "name": "Schema \u0026 documentation",
        "reasons": {
          "a": "llms.txt and the versioning page name an OpenAPI 3.1 document at api.hyperresearch.ai/v1/openapi.json, and the API reference has one page per operation generated from it. api.hyperresearch.ai's robots.txt asked for a sign-in, so read.py closed the host and the file wasn't read (20 of 25). llms.txt, and every docs page as Markdown with `.md` (10). The Answers page says when to use fast, standard, max or auto and that fast skips structured sources, and the docs say Answers is for one fact and runs for a report. The research MCP server's tool descriptions couldn't be read (12 of 20). Modes and run tiers are enums, and examples show `max_results`, but the schemas themselves weren't read (10 of 15). Request and result examples, one error envelope with status meanings and a stable `code` (14 of 15). The version is in the path (/v1) with an additive-only promise, but the hosted service has no public changelog. The open-source CLI's CHANGELOG.md is dated (10 of 15). 20+10+12+10+14+10 = 76.",
          "b": "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."
        },
        "scores": {
          "a": 76,
          "b": 45
        }
      },
      {
        "by": 30,
        "category": "payments",
        "leads": "hyperresearch",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "No x402, MPP or L402 (0). Per-call prices for Answers and flat per-run prices (Light $9, Deep $49) are published without login, with rerun discounts and refund rules (30). $5 of Answers credit and the first Light report free on every account, no card needed, and `hr_test_` keys are never billed (30). A person signs up through Clerk in a browser and creates keys in the console, and MCP clients authorise in a browser (0). 0+30+30+0 = 60.",
          "b": "No machine payment protocol (0). Per-call prices public (20). No free tier found (0). A person signs up in a browser for OAuth or an API key (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30."
        },
        "scores": {
          "a": 60,
          "b": 30
        }
      },
      {
        "by": 18,
        "category": "ergonomics",
        "leads": "hyperresearch",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Answers is three compact tools (`data_and_web_answer`, `data_and_web_search` and the free `get_pending_answer`), and an answer returns only a short answer, its quotes and links. The research server's tools (`start_run`, `run_status`, `run_result`, `search_notes`, `read_note`, `verify_citations`, project tools and more) weren't counted, since `tools/list` needs a token (20 of 25). `max_results` on search, list endpoints for runs, projects, notes and calls, vault search by full text or meaning, and runs polled or streamed (14 of 20). Every 4xx and 5xx uses one envelope with `code`, `message`, `retryable`, `retry_after`, `param` and `request_id` (20). `Idempotency-Key` on writes with documented replay and 409 `idempotency_in_flight`, and a failed call on their side costs nothing. MCP tool annotations weren't readable (14 of 20). Only a query and a tier are required to start a run. Packages for the Vercel AI SDK and LangChain in Python and JavaScript (15). 20+14+20+14+15 = 83.",
          "b": "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."
        },
        "scores": {
          "a": 83,
          "b": 65
        }
      }
    ],
    "facts": [
      {
        "a": "HTTP API",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Hyperresearch",
        "b": "Liner",
        "name": "Vendor"
      },
      {
        "a": "https://answers.hyperresearch.ai/mcp",
        "b": "https://platform.liner.com/api/v1/mcp",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth",
        "name": "Auth"
      },
      {
        "a": "Pay per use",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "$9 per transaction",
        "b": "not published",
        "name": "Price for research search"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "none",
        "b": "9",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "ai.hyperresearch/answers",
        "b": "com.liner/search",
        "name": "MCP registry"
      },
      {
        "a": "2026-11-16",
        "b": "none",
        "name": "Last release"
      },
      {
        "a": "2026-11-17",
        "b": "no document linked",
        "name": "Terms last updated"
      },
      {
        "a": "2026-11-17",
        "b": "no document linked",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Terms restrict automated access"
      },
      {
        "a": "yes",
        "b": "not read yet",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not read yet",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Hyperresearch scores 68.1 (B) on agent readiness against Liner Search MCP's 44.7 (E), and leads in 6 of 7 scored categories. Liner Search MCP leads on reliability.",
        "question": "Which is better for AI agents, Hyperresearch or Liner Search MCP?"
      },
      {
        "answer": "Hyperresearch takes an API key or an OAuth sign-in. Liner Search MCP uses an OAuth sign-in.",
        "question": "Do Hyperresearch and Liner Search MCP need an API key?"
      },
      {
        "answer": "Yes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and Liner Search MCP at https://platform.liner.com/api/v1/mcp.",
        "question": "Can an agent call Hyperresearch and Liner Search MCP without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Schema \u0026 documentation, 76 against 45",
          "Agent ergonomics, 83 against 65",
          "Security \u0026 auth, 79 against 35",
          "Payments \u0026 pricing, 60 against 30",
          "Maintenance \u0026 community, 88 against 45",
          "Transparency \u0026 trust, 71 against 34"
        ],
        "also": [
          "Free to start without a card"
        ],
        "goodFor": "Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.",
        "slug": "hyperresearch",
        "watchFor": "No status page, and the terms say there is no SLA and no uptime figure"
      },
      {
        "aheadOn": [
          "Reliability, 50 against 35"
        ],
        "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"
      }
    ],
    "history": {
      "hyperresearch": null,
      "liner-mcp": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.3,
          "from": 43.4,
          "fromGrade": "E",
          "to": 44.7,
          "toGrade": "E"
        }
      ]
    },
    "job": {
      "capability": "search.research",
      "name": "Research search"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.json",
        "title": "Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.json",
        "title": "Grounding with Bing Search vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch.json",
        "title": "Brave Search API + MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.json",
        "title": "Cloudflare Web Search API vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.json",
        "title": "DeepSeek Search and Fetch API vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch.json",
        "title": "Exa API + MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch.json",
        "title": "Firecrawl MCP vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search.json",
        "title": "Hyperresearch vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.json",
        "title": "Hyperresearch vs Mojeek Web Search API",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io.json",
        "title": "Hyperresearch vs SearchAPI.io",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi.json",
        "title": "Hyperresearch vs SerpApi",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serper.json",
        "title": "Hyperresearch vs Serper",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serper"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse.json",
        "title": "Hyperresearch vs SERPHouse",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite.json",
        "title": "Hyperresearch vs SerpKite",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite"
      },
      {
        "json": "https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch.json",
        "title": "Arcmira vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch"
      },
      {
        "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/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-hyperresearch.json",
        "title": "Grep AI vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/grep-ai-vs-hyperresearch"
      },
      {
        "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/hyperresearch-vs-linkup.json",
        "title": "Hyperresearch vs Linkup",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-linkup"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher.json",
        "title": "Hyperresearch vs NewsCatcher",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api.json",
        "title": "Hyperresearch vs Parallel Search and Task APIs",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api.json",
        "title": "Hyperresearch vs Perplexity Search API",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-specstream.json",
        "title": "Hyperresearch vs SpecStream",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-specstream"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp.json",
        "title": "Hyperresearch vs Tavily API + MCP",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search.json",
        "title": "Hyperresearch vs TinyFish Search",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.json",
        "title": "Hyperresearch vs Valyu",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-valyu"
      },
      {
        "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-you-com-api.json",
        "title": "Hyperresearch vs You.com APIs",
        "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-you-com-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-perplexity-search-api.json",
        "title": "Liner Search MCP vs Perplexity Search API",
        "url": "https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-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/fetch-reference-server-vs-hyperresearch.json",
        "title": "Fetch (MCP reference server) vs Hyperresearch",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch"
      },
      {
        "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": 15,
        "edge": "liner-mcp",
        "hyperresearch": 35,
        "key": "reliability",
        "liner-mcp": 50,
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 31,
        "edge": "hyperresearch",
        "hyperresearch": 76,
        "key": "schema",
        "liner-mcp": 45,
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 18,
        "edge": "hyperresearch",
        "hyperresearch": 83,
        "key": "ergonomics",
        "liner-mcp": 65,
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 44,
        "edge": "hyperresearch",
        "hyperresearch": 79,
        "key": "security",
        "liner-mcp": 35,
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 30,
        "edge": "hyperresearch",
        "hyperresearch": 60,
        "key": "payments",
        "liner-mcp": 30,
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 43,
        "edge": "hyperresearch",
        "hyperresearch": 88,
        "key": "maintenance",
        "liner-mcp": 45,
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 37,
        "edge": "hyperresearch",
        "hyperresearch": 71,
        "key": "transparency",
        "liner-mcp": 34,
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Hyperresearch scores 68.1 (B) on agent readiness against Liner Search MCP's 44.7 (E), and leads in 6 of 7 scored categories. Liner Search MCP leads on reliability. Both do research search.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "hyperresearch": "Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet.",
      "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."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp",
    "json": "https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.min.md"
  },
  "markdown": "Hyperresearch scores 68.1 (B) on agent readiness against Liner Search MCP's 44.7 (E), and leads in 6 of 7 scored categories. Liner Search MCP leads on reliability. Both do research search.\n\n- Hyperresearch: grade B, 68.1/100, rank #407 of 1557. Markdown https://www.anchorterminal.com/tools/hyperresearch.md · JSON https://www.anchorterminal.com/api/v1/tools/hyperresearch.json\n- Liner Search MCP: grade E, 44.7/100, rank #1295 of 1557. Markdown https://www.anchorterminal.com/tools/liner-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/liner-mcp.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 353 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### Hyperresearch (B)\n\nGood for: Agents that need cited, quote-checked facts or long research reports and want to keep sources in a searchable vault.\n\nAhead on:\n- Schema \u0026 documentation, 76 against 45\n- Agent ergonomics, 83 against 65\n- Security \u0026 auth, 79 against 35\n- Payments \u0026 pricing, 60 against 30\n- Maintenance \u0026 community, 88 against 45\n- Transparency \u0026 trust, 71 against 34\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No status page, and the terms say there is no SLA and no uptime figure\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\nAhead on:\n- Reliability, 50 against 35\n\nWatch for: No free tier found\n\n\n## Why the edge\n\n### Security \u0026 auth: Hyperresearch +44\n\n- Hyperresearch (79): Bearer keys of 32 random bytes stored as salted hashes, shown once, scoped to `runs:read`, `runs:write`, `vault:read`, `vault:write`, `verify`, `mcp` and `admin`, with a last-used time, rotation with a 24-hour overlap and instant revocation, plus an IP allowlist. MCP uses OAuth with PKCE and a consent screen that lists each scope. The docs say never to put keys in URLs (30). A client that requests no scopes gets read-only access, billed scopes are marked on the consent screen, and every workspace has a spend cap. No confirmation step for deletes was found (16 of 20). The trust page documents `\u003cuntrusted-source\u003e` fences on every fetched body, forged fence tags neutralised, per-role tool allowlists, schema-validated arguments and private address ranges refused (15). A workspace audit log exportable as NDJSON, a 365-day default window, and a list of agent connections that can be revoked (15). No security.txt (404), no formal disclosure policy and no bug bounty, and the trust page says there is no SOC 2 report. Vulnerabilities go to support@hyperresearch.ai (3 of 20). 30+16+15+15+3 = 79.\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\n### Maintenance \u0026 community: Hyperresearch +43\n\n- Hyperresearch (88): The pricing and about pages were updated on 17 November 2026, and the open-source CLI that the hosted service runs was tagged v0.13.3 on 16 November (30). Four tagged CLI releases in the 90 days to this check: v0.13.0 (27 October), v0.13.1 (9 November), v0.13.2 (12 November), v0.13.3 (16 November) (20). The CLI changelog credits fixes to issues and pull requests from outside contributors (#71, #201 to #206). We didn't read the issue threads (15 of 25). `ai.hyperresearch/hyperresearch` and `ai.hyperresearch/answers` are in the official MCP registry under the vendor's domain namespace (15). The repository has CI and publish workflows, and AI SDK and LangChain packages are published (8 of 10). 30+20+15+15+8 = 88.\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\n### Transparency \u0026 trust: Hyperresearch +37\n\n- Hyperresearch (71): The hosted service is closed with terms from Thalient Labs Inc. (version 1.7), and the CLI that runs the same pipeline is MIT (20 of 30). The trust page states retention per record type (content kept until deleted, verification inputs 7 days, billing at least 7 years, audit log 365 days by default), names the known gaps (the run index and questions are kept indefinitely, no automatic expiry), says customer content isn't used for training, and says it matches the privacy policy. No DPA on the shelf (26 of 30). A written deprecation policy: at least six months' notice, `Deprecation` and `Sunset` headers and a list of deprecations, plus 30 days' notice by email before a shutdown (20). Subprocessors are listed with what each receives and their countries, and the trust page says there is no data residency guarantee on Cloudflare's network (18 of 20). 20+26+20+18 = 84.\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\n### Schema \u0026 documentation: Hyperresearch +31\n\n- Hyperresearch (76): llms.txt and the versioning page name an OpenAPI 3.1 document at api.hyperresearch.ai/v1/openapi.json, and the API reference has one page per operation generated from it. api.hyperresearch.ai's robots.txt asked for a sign-in, so read.py closed the host and the file wasn't read (20 of 25). llms.txt, and every docs page as Markdown with `.md` (10). The Answers page says when to use fast, standard, max or auto and that fast skips structured sources, and the docs say Answers is for one fact and runs for a report. The research MCP server's tool descriptions couldn't be read (12 of 20). Modes and run tiers are enums, and examples show `max_results`, but the schemas themselves weren't read (10 of 15). Request and result examples, one error envelope with status meanings and a stable `code` (14 of 15). The version is in the path (/v1) with an additive-only promise, but the hosted service has no public changelog. The open-source CLI's CHANGELOG.md is dated (10 of 15). 20+10+12+10+14+10 = 76.\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\n### Payments \u0026 pricing: Hyperresearch +30\n\n- Hyperresearch (60): No x402, MPP or L402 (0). Per-call prices for Answers and flat per-run prices (Light $9, Deep $49) are published without login, with rerun discounts and refund rules (30). $5 of Answers credit and the first Light report free on every account, no card needed, and `hr_test_` keys are never billed (30). A person signs up through Clerk in a browser and creates keys in the console, and MCP clients authorise in a browser (0). 0+30+30+0 = 60.\n- Liner Search MCP (30): No machine payment protocol (0). Per-call prices public (20). No free tier found (0). A person signs up in a browser for OAuth or an API key (0). 0 + 20 + 0 + 0 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.\n\n### Agent ergonomics: Hyperresearch +18\n\n- Hyperresearch (83): Answers is three compact tools (`data_and_web_answer`, `data_and_web_search` and the free `get_pending_answer`), and an answer returns only a short answer, its quotes and links. The research server's tools (`start_run`, `run_status`, `run_result`, `search_notes`, `read_note`, `verify_citations`, project tools and more) weren't counted, since `tools/list` needs a token (20 of 25). `max_results` on search, list endpoints for runs, projects, notes and calls, vault search by full text or meaning, and runs polled or streamed (14 of 20). Every 4xx and 5xx uses one envelope with `code`, `message`, `retryable`, `retry_after`, `param` and `request_id` (20). `Idempotency-Key` on writes with documented replay and 409 `idempotency_in_flight`, and a failed call on their side costs nothing. MCP tool annotations weren't readable (14 of 20). Only a query and a tier are required to start a run. Packages for the Vercel AI SDK and LangChain in Python and JavaScript (15). 20+14+20+14+15 = 83.\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\n## Score by category\n\n| Category | Weight | Hyperresearch | Liner Search MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 35 | 50 | Liner Search MCP +15 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 76 | 45 | Hyperresearch +31 |\n| Agent ergonomics | 13% | 83 | 65 | Hyperresearch +18 |\n| Security \u0026 auth | 14% | 79 | 35 | Hyperresearch +44 |\n| Payments \u0026 pricing | 10% | 60 | 30 | Hyperresearch +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 88 | 45 | Hyperresearch +43 |\n| Transparency \u0026 trust | 7% | 71 | 34 | Hyperresearch +37 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **68.1 · B** | **44.7 · E** | |\n\n## Facts side by side\n\n| Fact | Hyperresearch | Liner Search MCP |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | Hyperresearch | Liner |\n| Hosted endpoint | `https://answers.hyperresearch.ai/mcp` | `https://platform.liner.com/api/v1/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Pay per use | Paid |\n| Price for research search | $9 per transaction | not published |\n| x402 | no | no |\n| Tools exposed | none | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `ai.hyperresearch/answers` | `com.liner/search` |\n| Last release | 2026-11-16 | none |\n| Terms last updated | 2026-11-17 | no document linked |\n| Privacy policy last updated | 2026-11-17 | no document linked |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n\n## How the scores have moved\n\n### Hyperresearch\n\nNo score change since it was listed.\n\n### Liner Search MCP\n\n- +1.3 on 13 November 2026: checklist\n\n## Verdicts\n\n**Hyperresearch.** Agents can buy one checked answer from 2 cents a call or a full research report for $9 or $49, with scoped, rotatable keys, stable error codes, idempotency keys and a six-month deprecation promise. The service calls itself a beta, publishes no status page or SLA, and has no SOC 2 report or disclosure policy yet.\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## Before you call either\n\n### Hyperresearch\n\n1. Use Answers (`data_and_web_answer` with mode `auto`) for one fact, and start a Light or Deep run only when the user wants a written report\n2. Send an `Idempotency-Key` on every write and reuse it only with an unchanged body, so a retried run or answer is charged once\n3. Poll a run with `GET /v1/runs/{id}` about once a minute, or stream its events. A Light run takes about 30 to 40 minutes\n4. If a response has `retryable: false`, change the request rather than retrying. Branch on `error.code`, never on the message\n5. Use a key that starts `hr_test_` to build and test an integration without spending\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## Questions\n\n### Which is better for AI agents, Hyperresearch or Liner Search MCP?\n\nHyperresearch scores 68.1 (B) on agent readiness against Liner Search MCP's 44.7 (E), and leads in 6 of 7 scored categories. Liner Search MCP leads on reliability.\n\n### Do Hyperresearch and Liner Search MCP need an API key?\n\nHyperresearch takes an API key or an OAuth sign-in. Liner Search MCP uses an OAuth sign-in.\n\n### Can an agent call Hyperresearch and Liner Search MCP without installing anything?\n\nYes. Hyperresearch has a hosted endpoint at https://answers.hyperresearch.ai/mcp and Liner Search MCP at https://platform.liner.com/api/v1/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"hyperresearch\", \"b\": \"liner-mcp\"}`. From a terminal: `anchor compare hyperresearch liner-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/hyperresearch.json and https://www.anchorterminal.com/api/v1/tools/liner-mcp.json\n\n## Other comparisons with Hyperresearch or Liner Search MCP\n\n- [Web Search Tool on Amazon Bedrock AgentCore vs Hyperresearch](https://www.anchorterminal.com/compare/agentcore-web-search-vs-hyperresearch.md)\n- [Grounding with Bing Search vs Hyperresearch](https://www.anchorterminal.com/compare/bing-grounding-vs-hyperresearch.md)\n- [Brave Search API + MCP vs Hyperresearch](https://www.anchorterminal.com/compare/brave-search-mcp-vs-hyperresearch.md)\n- [Cloudflare Web Search API vs Hyperresearch](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-hyperresearch.md)\n- [DeepSeek Search and Fetch API vs Hyperresearch](https://www.anchorterminal.com/compare/deepseek-search-api-vs-hyperresearch.md)\n- [Exa API + MCP vs Hyperresearch](https://www.anchorterminal.com/compare/exa-mcp-vs-hyperresearch.md)\n- [Firecrawl MCP vs Hyperresearch](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-hyperresearch.md)\n- [Hyperresearch vs Kagi Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-kagi-search.md)\n- [Hyperresearch vs Mojeek Web Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-mojeek.md)\n- [Hyperresearch vs SearchAPI.io](https://www.anchorterminal.com/compare/hyperresearch-vs-searchapi-io.md)\n- [Hyperresearch vs SerpApi](https://www.anchorterminal.com/compare/hyperresearch-vs-serpapi.md)\n- [Hyperresearch vs Serper](https://www.anchorterminal.com/compare/hyperresearch-vs-serper.md)\n- [Hyperresearch vs SERPHouse](https://www.anchorterminal.com/compare/hyperresearch-vs-serphouse.md)\n- [Hyperresearch vs SerpKite](https://www.anchorterminal.com/compare/hyperresearch-vs-serpkite.md)\n- [Arcmira vs Hyperresearch](https://www.anchorterminal.com/compare/arcmira-vs-hyperresearch.md)\n- [Arcmira vs Liner Search MCP](https://www.anchorterminal.com/compare/arcmira-vs-liner-mcp.md)\n- [Exa API + MCP vs Liner Search MCP](https://www.anchorterminal.com/compare/exa-mcp-vs-liner-mcp.md)\n- [Grep AI vs Hyperresearch](https://www.anchorterminal.com/compare/grep-ai-vs-hyperresearch.md)\n- [Grep AI vs Liner Search MCP](https://www.anchorterminal.com/compare/grep-ai-vs-liner-mcp.md)\n- [Hyperresearch vs Linkup](https://www.anchorterminal.com/compare/hyperresearch-vs-linkup.md)\n- [Hyperresearch vs NewsCatcher](https://www.anchorterminal.com/compare/hyperresearch-vs-newscatcher.md)\n- [Hyperresearch vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/hyperresearch-vs-parallel-search-api.md)\n- [Hyperresearch vs Perplexity Search API](https://www.anchorterminal.com/compare/hyperresearch-vs-perplexity-search-api.md)\n- [Hyperresearch vs SpecStream](https://www.anchorterminal.com/compare/hyperresearch-vs-specstream.md)\n- [Hyperresearch vs Tavily API + MCP](https://www.anchorterminal.com/compare/hyperresearch-vs-tavily-mcp.md)\n- [Hyperresearch vs TinyFish Search](https://www.anchorterminal.com/compare/hyperresearch-vs-tinyfish-search.md)\n- [Hyperresearch vs Valyu](https://www.anchorterminal.com/compare/hyperresearch-vs-valyu.md)\n- [Hyperresearch vs You.com APIs](https://www.anchorterminal.com/compare/hyperresearch-vs-you-com-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 Perplexity Search API](https://www.anchorterminal.com/compare/liner-mcp-vs-perplexity-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- [Fetch (MCP reference server) vs Hyperresearch](https://www.anchorterminal.com/compare/fetch-reference-server-vs-hyperresearch.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-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "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": "Hyperresearch vs Liner Search MCP",
        "url": ""
      }
    ],
    "description": "Hyperresearch scores 68.1 (B) to Liner Search MCP's 44.7 (E) for research search. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Hyperresearch B 68.1",
      "Liner Search MCP E 44.7",
      "scores"
    ],
    "h1": "Hyperresearch vs Liner Search MCP",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/hyperresearch-vs-liner-mcp",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Hyperresearch vs Liner Search MCP for AI agents (2026)",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/hyperresearch-vs-liner-mcp"
  },
  "tokens": {
    "markdown": 4850,
    "slim": 1080
  },
  "version": 1
}
