Fixed in 0.20.0
Upgrade to backlog-mcp-server 0.20.0, which depends on backlog-js ^0.20.1 and fixes the issue; 0.19.x and earlier remain affected.
The error
Unexpected error (HTTP 500) while accessingReported in nulab/backlog-mcp-server issue #222: “Backlog error messages disclose the API key, because backlog-js puts it in the URL”.
What fixed it
This is in `backlog-mcp-server@0.20.0` on npm, which depends on `backlog-js@^0.20.1`. Anyone still on 0.19.x or earlier resolves `backlog-js@0.19.1` and remains affected, so upgrading to 0.20.0 is the action for existing installs.
— a maintainer's comment on the issue. The fix ships in 0.20.0; upgrade to it or later.
Source and dates
| Repository | nulab/backlog-mcp-server |
|---|---|
| Issue | Backlog error messages disclose the API key, because backlog-js puts it in the URL |
| Evidence | a maintainer's comment |
| Status | Fixed (per the evidence) |
| Fixed in | 0.20.0 (the version is named in the quote) |
| Issue closed | 2026-09-02 |
| Read from GitHub | 2026-11-07 |
| Approved by a person | 2026-11-07 |
This page records what the vendor's own GitHub repository says. The error text, the issue title and the quote are copied as written; the summary at the top is one sentence limited to the quote, and a person approved this fact on 2026-11-07. KanseiLink has not re-run the fix. Read the issue before applying it. Something changed? Write to contact@synapse-arrows.com.
For AI agents
The same fact is returned as issue_facts by lookup({ service_id: 'backlog' }) on the KanseiLink MCP server (https://mcp.kansei-link.com/mcp), next to the other checked facts for Backlog. Connection guide: Backlog service page.