Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Epure

NPM · @EPURE-SH/MCP · 2 COMPONENTS

Read Epure error tracking issues from Claude Code, Cursor or Codex: stack, release and count.

+3 this week 73 Trust /100

Last scanned (20 hours ago)

Scores higher than 46% of npm servers

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 8 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
  • 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 3803 tokens (~64/item across 59 items; 58 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 12 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@epure-sh/mcp@0.3.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 58 exposed · ~3,623 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
epure_rules_list ~43

list Epure rules. alert rules notifications triggers thresholds conditions cooldown.

NameTypeReqDescription
project_idstring–Epure project UUID; obtain it with epure_projects_list.

No output schema declared.

No examples provided.

epure_rules_update ~131

update Epure rules. alert rules notifications triggers thresholds conditions cooldown.

NameTypeReqDescription
channel_idsarray–channel ids
condition_matchstring–condition match
conditionsarray–conditions
cooldown_minsnumber–cooldown mins
enabledboolean–enabled
environmentstring–environment
filters_jsonobject–filters json
idstringyesResource identifier
namestring–name
payload_optionsobject–payload options
thresholdnumber–threshold
triggersarray–triggers

No output schema declared.

No examples provided.

epure_webhooks_create ~68

create Epure webhooks. outgoing webhook integrations delivery signing secret.

NameTypeReqDescription
eventsarray–events
formatstringyesformat
project_idstringyesEpure project UUID; obtain it with epure_projects_list.
urlstringyesurl

No output schema declared.

No examples provided.

epure_webhooks_delete ~57

delete Epure webhooks. outgoing webhook integrations delivery signing secret. Permanently removes or changes data; requires explicit confirmation.

NameTypeReqDescription
confirmbooleanyesExplicit approval of the destructive action
idstringyesResource identifier

No output schema declared.

No examples provided.

epure_webhooks_list ~44

list Epure webhooks. outgoing webhook integrations delivery signing secret.

NameTypeReqDescription
project_idstringyesEpure project UUID; obtain it with epure_projects_list.

No output schema declared.

No examples provided.

epure_webhooks_rotate_secret ~59

rotate secret Epure webhooks. outgoing webhook integrations delivery signing secret. Permanently removes or changes data; requires explicit confirmation.

NameTypeReqDescription
confirmbooleanyesExplicit approval of the destructive action
idstringyesResource identifier

No output schema declared.

No examples provided.

epure_webhooks_test ~33

test Epure webhooks. outgoing webhook integrations delivery signing secret.

NameTypeReqDescription
idstringyesResource identifier

No output schema declared.

No examples provided.

epure_webhooks_update ~41

update Epure webhooks. outgoing webhook integrations delivery signing secret.

NameTypeReqDescription
eventsarray–events
idstringyesResource identifier

No output schema declared.

No examples provided.

Install

How do I install the Epure MCP server?

Epure runs locally as an npm package, launched with npx -y @epure-sh/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @epure-sh/mcp

# add to Claude Code
claude mcp add epure-sh-epure -- npx -y @epure-sh/mcp
Common questions

What is the Epure MCP server?

Epure is an MCP server listed in the public MCP registry as io.github.epure-sh/epure. Read Epure error tracking issues from Claude Code, Cursor or Codex: stack, release and count. This page covers its npm package (@epure-sh/mcp).

Is the Epure MCP server safe to use?

Epure scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Epure MCP server expose?

Epure exposes 58 tools: epure_alerts_list, epure_alerts_update, epure_auth_whoami, epure_channels_create, epure_channels_delete, and 53 more. Their descriptions and schemas cost roughly 3,623 tokens of context every time the server is loaded.

Is the Epure MCP server still maintained?

Epure is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Epure MCP server under?

Epure declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Epure MCP server?

VerifyMCP ran 16 checks on Epure, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.