DEV Community

Iliya Oblakov
Iliya Oblakov

Posted on

I rechecked 23 public MCP issues on GitHub. OAuth sign-in and docs mismatches came up most.

On 10 November 2026 I went through public GitHub issues on MCP servers that were already in that week's research notes, and rechecked each issue the same day through the public GitHub Issues API. The set is 23 issues, and two classes came up more than any other: OAuth sign-in that fails before the server is usable, and docs that don't match the live server.

At the recheck, about 16:00 Europe/Sofia, 21 issues were open and 2 had been closed as completed earlier that day. 5 of the 23 are feature requests, and I list them separately near the end. Some of the open issues were opened in October.

I didn't file these issues and I didn't reproduce them, so everything below is what the issue itself says. I don't name the projects. Each section gives the failure class, then what to check on your own connector.

1. OAuth sign-in fails before the server is usable

Five open issues describe a client that can't finish sign-in, or that signs in and then gets an expired-session or invalid-client error.

  1. Dynamic client registration accepts a loopback redirect URI such as http://127.0.0.1:53682/, then the authorize endpoint answers invalid_redirect for that same URI. Repeating the flow with http://localhost:53682/ works, and registering with application_type: "native" doesn't change the result.
  2. A hosted server can't be connected from the Claude.ai connector because OAuth fails at dynamic client registration. The quoted error begins "Couldn't register with" and then names the vendor's sign-in service.
  3. A second server fails the same way when it's added as a remote connector in Claude Desktop with automatic registration. This issue was opened in October and was still open on 10 November.
  4. VS Code's MCP client registers through POST /register and persists the client_id it's issued. After the server evicts or expires that id, /authorize fails with "Invalid client_id".
  5. initialize succeeds, then every tools/call returns a session-expired message or a 401 for a dynamically registered client. The issue says a fresh authorization and a brand-new client registration still fail within two minutes of the token being issued, while the same account works at the same time through the Claude connector.

Check on your connector:

  1. Register a client dynamically, then send the redirect URI that registration accepted to the authorize endpoint. Do it once with 127.0.0.1 and once with localhost.
  2. Add the server as a connector in each client your users run, with automatic registration, and watch whether registration completes.
  3. Remove a registered client_id on the server, start sign-in again from the client that still holds it, and read the error the client gets.
  4. After initialize, call a tool with a token issued a few seconds earlier to a dynamically registered client.

2. Docs, skills or the listed schema don't match the live server

Five issues fall here. Two of them were closed as completed on 10 November, so I describe those two in the past tense.

Closed as completed:

  1. A documented Claude Desktop setup put a remote server in claude_desktop_config.json with only url and headers. The issue says that file only accepts local stdio servers, where each entry needs a command, so Claude Desktop rejected the entry and the server never loaded. The docs also said 6 or 7 tools depending on the page, while the server registers 8 core tools plus 6 more on API-key connections. The issue was closed 25 minutes after it was opened. A comment on it says the production docs were updated and verified live the same day: the Claude Desktop pages now give an mcp-remote command entry, and the API reference says 8 core tools.
  2. A config class had a fluent instructions() method, but filters was only a public property, so ->filters([]) threw an unknown-method error. The issue was closed as completed the same day.

Open on 10 November:

  1. A hosted tools/list marks a parameter as required on two tools. The issue says calls without it succeed, sending it doesn't change the output, and the main branch has no such parameter on either tool.
  2. A README's Claude Code install command uses npx -y @anthropic-ai/mcp-remote. The issue says that npm package doesn't exist and the registry returns 404.
  3. Two skills call MCP actions that the live tool reference doesn't list. The reporter checked the public tool reference on 9 November 2026.

Check on your connector:

  1. Run every documented install command, and paste every documented config block into the client it names, on a machine that has never had your server on it.
  2. Count the tools tools/list returns, then compare that number with every page that states one.
  3. Diff the hosted tools/list against the tool definitions on your main branch, required parameters included.
  4. For each skill you ship, look up every action it calls in the live tool list.

3. Tool annotations a directory checklist flags

One issue, opened in October and still open on 10 November, says none of a server's 39 registered tools passes a title. It states that Anthropic's Connectors Directory requires a title plus readOnlyHint or destructiveHint on every tool. It also says two tools that overwrite an existing object at the same key are marked destructiveHint: false.

Check on your connector:

  1. Confirm every tool has a title and carries readOnlyHint or destructiveHint.
  2. Call each write tool against a target that already exists. If the call replaces what was there, the tool modifies data and destructiveHint: false is the wrong annotation.

4. Install, runtime and argument coercion

Three open issues fall here.

  1. A fresh install exits on startup with ImportError: cannot import name 'eval_type_backport' from 'pydantic._internal._typing_extra'. The issue attributes it to a pin on mcp[cli]==1.6.0 with pydantic left unpinned, after pydantic 2.14.0 removed that private name.
  2. Number(null) and Number("") are both 0, so an optional max-age parameter sent as null becomes 0, and 0 forces a live crawl.
  3. A tool call ended with MCP call failed: TimeoutError: MCP call timed out after 300.0s (configured timeout: 300.0s) and no result. The issue records one attempt, so it says nothing about how often this happens or why.

Check on your connector:

  1. Install into an empty environment, with no lockfile and no cached image, and start the server.
  2. Send null and "" for every optional number, and compare the result with leaving the field out.
  3. Make the upstream API hang, then look at what the client receives and how long it waits.

5. The connection reports connected and the agent has zero tools

One open issue reports a regression after a version upgrade: tools/list returns 403 and the agent sees zero tools, while the connection is still reported as connected.

Check on your connector: after every upgrade, call tools/list with the credentials an agent uses and count the tools that come back. The connected status in that report didn't show the failure.

6. A cache keyed on the raw caller URL, with no size bound

One issue, opened in October and still open on 10 November, says a docs client keys its cache on the caller's raw URL, has no size bound and no eviction, and removes an expired entry only when the same key is read again. It adds that the live docs site returns 200 for query-variant URLs, so each variant is cacheable.

Check on your connector: for every cache in the server, write down the key, the size bound and the moment an expired entry is removed. If the key is caller input, count how many distinct keys one caller can create.

7. The documented remote URL doesn't accept the connection

One issue, opened in October and still open on 10 November, says adding the documented remote MCP URL as a Claude.ai custom connector fails at the first step with "Couldn't reach this address". After "Continue anyway" the connector saves, but it stays in a "needs reconnect" state with no tools exposed.

Check on your connector: add the URL from your docs as a custom connector in the client the docs name, and confirm the tools appear.

8. Link-formatted values that don't open

One open issue says link-formatted values in an MCP view don't open in Claude on the web, and that the view should use ui/open-link.

Check on your connector: click every link your views render, in the web client.

The five feature requests

Five of the 23 issues ask for something new, and I don't count them as failures:

  1. OAuth support in an MCP client toward MCP servers (RFC 9728 discovery and PKCE).
  2. Per-user SQL identity through JWT passthrough on a shared HTTP deployment.
  3. MCP management of public sharing.
  4. Create-environment and delete-variables tools on a hosted MCP server.
  5. Native Streamable HTTP and/or SSE transport, so a server can be hosted remotely instead of only as local stdio. This request was opened in October and was still open on 10 November.

MCP connector review

If you want an outside review before your connector goes to customers or the Claude directory, I do an MCP connector review: an independent review of your existing MCP connector against Anthropic's connector pre-submission checklist.

  1. Every tool goes through the MCP Inspector, and through Claude as a custom connector where hosting allows it.
  2. Every tool is tested with valid input, bad input, denied access and an upstream error.
  3. The permission boundary is checked with two users.
  4. You get a checklist report where each finding has severity, impact, reproduction steps and a proposed fix.
  5. You get one retest after you fix the findings.

I don't claim the review would have caught every class in this article. Anthropic doesn't run, approve or certify it, and it can't guarantee a Community or Verified listing.

The scope is on the MCP connector review page.

If the server isn't built yet, the MCP build is an MCP server over your existing API: four to six read-only tools, one sign-in flow and deployment to your infrastructure. Following the checklist doesn't mean Anthropic approves or certifies the connector.

Top comments (0)