io.github.CloudCorpRecords/errorwatch
NPM · @RENETURCIOS/ERRORWATCH · 2 COMPONENTS
Organizations, projects, releases, and issues through the Sentry API.
Available components
Last scanned (18 minutes ago)
Scores higher than 32% of npm servers
Category Monitoring and Observability
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 562 tokens (~51/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 49
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@reneturcios/errorwatch@0.1.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_issue_comment ~44
Add a comment to an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | ID of the Sentry issue. |
| text | string | yes | Text content of the comment to add. |
No output schema declared.
No examples provided.
get_issue ~29
Get one issue by its id.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | ID of the Sentry issue. |
No output schema declared.
No examples provided.
get_issue_event ~60
Get an event for an issue, by event id or latest.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | – | ID of the event to retrieve for the issue; omit to get the latest event. |
| issue_id | string | yes | ID of the Sentry issue. |
No output schema declared.
No examples provided.
get_project ~48
Get one project in an organization.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_slug | string | yes | Slug of the Sentry organization. |
| project_slug | string | yes | Slug of the Sentry project within the organization. |
No output schema declared.
No examples provided.
list_issue_comments ~29
List comments on an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | ID of the Sentry issue. |
No output schema declared.
No examples provided.
list_organizations ~16
List organizations the token can access.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects ~29
List projects in an organization.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_slug | string | yes | Slug of the Sentry organization. |
No output schema declared.
No examples provided.
list_releases ~48
List releases for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_slug | string | yes | Slug of the Sentry organization. |
| project_slug | string | yes | Slug of the Sentry project within the organization. |
No output schema declared.
No examples provided.
search_issues ~100
Search issues in an organization, optionally within one project.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of issues to return. |
| organization_slug | string | yes | Slug of the Sentry organization. |
| project_slug | string | – | Slug of the Sentry project within the organization; omit to search across the whole organization. |
| query | string | – | Sentry issue search query string, passed through unchanged; omit to list issues without a search filter. |
No output schema declared.
No examples provided.
update_issue ~143
Update an issue: status, resolution, assignment, and flags.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | string | – | User or team to assign the issue to. |
| has_seen | boolean | – | Whether the issue is marked as seen. |
| is_bookmarked | boolean | – | Whether the issue is bookmarked. |
| is_subscribed | boolean | – | Whether the caller is subscribed to the issue. |
| issue_id | string | yes | ID of the Sentry issue. |
| resolved_in_next_release | boolean | – | Whether to mark the issue as resolved in the next release. |
| status | string | – | New status for the issue, such as "resolved", "unresolved", or "ignored". |
No output schema declared.
No examples provided.
whoami ~16
Get the authenticated user or token identity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/errorwatch MCP server?
io.github.CloudCorpRecords/errorwatch runs locally as an npm package, launched with npx -y @reneturcios/errorwatch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/errorwatch
claude mcp add cloudcorprecords-errorwatch -- npx -y @reneturcios/errorwatch
What is the io.github.CloudCorpRecords/errorwatch MCP server?
io.github.CloudCorpRecords/errorwatch is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/errorwatch. Organizations, projects, releases, and issues through the Sentry API. This page covers its npm package (@reneturcios/errorwatch).
Is the io.github.CloudCorpRecords/errorwatch MCP server safe to use?
io.github.CloudCorpRecords/errorwatch scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 io.github.CloudCorpRecords/errorwatch MCP server expose?
io.github.CloudCorpRecords/errorwatch exposes 11 tools: whoami, list_organizations, list_projects, get_project, list_releases, and 6 more. Their descriptions and schemas cost roughly 562 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/errorwatch MCP server still maintained?
io.github.CloudCorpRecords/errorwatch is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.CloudCorpRecords/errorwatch MCP server under?
io.github.CloudCorpRecords/errorwatch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.