# io.github.CloudCorpRecords/errorwatch (oci · ghcr.io/cloudcorprecords/errorwatch)

Organizations, projects, releases, and issues through the Sentry API.

- Trust score: 41/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/errorwatch`: 64/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-errorwatch/reneturcios-errorwatch.md), [page](https://verifymcp.io/servers/cloudcorprecords-errorwatch/reneturcios-errorwatch)
- oci · `ghcr.io/cloudcorprecords/errorwatch`: 41/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-errorwatch/ghcr-io-cloudcorprecords-errorwatch.md), [page](https://verifymcp.io/servers/cloudcorprecords-errorwatch/ghcr-io-cloudcorprecords-errorwatch)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/errorwatch`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 562 tokens (~51/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the io.github.CloudCorpRecords/errorwatch MCP server?

io.github.CloudCorpRecords/errorwatch runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/errorwatch:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-errorwatch -- docker run --rm -i ghcr.io/cloudcorprecords/errorwatch:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-errorwatch": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/errorwatch:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-errorwatch": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/errorwatch:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-errorwatch -- docker run --rm -i ghcr.io/cloudcorprecords/errorwatch:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-errorwatch": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/errorwatch:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-errorwatch:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/errorwatch:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-errorwatch": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/errorwatch:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-errorwatch": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/errorwatch:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 41, +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.

### 2026-11-02 (score 40)

First indexed and scored.

## MCP tools (11)

### `whoami` (~16 tokens)

Get the authenticated user or token identity.

### `list_organizations` (~16 tokens)

List organizations the token can access.

### `list_projects` (~29 tokens)

List projects in an organization.

Input parameters:

- `organization_slug` (string, required): Slug of the Sentry organization.

### `get_project` (~48 tokens)

Get one project in an organization.

Input parameters:

- `organization_slug` (string, required): Slug of the Sentry organization.
- `project_slug` (string, required): Slug of the Sentry project within the organization.

### `list_releases` (~48 tokens)

List releases for a project.

Input parameters:

- `organization_slug` (string, required): Slug of the Sentry organization.
- `project_slug` (string, required): Slug of the Sentry project within the organization.

### `search_issues` (~100 tokens)

Search issues in an organization, optionally within one project.

Input parameters:

- `limit` (integer): Maximum number of issues to return.
- `organization_slug` (string, required): 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.

### `get_issue` (~29 tokens)

Get one issue by its id.

Input parameters:

- `issue_id` (string, required): ID of the Sentry issue.

### `get_issue_event` (~60 tokens)

Get an event for an issue, by event id or latest.

Input parameters:

- `event_id` (string): ID of the event to retrieve for the issue; omit to get the latest event.
- `issue_id` (string, required): ID of the Sentry issue.

### `update_issue` (~143 tokens)

Update an issue: status, resolution, assignment, and flags.

Input parameters:

- `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, required): 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".

### `list_issue_comments` (~29 tokens)

List comments on an issue.

Input parameters:

- `issue_id` (string, required): ID of the Sentry issue.

### `create_issue_comment` (~44 tokens)

Add a comment to an issue.

Input parameters:

- `issue_id` (string, required): ID of the Sentry issue.
- `text` (string, required): Text content of the comment to add.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-errorwatch/ghcr-io-cloudcorprecords-errorwatch#diagnostics

## Score history

- 2026-11-05: 41
- 2026-11-04: 41
- 2026-11-03: 40
- 2026-11-02: 40

## Common questions

### 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 container image (ghcr.io/cloudcorprecords/errorwatch).

### Is the io.github.CloudCorpRecords/errorwatch MCP server safe to use?

io.github.CloudCorpRecords/errorwatch scores 41 out of 100 on VerifyMCP. 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.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/errorwatch
- Repository: https://github.com/CloudCorpRecords/errorwatch
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-errorwatch/ghcr-io-cloudcorprecords-errorwatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-errorwatch/ghcr-io-cloudcorprecords-errorwatch.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-errorwatch/ghcr-io-cloudcorprecords-errorwatch