com.mcparmory/sentry
OCI · GHCR.IO/MCPARMORY/SENTRY:1.0.2 · 2 COMPONENTS
Track errors, manage performance alerts, and configure dashboards and monitors
Available components
Last scanned (10 hours ago)
Scores higher than 81% of OCI 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 Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 176 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 33368 tokens (~166/item across 200 items; 200 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety99
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 31 of 32 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "create_deploy_for_release" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 200 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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
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 →
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.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 +5
- Source repository: unverified → pass ▲ security
- 23 Oct 26 −4
- Provenance: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 87. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 oci/ghcr.io/mcparmory/sentry:1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
update_team Update Team ~106
Update team attributes and configurable settings such as the team slug and other team-level properties.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| slug | string | yes | A unique identifier for the team using lowercase letters, numbers, hyphens, and underscores (cannot be purely numeric). Maximum 50 characters. |
| team_id_or_slug | string | yes | The team identifier, either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
upload_dsym_file Upload dSYM File ~174
Upload a debug information file (dSYM) for a specific release. The file must be a zip archive containing Apple .dSYM folders with debug images; uploading creates separate files for each contained image. Use region-specific domains (e.g., us.sentry.io or de.sentry.io) for this request.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Base64-encoded file content for upload. The dSYM file to upload as binary data. Must be a zip archive containing Apple .dSYM folders with debug images. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug. Used to scope the project within your organization. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL slug. Specifies which project receives the debug information file. |
No output schema declared.
No examples provided.
upload_release_file Upload Release File ~221
Upload a new file to a release. Files must be submitted using multipart/form-data encoding and requests should target region-specific domains (e.g., us.sentry.io or de.sentry.io).
| Name | Type | Req | Description |
|---|---|---|---|
| dist | string | – | The distribution name to associate with this file, useful for organizing files across different build variants or platforms. |
| file | string | yes | Base64-encoded file content for upload. The file content to upload, provided as binary multipart form data. |
| header | string | – | HTTP headers to attach to the file, specified as key:value pairs. This parameter can be supplied multiple times to add multiple headers (e.g., to define content type or caching directives). |
| name | string | – | The absolute path or URI where this file will be referenced (e.g., a full web URI for JavaScript files). If omitted, the original filename is used. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug. |
| version | string | yes | The release version identifier to associate this file with. |
No output schema declared.
No examples provided.
upload_release_file_project Upload Release File ~224
Upload a new file artifact for a specific release version. Files must be submitted using multipart/form-data encoding and requests should target region-specific domains (e.g., us.sentry.io or de.sentry.io).
| Name | Type | Req | Description |
|---|---|---|---|
| dist | string | – | Optional distribution name to associate with this file artifact. |
| file | string | yes | Base64-encoded file content for upload. The file content to upload as binary data via multipart form encoding. |
| header | string | – | Optional HTTP headers to attach to the file, specified as key:value pairs. This parameter can be supplied multiple times for multiple headers (e.g., to define content type). |
| name | string | – | Optional absolute path or URI where this file will be referenced (e.g., full web URI for JavaScript files). |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL slug. |
| version | string | yes | The release version identifier to associate this file with. |
No output schema declared.
No examples provided.
How do I install the com.mcparmory/sentry MCP server?
com.mcparmory/sentry runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/sentry:1.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/sentry:1.0.2
claude mcp add com-mcparmory-sentry -- docker run --rm -i ghcr.io/mcparmory/sentry:1.0.2
What is the com.mcparmory/sentry MCP server?
com.mcparmory/sentry is an MCP server listed in the public MCP registry as com.mcparmory/sentry. Track errors, manage performance alerts, and configure dashboards and monitors. This page covers its container image (ghcr.io/mcparmory/sentry:1.0.2).
Is the com.mcparmory/sentry MCP server safe to use?
com.mcparmory/sentry scores 51 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 com.mcparmory/sentry MCP server expose?
com.mcparmory/sentry exposes 200 tools: list_organizations, get_organization, update_organization, update_metric_alert_rule, list_integration_providers, and 195 more. Their descriptions and schemas cost roughly 33,368 tokens of context every time the server is loaded.
Is the com.mcparmory/sentry MCP server still maintained?
com.mcparmory/sentry 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 did VerifyMCP test on the com.mcparmory/sentry MCP server?
VerifyMCP ran 12 checks on com.mcparmory/sentry, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about com.mcparmory/sentry: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.