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_action ~51

Execute a discovered action with its validated arguments. Destructive operations require confirm=true. Discover the operation first.

NameTypeReqDescription
argumentsobjectyes–
confirmboolean––
operationstringyes–

No output schema declared.

No examples provided.

epure_alerts_list ~51

list Epure alerts. fired alerts incidents notification delivery acknowledgement.

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

No output schema declared.

No examples provided.

epure_alerts_update ~40

update Epure alerts. fired alerts incidents notification delivery acknowledgement.

NameTypeReqDescription
idstringyesResource identifier
statusstring–status

No output schema declared.

No examples provided.

epure_api ~69

Advanced OAuth REST request from the catalog. Prefer named tools. GET only in read-only mode; destructive writes require confirm=true.

NameTypeReqDescription
bodyobject––
confirmboolean––
methodstringyes–
pathstringyes–
queryobject––

No output schema declared.

No examples provided.

epure_api_catalog ~125

Search advanced product REST routes. Excludes browser auth and manual credential management. No sign-in required.

NameTypeReqDescription
include_schemaboolean–Include exact input schemas; default false for concise discovery.
limitinteger––
offsetinteger––
resourcestring–Resource group: issues, projects, rules, channels, monitors, alerts, releases, members, invitations, webhooks, privacy, connected-apps or auth.
searchstring–Natural-language task or keywords, such as email alerts, cron jobs, crashes or team invitations.

No output schema declared.

No examples provided.

epure_auth_whoami ~38

Identify the signed-in Epure account, workspace, role and OAuth scopes. Use to diagnose access or workspace selection before making changes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

epure_channels_create ~123

Create one Epure notification output channel for one or several projects. Supply project_ids for sharing, provider and destination config. Verification may be required before delivery; use channels.test next.

NameTypeReqDescription
configobject–config
labelstringyeslabel
project_idstring–Epure project UUID; obtain it with epure_projects_list.
project_idsarray–Project UUIDs sharing this single destination; all must belong to the authorized workspace.
providerstringyesprovider
require_verifyboolean–require verify

No output schema declared.

No examples provided.

epure_channels_delete ~59

delete Epure channels. output channels destinations email Slack Discord webhook verification multiple projects. 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_channels_list ~46

list Epure channels. output channels destinations email Slack Discord webhook verification multiple projects.

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

No output schema declared.

No examples provided.

epure_channels_ping ~35

ping Epure channels. output channels destinations email Slack Discord webhook verification multiple projects.

NameTypeReqDescription
idstringyesResource identifier

No output schema declared.

No examples provided.

epure_channels_test ~60

Send a real verification notification to an output channel destination. This has an external delivery side effect; enable_on_ok can enable the channel after success.

NameTypeReqDescription
enable_on_okboolean–enable on ok
idstringyesResource identifier

No output schema declared.

No examples provided.

epure_channels_update ~104

update Epure channels. output channels destinations email Slack Discord webhook verification multiple projects.

NameTypeReqDescription
configobject–config
idstringyesResource identifier
is_enabledboolean–is enabled
labelstring–label
project_idstring–Epure project UUID; obtain it with epure_projects_list.
project_idsarray–Project UUIDs sharing this single destination; all must belong to the authorized workspace.

No output schema declared.

No examples provided.

epure_connected_apps_delete ~57

delete Epure connected-apps. OAuth authorized applications revoke access. 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_connected_apps_list ~24

list Epure connected-apps. OAuth authorized applications revoke access.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

epure_discover ~156

Find Epure tools for errors and crashes, alert rules, notification channels, cron jobs, projects, releases, team and privacy. Search with task keywords; returns tool names and concise descriptions. Set include_schema=true for exact inputs. No sign-in required.

NameTypeReqDescription
include_schemaboolean–Include exact input schemas; default false for concise discovery.
limitinteger––
offsetinteger––
resourcestring–Resource group: issues, projects, rules, channels, monitors, alerts, releases, members, invitations, webhooks, privacy, connected-apps or auth.
searchstring–Natural-language task or keywords, such as email alerts, cron jobs, crashes or team invitations.

No output schema declared.

No examples provided.

epure_invitations_create ~38

create Epure invitations. invite teammates workspace access.

NameTypeReqDescription
emailstringyesemail
rolestringyesrole

No output schema declared.

No examples provided.

epure_invitations_delete ~55

delete Epure invitations. invite teammates workspace access. 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_invitations_list ~22

list Epure invitations. invite teammates workspace access.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

epure_issues_context ~91

Investigate an Epure error or crash by issue ID: stack trace, source context, breadcrumbs and suspect code. Raw payload and end-user data are excluded unless explicitly requested.

NameTypeReqDescription
eventstring–event
formatstring–format
idstringyesResource identifier
include_payloadboolean–include payload
include_userboolean–include user

No output schema declared.

No examples provided.

epure_issues_events ~37

events Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
issue_idstringyesResource identifier

No output schema declared.

No examples provided.

epure_issues_ignore ~48

ignore Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
idstringyesResource identifier
resolved_in_releasestring–resolved in release

No output schema declared.

No examples provided.

epure_issues_list ~107

Search Epure errors, exceptions, crashes and regressions; returns a priority-ranked issue queue. Filter by project_id, environment or q; default 20, maximum 100. Use issues.context for a selected issue.

NameTypeReqDescription
environmentstring–environment
limitinteger–limit
project_idstring–Epure project UUID; obtain it with epure_projects_list.
qstring–q
windowstring–window

No output schema declared.

No examples provided.

epure_issues_releases ~38

releases Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
issue_idstringyesResource identifier

No output schema declared.

No examples provided.

epure_issues_reopen ~49

reopen Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
idstringyesResource identifier
resolved_in_releasestring–resolved in release

No output schema declared.

No examples provided.

epure_issues_resolve ~49

resolve Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
idstringyesResource identifier
resolved_in_releasestring–resolved in release

No output schema declared.

No examples provided.

epure_issues_show ~36

show Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
idstringyesResource identifier

No output schema declared.

No examples provided.

epure_issues_snooze ~47

snooze Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
idstringyesResource identifier
modestringyesmode

No output schema declared.

No examples provided.

epure_issues_timeline ~38

timeline Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
issue_idstringyesResource identifier

No output schema declared.

No examples provided.

epure_issues_unsnooze ~40

unsnooze Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
idstringyesResource identifier

No output schema declared.

No examples provided.

epure_issues_update ~56

update Epure issues. errors exceptions crashes bugs stack traces triage regressions.

NameTypeReqDescription
idstringyesResource identifier
resolved_in_releasestring–resolved in release
statusstring–status

No output schema declared.

No examples provided.

epure_members_delete ~55

delete Epure members. workspace team membership roles access. Permanently removes or changes data; requires explicit confirmation.

NameTypeReqDescription
confirmbooleanyesExplicit approval of the destructive action
user_idstringyesResource identifier

No output schema declared.

No examples provided.

epure_members_list ~21

list Epure members. workspace team membership roles access.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

epure_members_update ~39

update Epure members. workspace team membership roles access.

NameTypeReqDescription
rolestringyesrole
user_idstringyesResource identifier

No output schema declared.

No examples provided.

epure_monitors_check_in ~70

Send a real cron monitor heartbeat: in_progress when a job starts, ok on success, error on failure. This changes monitor state and can trigger alerts.

NameTypeReqDescription
duration_msnumber–duration ms
idstringyesResource identifier
statusstring–status

No output schema declared.

No examples provided.

epure_monitors_create ~182

Monitor a real cron job or scheduled task in Epure. Create a heartbeat monitor with schedule, timezone, grace margin and runtime limits; send real check-ins from the job.

NameTypeReqDescription
checkin_margin_minsnumber–checkin margin mins
environmentstring–environment
failure_issue_thresholdnumber–failure issue threshold
max_runtime_minsnumber–max runtime mins
namestring–name
project_idstringyesEpure project UUID; obtain it with epure_projects_list.
schedulestring–Cron expression, for example 0 * * * * for every hour.
schedule_typestring–schedule type
slugstringyesslug
timezonestring–IANA timezone, for example Europe/Paris; use UTC when appropriate.

No output schema declared.

No examples provided.

epure_monitors_delete ~61

delete Epure monitors. cron jobs scheduled tasks heartbeat check-ins missed failed jobs timezone. 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_monitors_list ~48

list Epure monitors. cron jobs scheduled tasks heartbeat check-ins missed failed jobs timezone.

NameTypeReqDescription
project_idstringyesEpure project UUID; obtain it with epure_projects_list.

No output schema declared.

No examples provided.

epure_monitors_show ~37

show Epure monitors. cron jobs scheduled tasks heartbeat check-ins missed failed jobs timezone.

NameTypeReqDescription
idstringyesResource identifier

No output schema declared.

No examples provided.

epure_monitors_update ~153

update Epure monitors. cron jobs scheduled tasks heartbeat check-ins missed failed jobs timezone.

NameTypeReqDescription
checkin_margin_minsnumber–checkin margin mins
environmentstring–environment
failure_issue_thresholdnumber–failure issue threshold
idstringyesResource identifier
max_runtime_minsnumber–max runtime mins
namestring–name
pausedboolean–paused
schedulestring–Cron expression, for example 0 * * * * for every hour.
schedule_typestring–schedule type
timezonestring–IANA timezone, for example Europe/Paris; use UTC when appropriate.

No output schema declared.

No examples provided.

epure_privacy_erase ~84

erase Epure privacy. end-user personal data export erase anonymize. Permanently removes or changes data; requires explicit confirmation.

NameTypeReqDescription
confirmbooleanyesExplicit approval of the destructive action
emailstring–email
idstringyesResource identifier
user_idstring–Existing resource UUID returned by the corresponding list tool.

No output schema declared.

No examples provided.

epure_privacy_export ~59

export Epure privacy. end-user personal data export erase anonymize.

NameTypeReqDescription
emailstring–email
idstringyesResource identifier
user_idstring–Existing resource UUID returned by the corresponding list tool.

No output schema declared.

No examples provided.

epure_privacy_show ~25

show Epure privacy. end-user personal data export erase anonymize.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

epure_privacy_strip_identifiers ~61

strip identifiers Epure privacy. end-user personal data export erase anonymize. 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_projects_create ~30

create Epure projects. applications services SDK ingestion project configuration.

NameTypeReqDescription
namestringyesname

No output schema declared.

No examples provided.

epure_projects_delete ~55

delete Epure projects. applications services SDK ingestion project configuration. 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_projects_list ~29

Find Epure projects and their IDs before searching errors or configuring monitoring for an application or service.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

epure_projects_update ~78

update Epure projects. applications services SDK ingestion project configuration.

NameTypeReqDescription
idstringyesResource identifier
ingest_cap_per_hournumber–ingest cap per hour
namestring–name
retention_daysinteger–retention days
store_end_user_identifiersboolean–store end user identifiers

No output schema declared.

No examples provided.

epure_releases_list ~41

list Epure releases. deployments versions release health.

NameTypeReqDescription
project_idstringyesEpure project UUID; obtain it with epure_projects_list.

No output schema declared.

No examples provided.

epure_rules_create ~174

Create an Epure alert rule for new errors, regressions or velocity spikes. Requires project_id, name and kind; channel_ids selects delivery destinations. Create or find a channel first.

NameTypeReqDescription
channel_idsarray–channel ids
condition_matchstring–condition match
conditionsarray–conditions
cooldown_minsnumber–cooldown mins
enabledboolean–enabled
environmentstring–environment
filters_jsonobject–filters json
kindstringyeskind
namestringyesname
payload_optionsobject–payload options
project_idstringyesEpure project UUID; obtain it with epure_projects_list.
thresholdnumber–threshold
triggersarray–triggers

No output schema declared.

No examples provided.

epure_rules_delete ~56

delete Epure rules. alert rules notifications triggers thresholds conditions cooldown. Permanently removes or changes data; requires explicit confirmation.

NameTypeReqDescription
confirmbooleanyesExplicit approval of the destructive action
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.