io.github.epure-sh/epure
Epure
Is the Epure MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.
Read Epure error tracking issues from Claude Code, Cursor or Codex: stack, release and count.
needs auth probed 2026-11-14 · HTTP 401 · Bearer
The server needs auth, so these tool definitions were read from the publisher's open-source package npm:@epure-sh/mcp, started in a container with placeholder values and the network off, on 2026-11-14. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token"}- Endpoint
- https://app.epure.sh/mcp (streamable-http)
- Host
- app.epure.sh
- Of a 1M window
- 1.1 % of a 1M context window
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.epure.sh/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server app.epure.sh, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes read:agent write:triage write:admin.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/epure-sh/epure
- Website
- https://epure.sh/docs/guides/mcp-and-cli
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention epure or tracking or release.
- Depureco Industrial Vacuum Explorer io.github.depurecoindustrialvacuums-boop/industrial-vacuum-explorer · alive
- AI-Portal Enterprise GenAI Briefing ai.ai-portal/ai-portal · alive
- Daystruct ai.daystruct.api/daystruct · alive
- Divinci AI ai.divinci/divinci · needs auth
- DoneThat ai.donethat/donethat · needs auth
- Helixar Security ai.helixar/mcp · needs auth
- Jason Lovell ai.jasonlovell/site · alive
- ai.klipy/klipy · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.