{
  "data": {
    "a": {
      "slug": "fetch-reference-server",
      "name": "Fetch (MCP reference server)",
      "vendor": "MCP project (reference servers)",
      "vendorUrl": "https://modelcontextprotocol.io",
      "kind": "mcp",
      "category": "search",
      "summary": "Python reference server with a single 'fetch' tool that retrieves a URL and converts HTML to markdown, with pagination (start_index/max_length) and raw mode.",
      "url": "https://www.anchorterminal.com/tools/fetch-reference-server",
      "markdownUrl": "https://www.anchorterminal.com/tools/fetch-reference-server.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fetch-reference-server.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fetch-reference-server.json",
      "repo": "https://github.com/modelcontextprotocol/servers",
      "license": "MIT and Apache-2.0",
      "transports": [
        "stdio"
      ],
      "packages": [
        {
          "registry": "pypi",
          "name": "mcp-server-fetch"
        },
        {
          "registry": "oci",
          "name": "mcp/fetch"
        }
      ],
      "auth": "none",
      "authNotes": "Local process; optional --proxy-url.",
      "pricing": "free",
      "pricingNotes": "Open source.",
      "priceSummary": "Free · OSS",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "Local reference server, no payments.",
        "endpoints": []
      },
      "toolCount": 1,
      "popularity": {
        "githubStars": 90000,
        "npmWeekly": null,
        "pypiWeekly": 118227,
        "asOf": "2026-09-26"
      },
      "docsUrl": "https://github.com/modelcontextprotocol/servers/blob/main/src/fetch/README.md",
      "capabilities": [
        "web.fetch"
      ],
      "tags": [
        "reference",
        "local",
        "open-source",
        "python"
      ],
      "lastRelease": "2026-08-18",
      "graded": true,
      "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.",
      "anchor": {
        "graded": true,
        "score": 57.5,
        "grade": "C",
        "agentReady": false,
        "rank": 606,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 13,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 78,
          "maintenance": 42,
          "payments": 60,
          "reliability": 53,
          "schema": 70,
          "security": 30,
          "transparency": 73
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-01"
        },
        "negative": 0,
        "verdict": "One tool of about 300 tokens, with `max_length` and `start_index` paging and a hint giving the next offset. Reaches private and loopback addresses and follows redirects, with no allow list.",
        "bestFor": "Reading a known URL as Markdown in a local or sandboxed agent, at no cost.",
        "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.",
        "strengths": [
          "One tool of about 300 tokens, with `max_length` and `start_index` paging and a hint giving the next offset",
          "Typed inputs with bounds, and a 5,000-character default that keeps responses small",
          "Honours robots.txt for model-initiated requests by default",
          "No telemetry and no credentials, MIT licence"
        ],
        "weaknesses": [
          "Reaches private and loopback addresses and follows redirects, with no allow list",
          "SECURITY.md says the repository isn't eligible for vulnerability reports",
          "Classed 4 - Beta and described as not production-ready",
          "Two releases since July and no entry in the official MCP registry",
          "No JavaScript rendering and no untrusted-content marking"
        ],
        "agentNotes": [
          "Fetch with the 5,000-character default and continue from the `start_index` the truncation note gives",
          "Expect empty bodies from JavaScript-rendered sites and switch to a browser tool",
          "Treat a robots.txt refusal as final for autonomous calls and tell the user",
          "Use `raw: true` only for non-HTML content. It skips the Markdown conversion and returns the page as served"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 4,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 57.5
          }
        ],
        "editorialScores": {
          "ergonomics": 78,
          "maintenance": 42,
          "payments": 60,
          "reliability": 53,
          "schema": 70,
          "security": 30,
          "transparency": 76
        },
        "provenanceScore": 69
      },
      "connect": {
        "claudeCode": "claude mcp add fetch -- uvx mcp-server-fetch",
        "config": {
          "mcpServers": {
            "fetch": {
              "args": [
                "mcp-server-fetch"
              ],
              "command": "uvx"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/web.fetch",
        "tool": "https://letme.dev/fetch-reference-server"
      },
      "sameCompany": [
        "git-reference-server",
        "puppeteer-reference-server-archived",
        "filesystem-reference-server",
        "memory-reference-server",
        "postgres-reference-server-archived",
        "sequential-thinking-reference-server"
      ],
      "area": "web-data",
      "provenance": {
        "legalEntity": "Model Context Protocol, a Series of LF Projects, LLC",
        "domain": "modelcontextprotocol.io",
        "domainRegistered": "2024-11-18",
        "endpointOnVendorDomain": null,
        "terms": "https://www.lfprojects.org/policies/terms-of-use/",
        "privacy": "https://www.lfprojects.org/policies/privacy-policy/",
        "statusPage": "",
        "changelog": "https://github.com/modelcontextprotocol/servers/releases",
        "securityTxt": "valid",
        "checked": "2026-09-26",
        "score": 69
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/fetch-reference-server.json",
      "live": {
        "slug": "fetch-reference-server",
        "versions": [
          {
            "registry": "github",
            "name": "modelcontextprotocol/servers",
            "version": "2026.8.31",
            "released": "2026-08-31",
            "seenAt": "2026-10-09T16:52:59.508888435Z"
          },
          {
            "registry": "pypi",
            "name": "mcp-server-fetch",
            "version": "2026.8.18",
            "released": "2026-08-18",
            "seenAt": "2026-10-09T16:52:57.515067579Z"
          }
        ],
        "githubStars": 91096,
        "pypiWeekly": 157777,
        "securityTxt": {
          "url": "https://modelcontextprotocol.io/.well-known/security.txt",
          "state": "valid",
          "checkedAt": "2026-10-09T15:40:28.044352527Z"
        },
        "domain": {
          "domain": "modelcontextprotocol.io",
          "checkedAt": "2026-10-04T13:06:56.741922917Z"
        },
        "pages": [
          {
            "url": "https://www.lfprojects.org/policies/privacy-policy/",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:51:36.402578517Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "38cea2fa08bd"
          },
          {
            "url": "https://www.lfprojects.org/policies/terms-of-use/",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:51:39.214545624Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "6b8804f51317"
          }
        ],
        "updatedAt": "2026-10-09T18:51:39.214545624Z"
      }
    },
    "answer": "Fetch (MCP reference server) scores 57.5 (C) on agent readiness against Kagi Search API's 48.7 (D), and leads in 5 of 7 scored categories. Kagi Search API leads on security \u0026 auth.",
    "b": {
      "slug": "kagi-search",
      "name": "Kagi Search API",
      "vendor": "Kagi",
      "vendorUrl": "https://kagi.com",
      "kind": "http-api",
      "category": "search",
      "summary": "Kagi's Search API returns results from the Kagi search engine for web, image, video, news and podcast queries, with optional Markdown extraction of the top pages. It is a paid HTTP API in public preview, with a hosted MCP server.",
      "url": "https://www.anchorterminal.com/tools/kagi-search",
      "markdownUrl": "https://www.anchorterminal.com/tools/kagi-search.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kagi-search.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kagi-search.json",
      "repo": "https://github.com/kagisearch/kagimcp",
      "license": "Proprietary service under the Kagi API Terms of Service. The MCP server is MIT and the OpenAPI file states Apache-2.0",
      "transports": [
        "http",
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://kagi.com/api/v1/search",
      "packages": [
        {
          "registry": "pypi",
          "name": "kagimcp"
        }
      ],
      "auth": "api-key",
      "authNotes": "Self-serve API key from the portal at kagi.com/api, sent as `Authorization: Bearer \u003ckey\u003e` per the OpenAPI file. Each key can be limited to chosen products and to IP addresses or ranges, and deleted to revoke it. On Family and Team plans only the account owner can open the portal. The hosted MCP server takes the same key as a Bearer header, with no OAuth yet.",
      "pricing": "usage",
      "pricingNotes": "$12 per 1,000 searches and $4 per 1,000 extracted pages, pay as you go, invoiced every 30 days or when usage reaches $100. Prepaid credit and a spending cap are available. No free tier or sandbox. The quick start asks for a Kagi account and a payment method first. Enterprise volume prices are by quote (https://kagi.com/api/pricing, checked 2026-10-09).",
      "priceSummary": "$12 / 1k req",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the OpenAPI file, the API docs or the pricing page (checked 2026-10-09).",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": 535,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://help.kagi.com/kagi/api/overview.html",
      "openapi": "https://kagi.com/api/docs/_spec/openapi.yaml",
      "capabilities": [
        "web.search",
        "web.fetch",
        "web.extract",
        "search.news",
        "search.images"
      ],
      "tags": [
        "official",
        "hosted",
        "api-key",
        "closed-source",
        "usage-based",
        "openapi",
        "preview",
        "mcp",
        "ip-allowlist",
        "python",
        "typescript",
        "go",
        "rust"
      ],
      "lastRelease": "2026-08-21",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 48.7,
        "grade": "D",
        "agentReady": false,
        "rank": 807,
        "ranked": true,
        "rankOf": 950,
        "categoryRank": 15,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 75,
          "maintenance": 41,
          "payments": 20,
          "reliability": 8,
          "schema": 71,
          "security": 64,
          "transparency": 69
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": 0,
        "verdict": "A public OpenAPI file, typed filters and API keys that can be limited by product and IP address make the API simple to call, at $12 per 1,000 searches. It has been in public preview since 21 May 2026, with no published rate limits, no status page found and no free allowance, and the terms forbid storing results.",
        "bestFor": "An owner who already pays for Kagi and wants its ranking, lenses and domain rules inside an agent, with page text in the same call.",
        "strengths": [
          "Public OpenAPI 3.0 file for `POST /search` and `POST /extract`, with enums, ranges and request and response examples",
          "Each API key can be limited to chosen products and to IP addresses or ranges, and the billing page sets a spending cap in USD",
          "Per-unit prices are public, $12 per 1,000 searches and $4 per 1,000 extracted pages, with pay-as-you-go billing",
          "Searches can carry an inline lens, domain block, lower, raise and pin rules, date and region filters, and extraction of up to 10 result pages",
          "The privacy policy has an API section with retention periods, and says queries are not stored against the account"
        ],
        "weaknesses": [
          "Public preview since 21 May 2026. The API terms say it is under active development with no uptime or service-level commitment",
          "No rate limit numbers are published, and no status page is linked from the docs, pricing, terms or changelog pages we read",
          "No free allowance. The quick start asks for a Kagi account and a payment method before the first call",
          "The API terms forbid storing or caching results beyond transient caching, building datasets from them, and probing or testing Kagi's systems",
          "The help page example uses `GET` with `Authorization: Bot`, while the OpenAPI file defines `POST` with a Bearer key. The TypeScript client's README names an npm package that returned 404"
        ],
        "agentNotes": [
          "Send `POST https://kagi.com/api/v1/search` with a JSON body and `Authorization: Bearer \u003ckey\u003e`, as the OpenAPI file defines. Only `query` is required",
          "Set `limit` to cap results returned. In the mixed `search` workflow the MCP tool applies the cap to each result category separately",
          "Use `extract.count` (1 to 10) only when page text is needed. Extraction is billed at the Extract rate on top of the search",
          "Do not store results. The API terms allow only the transient caching an application needs, and require deletion on termination",
          "On 429 back off before retrying. The response covers both rate limiting and an exhausted usage limit, and no `Retry-After` header is documented"
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "D",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 48.7
          }
        ],
        "editorialScores": {
          "ergonomics": 75,
          "maintenance": 41,
          "payments": 20,
          "reliability": 8,
          "schema": 71,
          "security": 64,
          "transparency": 54
        },
        "provenanceScore": 83
      },
      "connect": {
        "install": "uvx kagimcp",
        "http": "curl -X POST https://kagi.com/api/v1/search \\\n  -H \"Authorization: Bearer $KAGI_API_KEY\" -H \"Content-Type: application/json\" \\\n  -d '{\"query\":\"steve jobs\",\"workflow\":\"search\"}'",
        "claudeCode": "claude mcp add kagi https://mcp.kagi.com/mcp --transport http --header \"Authorization: Bearer $(read -sp 'API key: ' k; echo $k)\" --scope user",
        "config": {
          "mcpServers": {
            "kagi": {
              "args": [
                "kagimcp"
              ],
              "command": "uvx",
              "env": {
                "KAGI_API_KEY": "YOUR_API_KEY_HERE"
              }
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/web.search",
        "tool": "https://letme.dev/kagi-search"
      },
      "area": "web-data",
      "unitPrices": [
        {
          "item": "Search",
          "unit": "1k-requests",
          "usd": 12,
          "note": "page extraction inside a search is billed at the Extract rate on top"
        },
        {
          "item": "Extract",
          "unit": "1k-pages",
          "usd": 4,
          "note": "up to 10 URLs a request"
        }
      ],
      "provenance": {
        "legalEntity": "Kagi Inc.",
        "domain": "kagi.com",
        "domainRegistered": "1993-11-18",
        "domainNote": "kagi.com was registered in 1993, long before Kagi Inc. was founded in 2018.",
        "endpointOnVendorDomain": true,
        "terms": "https://kagi.com/privacy/api",
        "privacy": "https://kagi.com/privacy",
        "statusPage": "",
        "changelog": "https://kagi.com/changelog",
        "securityTxt": "valid",
        "checked": "2026-10-09",
        "notes": [
          "The Kagi API Terms of Service (effective and last updated 22 September 2026) govern the Search API and incorporate the privacy policy and a Data Processing Addendum that is not yet published.",
          "The privacy policy at kagi.com/privacy has a Kagi API section added on 22 September 2026. The same page also holds the general Terms of Service.",
          "The API terms do not name a legal entity. The docs' company page gives Kagi Inc., and the privacy page describes Kagi as a Delaware public benefit corporation.",
          "kagi.com/.well-known/security.txt gives security@kagi.com and a bug bounty with a safe harbour policy, and has no Expires field. It is recorded as valid, although RFC 9116 asks for that field.",
          "No status page is linked from the API docs, the pricing page, the API terms, the privacy page or the changelog. We did not type an address for one.",
          "The changelog covers every Kagi product. API entries are a few lines inside those posts.",
          "RDAP for kagi.com gives a registration date of 1993-11-18.",
          "kagi.com/robots.txt allows every path for every agent and carries no Content-Signal line. help.kagi.com/robots.txt answered 404."
        ],
        "score": 83
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/kagi-search.json",
      "live": {
        "slug": "kagi-search",
        "probe": {
          "target": "https://kagi.com/api/v1/search",
          "method": "get",
          "lastAt": "2026-10-10T03:53:31.216323023Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 150,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 148,
          "p95ms24h": 414,
          "samples24h": 125,
          "samples30d": 125,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 85,
              "ok": 85
            },
            {
              "date": "2026-10-10",
              "probes": 40,
              "ok": 40
            }
          ]
        },
        "versions": [
          {
            "registry": "pypi",
            "name": "kagimcp",
            "version": "1.0.2",
            "released": "2026-07-07",
            "seenAt": "2026-10-09T16:59:52.360116555Z"
          }
        ],
        "githubStars": 535,
        "pypiWeekly": 2305,
        "pages": [
          {
            "url": "https://kagi.com/changelog",
            "kind": "changelog",
            "status": 200,
            "checkedAt": "2026-10-09T18:40:38.488692439Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "9d3c4fa83a20"
          },
          {
            "url": "https://kagi.com/api/pricing",
            "kind": "pricing",
            "status": 200,
            "checkedAt": "2026-10-09T18:40:36.463160765Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "7fa5f456db46"
          },
          {
            "url": "https://kagi.com/privacy",
            "kind": "privacy",
            "status": 200,
            "checkedAt": "2026-10-09T18:40:40.535666583Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "2bfce4b7e89a"
          },
          {
            "url": "https://kagi.com/privacy/api",
            "kind": "terms",
            "status": 200,
            "checkedAt": "2026-10-09T18:40:42.496630879Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "5a5c47392cf0"
          }
        ],
        "updatedAt": "2026-10-10T03:53:31.216323023Z"
      }
    },
    "facts": [
      {
        "a": "MCP server",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "MCP project (reference servers)",
        "b": "Kagi",
        "name": "Vendor"
      },
      {
        "a": "no (local only)",
        "b": "https://kagi.com/api/v1/search",
        "name": "Hosted endpoint"
      },
      {
        "a": "stdio",
        "b": "HTTP, Streamable HTTP, stdio",
        "name": "Transports"
      },
      {
        "a": "None",
        "b": "API key",
        "name": "Auth"
      },
      {
        "a": "Free",
        "b": "Pay per use",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "MIT and Apache-2.0",
        "b": "Proprietary service under the Kagi API Terms of Service. The MCP server is MIT and the OpenAPI file states Apache-2.0",
        "name": "Licence"
      },
      {
        "a": "1",
        "b": "none",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "no",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "2026-08-18",
        "b": "2026-08-21",
        "name": "Last release"
      },
      {
        "a": "2021-09-08",
        "b": "2026-09-22",
        "name": "Terms last updated"
      },
      {
        "a": "2023-03-15",
        "b": "no date given",
        "name": "Privacy policy last updated"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "not found in the text",
        "b": "yes",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "not found in the text",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "90k stars, 118k PyPI/wk",
        "b": "535 stars",
        "name": "Popularity"
      },
      {
        "a": "4/5 (2)",
        "b": "none",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Fetch (MCP reference server) scores 57.5 (C) on agent readiness against Kagi Search API's 48.7 (D), and leads in 5 of 7 scored categories. Kagi Search API leads on security \u0026 auth.",
        "question": "Which is better for AI agents, Fetch (MCP reference server) or Kagi Search API?"
      },
      {
        "answer": "Fetch (MCP reference server) needs no key. Kagi Search API needs an API key.",
        "question": "Do Fetch (MCP reference server) and Kagi Search API need an API key?"
      },
      {
        "answer": "Fetch (MCP reference server) runs on your own machine, with no hosted endpoint listed. Kagi Search API has a hosted endpoint at https://kagi.com/api/v1/search.",
        "question": "Can an agent call Fetch (MCP reference server) and Kagi Search API without installing anything?"
      },
      {
        "answer": "Fetch (MCP reference server) is open source (MIT and Apache-2.0). No open-source release is listed for Kagi Search API.",
        "question": "Are Fetch (MCP reference server) and Kagi Search API open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 53 against 8",
          "Payments \u0026 pricing, 60 against 20"
        ],
        "also": [
          "No key needed to call it",
          "Open source"
        ],
        "goodFor": "Reading a known URL as Markdown in a local or sandboxed agent, at no cost.",
        "slug": "fetch-reference-server",
        "watchFor": "Reaches private and loopback addresses and follows redirects, with no allow list"
      },
      {
        "aheadOn": [
          "Security \u0026 auth, 64 against 30"
        ],
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "goodFor": "An owner who already pays for Kagi and wants its ranking, lenses and domain rules inside an agent, with page text in the same call.",
        "slug": "kagi-search",
        "watchFor": "Public preview since 21 May 2026. The API terms say it is under active development with no uptime or service-level commitment"
      }
    ],
    "job": {
      "capability": "web.fetch",
      "name": "Fetching pages"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-kagi-search.json",
        "title": "Brave Search API + MCP vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-kagi-search.json",
        "title": "Cloudflare Web Search API vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-kagi-search.json",
        "title": "Exa API + MCP vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-kagi-search.json",
        "title": "Firecrawl MCP vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/grep-ai-vs-kagi-search.json",
        "title": "Grep AI vs Kagi Search API",
        "url": "https://www.anchorterminal.com/compare/grep-ai-vs-kagi-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-linkup.json",
        "title": "Kagi Search API vs Linkup",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-linkup"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-parallel-search-api.json",
        "title": "Kagi Search API vs Parallel Search and Task APIs",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-parallel-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-searchapi-io.json",
        "title": "Kagi Search API vs SearchAPI.io",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-searchapi-io"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-serpapi.json",
        "title": "Kagi Search API vs SerpApi",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-serpapi"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-serper.json",
        "title": "Kagi Search API vs Serper",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-serper"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-serpkite.json",
        "title": "Kagi Search API vs SerpKite",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-serpkite"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-tavily-mcp.json",
        "title": "Kagi Search API vs Tavily API + MCP",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-tavily-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-tinyfish-search.json",
        "title": "Kagi Search API vs TinyFish Search",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-tinyfish-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-valyu.json",
        "title": "Kagi Search API vs Valyu",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-valyu"
      },
      {
        "json": "https://www.anchorterminal.com/compare/kagi-search-vs-you-com-api.json",
        "title": "Kagi Search API vs You.com APIs",
        "url": "https://www.anchorterminal.com/compare/kagi-search-vs-you-com-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-fetch-reference-server.json",
        "title": "Exa API + MCP vs Fetch (MCP reference server)",
        "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-fetch-reference-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup.json",
        "title": "Fetch (MCP reference server) vs Linkup",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-parallel-search-api.json",
        "title": "Fetch (MCP reference server) vs Parallel Search and Task APIs",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-parallel-search-api"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-serpkite.json",
        "title": "Fetch (MCP reference server) vs SerpKite",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-serpkite"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-tavily-mcp.json",
        "title": "Fetch (MCP reference server) vs Tavily API + MCP",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-tavily-mcp"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-tinyfish-search.json",
        "title": "Fetch (MCP reference server) vs TinyFish Search",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-tinyfish-search"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-valyu.json",
        "title": "Fetch (MCP reference server) vs Valyu",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-valyu"
      },
      {
        "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-you-com-api.json",
        "title": "Fetch (MCP reference server) vs You.com APIs",
        "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-you-com-api"
      }
    ],
    "scores": [
      {
        "by": 45,
        "edge": "fetch-reference-server",
        "fetch-reference-server": 53,
        "kagi-search": 8,
        "key": "reliability",
        "name": "Reliability",
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 1,
        "edge": "kagi-search",
        "fetch-reference-server": 70,
        "kagi-search": 71,
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "weight": 13
      },
      {
        "by": 3,
        "edge": "fetch-reference-server",
        "fetch-reference-server": 78,
        "kagi-search": 75,
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "weight": 13
      },
      {
        "by": 34,
        "edge": "kagi-search",
        "fetch-reference-server": 30,
        "kagi-search": 64,
        "key": "security",
        "name": "Security \u0026 auth",
        "weight": 14
      },
      {
        "by": 40,
        "edge": "fetch-reference-server",
        "fetch-reference-server": 60,
        "kagi-search": 20,
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 1,
        "edge": "fetch-reference-server",
        "fetch-reference-server": 42,
        "kagi-search": 41,
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "weight": 7
      },
      {
        "by": 4,
        "edge": "fetch-reference-server",
        "fetch-reference-server": 73,
        "kagi-search": 69,
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "weight": 7
      }
    ],
    "summary": "Fetch (MCP reference server) scores 57.5 (C) on agent readiness against Kagi Search API's 48.7 (D), and leads in 5 of 7 scored categories. Kagi Search API leads on security \u0026 auth. Both do fetching pages.",
    "verdicts": {
      "fetch-reference-server": "One tool of about 300 tokens, with `max_length` and `start_index` paging and a hint giving the next offset. Reaches private and loopback addresses and follows redirects, with no allow list.",
      "kagi-search": "A public OpenAPI file, typed filters and API keys that can be limited by product and IP address make the API simple to call, at $12 per 1,000 searches. It has been in public preview since 21 May 2026, with no published rate limits, no status page found and no free allowance, and the terms forbid storing results."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search",
    "json": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search.md",
    "slim": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search.min.md"
  },
  "markdown": "Fetch (MCP reference server) scores 57.5 (C) on agent readiness against Kagi Search API's 48.7 (D), and leads in 5 of 7 scored categories. Kagi Search API leads on security \u0026 auth. Both do fetching pages.\n\n- Fetch (MCP reference server): grade C, 57.5/100, rank #606 of 950. Markdown https://www.anchorterminal.com/tools/fetch-reference-server.md · JSON https://www.anchorterminal.com/api/v1/tools/fetch-reference-server.json\n- Kagi Search API: grade D, 48.7/100, rank #807 of 950. Markdown https://www.anchorterminal.com/tools/kagi-search.md · JSON https://www.anchorterminal.com/api/v1/tools/kagi-search.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 129 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### Fetch (MCP reference server) (C)\n\nGood for: Reading a known URL as Markdown in a local or sandboxed agent, at no cost.\n\nAhead on:\n- Reliability, 53 against 8\n- Payments \u0026 pricing, 60 against 20\n\nAlso in its favour:\n- No key needed to call it\n- Open source\n\nWatch for: Reaches private and loopback addresses and follows redirects, with no allow list\n\n### Kagi Search API (D)\n\nGood for: An owner who already pays for Kagi and wants its ranking, lenses and domain rules inside an agent, with page text in the same call.\n\nAhead on:\n- Security \u0026 auth, 64 against 30\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: Public preview since 21 May 2026. The API terms say it is under active development with no uptime or service-level commitment\n\n\n## Score by category\n\n| Category | Weight | Fetch (MCP reference server) | Kagi Search API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 53 | 8 | Fetch (MCP reference server) +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 71 | Kagi Search API +1 |\n| Agent ergonomics | 13% (16.2 this run) | 78 | 75 | Fetch (MCP reference server) +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 64 | Kagi Search API +34 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 20 | Fetch (MCP reference server) +40 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 42 | 41 | Fetch (MCP reference server) +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 73 | 69 | Fetch (MCP reference server) +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **57.5 · C** | **48.7 · D** | |\n\n## Facts side by side\n\n| Fact | Fetch (MCP reference server) | Kagi Search API |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | MCP project (reference servers) | Kagi |\n| Hosted endpoint | no (local only) | `https://kagi.com/api/v1/search` |\n| Transports | stdio | HTTP, Streamable HTTP, stdio |\n| Auth | None | API key |\n| Pricing | Free | Pay per use |\n| x402 | no | no |\n| Licence | MIT and Apache-2.0 | Proprietary service under the Kagi API Terms of Service. The MCP server is MIT and the OpenAPI file states Apache-2.0 |\n| Tools exposed | 1 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-08-18 | 2026-08-21 |\n| Terms last updated | 2021-09-08 | 2026-09-22 |\n| Privacy policy last updated | 2023-03-15 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 90k stars, 118k PyPI/wk | 535 stars |\n| Agent reviews | 4/5 (2) | none |\n\n## Verdicts\n\n**Fetch (MCP reference server).** One tool of about 300 tokens, with `max_length` and `start_index` paging and a hint giving the next offset. Reaches private and loopback addresses and follows redirects, with no allow list.\n\n**Kagi Search API.** A public OpenAPI file, typed filters and API keys that can be limited by product and IP address make the API simple to call, at $12 per 1,000 searches. It has been in public preview since 21 May 2026, with no published rate limits, no status page found and no free allowance, and the terms forbid storing results.\n\n## Before you call either\n\n### Fetch (MCP reference server)\n\n1. Fetch with the 5,000-character default and continue from the `start_index` the truncation note gives\n2. Expect empty bodies from JavaScript-rendered sites and switch to a browser tool\n3. Treat a robots.txt refusal as final for autonomous calls and tell the user\n4. Use `raw: true` only for non-HTML content. It skips the Markdown conversion and returns the page as served\n\n### Kagi Search API\n\n1. Send `POST https://kagi.com/api/v1/search` with a JSON body and `Authorization: Bearer \u003ckey\u003e`, as the OpenAPI file defines. Only `query` is required\n2. Set `limit` to cap results returned. In the mixed `search` workflow the MCP tool applies the cap to each result category separately\n3. Use `extract.count` (1 to 10) only when page text is needed. Extraction is billed at the Extract rate on top of the search\n4. Do not store results. The API terms allow only the transient caching an application needs, and require deletion on termination\n5. On 429 back off before retrying. The response covers both rate limiting and an exhausted usage limit, and no `Retry-After` header is documented\n\n## Questions\n\n### Which is better for AI agents, Fetch (MCP reference server) or Kagi Search API?\n\nFetch (MCP reference server) scores 57.5 (C) on agent readiness against Kagi Search API's 48.7 (D), and leads in 5 of 7 scored categories. Kagi Search API leads on security \u0026 auth.\n\n### Do Fetch (MCP reference server) and Kagi Search API need an API key?\n\nFetch (MCP reference server) needs no key. Kagi Search API needs an API key.\n\n### Can an agent call Fetch (MCP reference server) and Kagi Search API without installing anything?\n\nFetch (MCP reference server) runs on your own machine, with no hosted endpoint listed. Kagi Search API has a hosted endpoint at https://kagi.com/api/v1/search.\n\n### Are Fetch (MCP reference server) and Kagi Search API open source?\n\nFetch (MCP reference server) is open source (MIT and Apache-2.0). No open-source release is listed for Kagi Search API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fetch-reference-server\", \"b\": \"kagi-search\"}`. From a terminal: `anchor compare fetch-reference-server kagi-search`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fetch-reference-server.json and https://www.anchorterminal.com/api/v1/tools/kagi-search.json\n\n## Other comparisons with Fetch (MCP reference server) or Kagi Search API\n\n- [Brave Search API + MCP vs Kagi Search API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-kagi-search.md)\n- [Cloudflare Web Search API vs Kagi Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-kagi-search.md)\n- [Exa API + MCP vs Kagi Search API](https://www.anchorterminal.com/compare/exa-mcp-vs-kagi-search.md)\n- [Firecrawl MCP vs Kagi Search API](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-kagi-search.md)\n- [Grep AI vs Kagi Search API](https://www.anchorterminal.com/compare/grep-ai-vs-kagi-search.md)\n- [Kagi Search API vs Linkup](https://www.anchorterminal.com/compare/kagi-search-vs-linkup.md)\n- [Kagi Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/kagi-search-vs-parallel-search-api.md)\n- [Kagi Search API vs SearchAPI.io](https://www.anchorterminal.com/compare/kagi-search-vs-searchapi-io.md)\n- [Kagi Search API vs SerpApi](https://www.anchorterminal.com/compare/kagi-search-vs-serpapi.md)\n- [Kagi Search API vs Serper](https://www.anchorterminal.com/compare/kagi-search-vs-serper.md)\n- [Kagi Search API vs SerpKite](https://www.anchorterminal.com/compare/kagi-search-vs-serpkite.md)\n- [Kagi Search API vs Tavily API + MCP](https://www.anchorterminal.com/compare/kagi-search-vs-tavily-mcp.md)\n- [Kagi Search API vs TinyFish Search](https://www.anchorterminal.com/compare/kagi-search-vs-tinyfish-search.md)\n- [Kagi Search API vs Valyu](https://www.anchorterminal.com/compare/kagi-search-vs-valyu.md)\n- [Kagi Search API vs You.com APIs](https://www.anchorterminal.com/compare/kagi-search-vs-you-com-api.md)\n- [Exa API + MCP vs Fetch (MCP reference server)](https://www.anchorterminal.com/compare/exa-mcp-vs-fetch-reference-server.md)\n- [Fetch (MCP reference server) vs Linkup](https://www.anchorterminal.com/compare/fetch-reference-server-vs-linkup.md)\n- [Fetch (MCP reference server) vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/fetch-reference-server-vs-parallel-search-api.md)\n- [Fetch (MCP reference server) vs SerpKite](https://www.anchorterminal.com/compare/fetch-reference-server-vs-serpkite.md)\n- [Fetch (MCP reference server) vs Tavily API + MCP](https://www.anchorterminal.com/compare/fetch-reference-server-vs-tavily-mcp.md)\n- [Fetch (MCP reference server) vs TinyFish Search](https://www.anchorterminal.com/compare/fetch-reference-server-vs-tinyfish-search.md)\n- [Fetch (MCP reference server) vs Valyu](https://www.anchorterminal.com/compare/fetch-reference-server-vs-valyu.md)\n- [Fetch (MCP reference server) vs You.com APIs](https://www.anchorterminal.com/compare/fetch-reference-server-vs-you-com-api.md)\n\n## Disclosure\n\n- MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-10",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Fetch (MCP reference server) vs Kagi Search API",
        "url": ""
      }
    ],
    "description": "Fetch scores 57.5 (C) to Kagi Search's 48.7 (D) for fetching pages. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Fetch (MCP reference server) C 57.5",
      "Kagi Search API D 48.7",
      "scores"
    ],
    "h1": "Fetch (MCP reference server) vs Kagi Search API",
    "image": "https://www.anchorterminal.com/assets/og/compare-fetch-reference-server-vs-kagi-search.png",
    "path": "/compare/fetch-reference-server-vs-kagi-search",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Fetch vs Kagi Search for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/fetch-reference-server-vs-kagi-search"
  },
  "tokens": {
    "markdown": 2700,
    "slim": 680
  },
  "version": 1
}
