RReadwise MCP (remote)

Vendor-hosted
What we probed (2026-11-03 UTC, no credentials): an MCP initialize POST to https://mcp2.readwise.io/mcp returned HTTP 401 with an OAuth challenge (WWW-Authenticate resource_metadata https://mcp2.readwise.io/.well-known/oauth-protected-resource/mcp); that metadata lists authorization server https://readwise.io/o/. We did not sign in, so no tools were listed or called. Readwise publishes 36 tool names on readwise.io/mcp; we did not verify them. The npm package @readwise/readwise-mcp (older Readwise-only server, being deprecated per Readwise docs) was not tested. Handshake scored 5/30 under the sign-in rule.
Claude Code 2.1.321 fixed MCP OAuth requests sending secrets such as refresh tokens to another host when a server redirected them. Claude Code changelog
Readwise-hosted MCP; OAuth sign-in with a Readwise account required. Listed under the vendor-hosted rule (Our review, Nov 2, 2026).
Sources: https://readwise.io/mcp · https://docs.readwise.io/tools/mcp · https://docs.readwise.io/changelog#october-30-2026

Transport: Streamable HTTP · not tested

Score 65/100 · Tools 0 · Token cost pending · Compare · Last tested 2026-11-03 · Server version not reported · Remote endpoint https://mcp2.readwise.io/mcp (streamable-http)

Summary: Readwise MCP (remote) requires credentials or a backing service before it will list tools.

Evidence summary

Handshake

auth-gated

Tools listed

0

Context cost

Pending The token cost figure is pending. ranking

Login

Needs OAuth sign-in

Tested

2026-11-03

Test results

Local-model readiness

What we tested and what we didn't

Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that giving it access to your data carries no risk.

{
  "name": "readwise-remote",
  "version": null,
  "registry": "remote",
  "status": "auth-gated",
  "tested": "2026-11-03",
  "tools_count": null,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://mcp2.readwise.io/mcp reachable over streamable-http (HTTP 401) in 0.1s; no install step for remote servers."
    ],
    "handshake": [
      "auth-gated",
      5,
      "Needs credentials: vendor-hosted, OAuth sign-in required. HTTP 401 with OAuth challenge (WWW-Authenticate resource_metadata https://mcp2.readwise.io/.well-known/oauth-protected-resource/mcp; metadata lists authorization server https://readwise.io/o/). We do not sign in; not counted as working until a credentialed test exists."
    ],
    "maintenance": [
      "pass",
      25,
      "Vendor-hosted rule: scored from dated Readwise changelog entry 2026-10-30 (https://docs.readwise.io/changelog#october-30-2026), 4 days before test. Registry: Not found in the official MCP registry (checked 2026-11-03 UTC)."
    ],
    "docs": [
      "pass",
      15,
      "official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://readwise.io/mcp, https://docs.readwise.io/tools/mcp)."
    ],
    "license": [
      "fail",
      0,
      "Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
    ]
  }
}

Install

https://mcp2.readwise.io/mcpCopy

Tools listed

Not available (handshake did not complete without credentials).

Quick config

{
  "mcpServers": {
    "readwise-mcp-remote": {
      "type": "http",
      "url": "https://mcp2.readwise.io/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

{
  "mcpServers": {
    "readwise-mcp-remote": {
      "type": "http",
      "url": "https://mcp2.readwise.io/mcp"
    }
  }
}

Related: Troubleshooting: 401 Unauthorized on remote servers · MCP servers that need an OAuth sign-in · How to protect AI API keys

FAQ

Is Readwise MCP deprecated?

No. readwise-remote was not deprecated or archived when we last tested it on 2026-11-03.

What replaces Readwise MCP?

Nothing; Readwise MCP (remote) is not deprecated as of 2026-11-03.

Does Readwise MCP need an API key?

Not an API key: it needs an OAuth sign-in. Without signing in, the endpoint returned HTTP 401 with an OAuth challenge and did not list tools.

Embed the badge

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Copy HTML

Copy Markdown Claim this listing · Report an issue