com.mcparmory/sentry
OCI · GHCR.IO/MCPARMORY/SENTRY:1.0.2 · 2 COMPONENTS · SCANNED SEP 20
Track errors, manage performance alerts, and configure dashboards and monitors
Available components
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
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.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 130 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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.
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
{
"mcpServers": {
"com-mcparmory-sentry": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
]
}
}
} {
"servers": {
"com-mcparmory-sentry": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
]
}
}
} codex mcp add com-mcparmory-sentry -- docker run --rm -i ghcr.io/mcparmory/sentry:1.0.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-sentry": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-sentry:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/sentry:1.0.2"] {
"McpServers": {
"com-mcparmory-sentry": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
]
}
}
} {
"mcpServers": {
"com-mcparmory-sentry": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/sentry:1.0.2"
]
}
}
} 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 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.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 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.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 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.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 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 20 Sept 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 →
enable_spike_protection_for_projects Enable Spike Protection for Projects ~119
Enables Spike Protection feature for specified projects within an organization. Spike Protection helps manage error rate spikes by automatically adjusting error sampling thresholds.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. This determines which organization's projects will have Spike Protection enabled. |
| projects | array | yes | Array of project slugs to enable Spike Protection for. Use the special value `$all` to enable Spike Protection across all projects in the organization, or provide specific project slugs as an array o… |
No output schema declared.
No examples provided.
get_alert Get Alert ~87
Retrieve a specific alert (workflow) by its ID. This endpoint is part of the New Monitors and Alerts system and is currently in beta.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. This determines which organization's alert you're accessing. |
| workflow_id | integer | yes | The numeric ID of the alert (workflow) to retrieve. |
No output schema declared.
No examples provided.
get_artifact_install_details Get Artifact Install Details ~90
Retrieve installation and distribution details for a preprod artifact, including installability status, install URL, download metrics, and iOS code signing information.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id | string | yes | The unique identifier of the build artifact for which to retrieve installation details. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
No output schema declared.
No examples provided.
get_artifact_size_analysis Get Artifact Size Analysis ~113
Retrieve size analysis results for a build artifact, including download and install size metrics. Optionally compare against a base artifact to see size differences.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id | string | yes | The unique identifier of the build artifact to analyze. |
| baseArtifactId | string | – | Optional artifact ID to use as a baseline for size comparison. If omitted, the system uses the default base artifact from commit comparison. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
get_client_key Get Client Key ~107
Retrieve a specific client key associated with a project. Returns the key details including its configuration and status.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The unique identifier of the client key to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL-friendly slug of the project within the organization. |
No output schema declared.
No examples provided.
get_custom_integration Get Custom Integration ~86
Retrieve details about a custom integration (Sentry App) by its unique identifier or slug. Use this to fetch configuration, permissions, and metadata for a specific custom integration.
| Name | Type | Req | Description |
|---|---|---|---|
| sentry_app_id_or_slug | string | yes | The unique identifier or URL-friendly slug of the custom integration. You can use either the numeric ID or the slug string to identify which custom integration to retrieve. |
No output schema declared.
No examples provided.
get_discover_saved_query Get Discover Saved Query ~82
Retrieve a saved Discover query by its ID within a specific organization. This returns the full configuration and metadata of the saved query.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL slug of the organization. |
| query_id | integer | yes | The numeric ID of the saved Discover query to retrieve. |
No output schema declared.
No examples provided.
get_event Get Event ~115
Retrieve detailed information about a specific event within a project, including error data, breadcrumbs, and other event metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The unique hexadecimal identifier of the event to retrieve, as reported by the client SDK. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL-friendly slug of the project within the organization. |
No output schema declared.
No examples provided.
get_event_counts_for_organization Get Event Counts for Organization ~609
Retrieve aggregated event counts for an organization over a specified time period. Query by event type, outcome, and other dimensions using flexible grouping and filtering options.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter results to a specific data category. Each category represents a distinct data type: errors, transactions, file attachments, session replays, performance profiles, profile duration metrics, or… |
| end | string | – | This defines the inclusive end of the time series range as an explicit datetime, either in UTC ISO8601 or epoch seconds.Use along with `start` instead of `statsPeriod`. |
| field | string | yes | The metric to aggregate: `sum(quantity)` counts events (or bytes for attachments), while `sum(times_seen)` counts unique occurrences (sessions for replay data, or attachment count for attachments). |
| groupBy | array | yes | One or more dimensions to group results by (e.g., project, outcome, category). Multiple groupBy parameters can be passed to create multi-dimensional breakdowns. Note: grouping by project may omit row… |
| interval | string | – | This is the resolution of the time series, given in the same format as `statsPeriod`. The default resolution is `1h` and the minimum resolution is currently restricted to `1h` as well. Intervals larg… |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| outcome | string | – | Filter results by event outcome status, indicating whether an event was accepted, rate-limited, filtered, invalid, abused, discarded by client, or subject to cardinality limits. See Sentry documentat… |
| project | array | – | The ID of the projects to filter by. Use `-1` to include all accessible projects. |
| reason | string | – | Filter results by the specific reason an event was filtered or dropped. Provide the reason string to narrow results to events rejected for a particular cause. |
| start | string | – | This defines the start of the time series range as an explicit datetime, either in UTC ISO8601 or epoch seconds.Use along with `end` instead of `statsPeriod`. |
| statsPeriod | string | – | This defines the range of the time series, relative to now. The range is given in a `<number><unit>` format. For example `1d` for a one day range. Possible units are `m` for minutes, `h` for hours, `… |
No output schema declared.
No examples provided.
get_event_counts_for_project Get Event Counts for Project ~249
Retrieve event statistics for a project over a specified time range. Returns normalized timestamps with event counts aggregated at the requested resolution. Query ranges are limited by Sentry's configured time-series resolutions.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| resolution | string | – | The time bucket size for aggregating results: 10 seconds for fine-grained data, 1 hour for daily trends, or 1 day for long-term analysis. If omitted, Sentry selects an appropriate resolution based on… |
| since | string | – | The start of the query time range as an ISO 8601 formatted timestamp. If omitted, defaults to a recent time window. |
| stat | string | – | The type of event statistic to retrieve: received (accepted events), rejected (rate-limited events), blacklisted (filtered events), or generated (server-generated events). |
| until | string | – | The end of the query time range as an ISO 8601 formatted timestamp. If omitted, defaults to the current time. |
No output schema declared.
No examples provided.
get_events_timeseries Get Events Timeseries ~289
Retrieves event data for an organization as a timeseries, supporting single or multiple axes with optional grouping by top events. Results can be filtered by environment, time range, and custom query syntax.
| Name | Type | Req | Description |
|---|---|---|---|
| comparisonDelta | integer | – | Return an additional offset timeseries shifted by this many seconds for comparison purposes. |
| dataset | string | yes | The dataset to query. Different datasets provide different available fields: logs, profile_functions, spans, or uptime_results. |
| environment | array | – | Filter results to specific environments by name. Accepts multiple environment names as an array. |
| groupBy | array | – | Fields to group results by, determining which events are considered 'top' when used with topEvents. Required when topEvents is specified. Accepts multiple field names as an array. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or URL slug. |
| query | string | – | Filter results using Sentry query syntax. Supports boolean operators (AND, OR) and field matching with ranges or multiple values. |
| topEvents | integer | – | Return the top N events by the sort criteria. Must be between 1 and 10. When specified, both groupBy and sort parameters become required. |
| yAxis | string | – | The aggregate function to compute for the timeseries (e.g., count(), sum(), avg()). Defaults to count() if not provided. |
No output schema declared.
No examples provided.
get_issue Get Issue ~91
Retrieve detailed information about a specific issue, including its core metadata (title, first/last seen timestamps), engagement metrics (comments, user reports), and summarized event data.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | The unique identifier of the issue to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization that owns the issue. |
No output schema declared.
No examples provided.
get_issue_alert_rule Get Issue Alert Rule ~124
Retrieve details for a specific issue alert rule in a project. Issue alert rules define triggers, filters, and actions that determine when alerts are sent for matching issues. Note: This endpoint is deprecated; use the Fetch an Alert endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL slug of the project. |
| rule_id | integer | yes | The numeric ID of the alert rule to retrieve. |
No output schema declared.
No examples provided.
get_issue_autofix_state Get Issue Autofix State ~117
Retrieve the current state and progress of an automated fix process for a specific issue, including status, completed steps, root cause analysis, proposed solution, and generated code changes. Note: This endpoint is experimental and the response structure may change.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | integer | yes | The numeric identifier of the issue. Required to retrieve the specific autofix state for that issue. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug. Required to scope the issue within the correct organization. |
No output schema declared.
No examples provided.
get_issue_event Get Issue Event ~205
Retrieves detailed information about a specific event associated with an issue, such as comments, status changes, or assignments. You can fetch a particular event by ID or retrieve special event references like the latest, oldest, or recommended event.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | Optional filter to limit results to events from specific environments. Provide as a list of environment names; events matching any of the specified environments will be included. |
| event_id | string | yes | The event identifier to retrieve. Accepts a specific event ID or one of three special values: 'latest' for the most recent event, 'oldest' for the first event, or 'recommended' for a system-suggested… |
| issue_id | integer | yes | The numeric ID of the issue containing the event you want to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug (e.g., 'my-org'). This determines which organization's resources are accessed. |
No output schema declared.
No examples provided.
get_latest_installable_build Get Latest Installable Build ~240
Retrieve the latest installable build for a project matching the specified criteria. Optionally check for available updates by providing the current build version.
| Name | Type | Req | Description |
|---|---|---|---|
| appId | string | yes | The application identifier to match exactly against available builds. |
| buildConfiguration | string | – | Filter results to a specific build configuration by exact name match (e.g., 'debug', 'release'). |
| buildVersion | string | – | The current build version installed on the device. When provided, the response includes the current build details and indicates whether an update is available. |
| codesigningType | string | – | Filter results by code signing type to match your app's signing configuration. |
| installGroups | array | – | Filter results to one or more install groups by name. Specify multiple times to include builds from multiple groups. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| platform | string | yes | The target platform for the build: either 'apple' for iOS or 'android' for Android. |
| project_id_or_slug | string | yes | The project identifier, either as a numeric ID or URL-friendly slug. |
No output schema declared.
No examples provided.
get_monitor Get Monitor ~109
Retrieves detailed information about a specific monitor, including its configuration, status, and settings.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | Optional list of environment names to filter the monitor data by. Specify multiple environments as separate array items. |
| monitor_id_or_slug | string | yes | The monitor identifier, which can be either the numeric ID or the URL-friendly slug of the monitor. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
No output schema declared.
No examples provided.
get_monitor_detector Get Monitor Detector ~82
Retrieve detailed information about a specific monitor (detector). This endpoint is part of the New Monitors and Alerts system and is currently in beta.
| Name | Type | Req | Description |
|---|---|---|---|
| detector_id | integer | yes | The numeric ID of the monitor to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL slug of the organization. |
No output schema declared.
No examples provided.
get_monitor_project Get Monitor ~124
Retrieves detailed information about a specific monitor within a project, including its configuration, status, and alert rules.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id_or_slug | string | yes | The monitor identifier, which can be either the numeric ID or the URL-friendly slug uniquely identifying the monitor within the project. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL-friendly slug of the project within the organization. |
No output schema declared.
No examples provided.
get_organization Get Organization ~88
Retrieve detailed information about a specific organization, including membership access levels and associated teams.
| Name | Type | Req | Description |
|---|---|---|---|
| detailed | string | – | Set to `"0"` to retrieve only basic organization details while excluding projects and teams from the response. Omit to include full details. |
| organization_id_or_slug | string | yes | The unique identifier or slug of the organization. Use either the numeric ID or the URL-friendly slug name. |
No output schema declared.
No examples provided.
get_organization_dashboard Get Organization Dashboard ~73
Retrieve detailed information about a specific custom dashboard within an organization, including its configuration and contents.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard_id | integer | yes | The numeric ID of the dashboard to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
No output schema declared.
No examples provided.
get_organization_events_count_by_project Get Organization Events Count by Project ~275
Retrieve summarized event counts aggregated by project for an organization. Use this to analyze event volume, filtering by category (errors, transactions, attachments, replays, profiles), outcome status, and other dimensions.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter results by event category. Note: attachments cannot be combined with other categories as quantity values differ (bytes vs. event counts). Filtering by `error` automatically includes `default`… |
| download | boolean | – | If true, download the response as a CSV file instead of JSON. |
| field | string | yes | The aggregation metric to retrieve: `sum(quantity)` returns event counts (or total bytes for attachments), while `sum(times_seen)` returns the number of times events were observed (or unique session… |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| outcome | string | – | Filter results by event outcome status, indicating whether events were accepted, filtered, rate-limited, invalid, abused, client-discarded, or cardinality-limited. See Sentry's stats documentation fo… |
| reason | string | – | Filter results by the specific reason an event was filtered or dropped. Provide the reason as a string value. |
No output schema declared.
No examples provided.
get_organization_integration Get Organization Integration ~72
Retrieve a specific integration installed on an organization. Both the integration and its organization-specific configuration must exist.
| Name | Type | Req | Description |
|---|---|---|---|
| integration_id | string | yes | The unique identifier of the integration installed on the organization. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
No output schema declared.
No examples provided.
get_organization_member Get Organization Member ~79
Retrieve details for a specific organization member, including pending invite status if the member has been approved by owners or managers but hasn't yet accepted the invitation.
| Name | Type | Req | Description |
|---|---|---|---|
| member_id | string | yes | The unique identifier of the organization member to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
get_organization_release Get Organization Release ~274
Retrieve detailed information about a specific release within an organization, including optional health metrics, adoption stages, and summary statistics.
| Name | Type | Req | Description |
|---|---|---|---|
| adoptionStages | boolean | – | Include adoption stage information showing how the release is being adopted across your user base. Disabled by default. |
| health | boolean | – | Include health metrics and crash data with the release details. Disabled by default. |
| healthStatsPeriod | string | – | Time period for aggregating health statistics when health data is enabled. Defaults to 24 hours if health is enabled. Valid periods range from 1 hour to 90 days. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
| project_id | string | – | Filter release data to a specific project within the organization. |
| query | string | – | Apply advanced filters using query syntax to narrow results by transaction, release, and other attributes. Supports boolean operators (AND, OR) and comma-separated value lists. |
| status | string | – | Filter results by release status: archived releases or actively open releases. |
| summaryStatsPeriod | string | – | Time period for aggregating summary statistics. Defaults to 14 days. Valid periods range from 1 hour to 90 days. |
| version | string | yes | The version identifier that uniquely identifies the release within the organization. |
No output schema declared.
No examples provided.
get_project Get Project ~86
Retrieve detailed information about a specific project, including its configuration, settings, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL-friendly slug of the project within the organization. |
No output schema declared.
No examples provided.
get_project_environment Get Project Environment ~111
Retrieve detailed information about a specific environment within a project, including its configuration and settings.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | yes | The name of the environment to retrieve (e.g., 'production', 'staging', 'development'). |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL-friendly slug of the project. |
No output schema declared.
No examples provided.
get_project_ownership_configuration Get Project Ownership Configuration ~87
Retrieve the ownership configuration for a project, including details about code ownership rules and assignments.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL slug of the project within the organization. |
No output schema declared.
No examples provided.
get_recording_segment Get Recording Segment ~162
Retrieve a specific recording segment from a replay session. Recording segments contain the captured user interaction data for a portion of the replay.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. This determines which organization's resources are accessed. |
| project_id_or_slug | string | yes | The project identifier, either as a numeric ID or URL-friendly slug. This determines which project within the organization contains the replay. |
| replay_id | string | yes | The unique identifier of the replay session, formatted as a UUID. This identifies which replay the segment belongs to. |
| segment_id | integer | yes | The numeric identifier of the recording segment within the replay. Segments are indexed sequentially and represent discrete portions of the replay recording. |
No output schema declared.
No examples provided.
get_release_file Get Release File ~136
Retrieve a specific file from a release, either as file metadata or raw file contents. Use the download parameter to control whether you receive JSON metadata or the actual file data.
| Name | Type | Req | Description |
|---|---|---|---|
| download | boolean | – | Set to true to retrieve the raw file contents as a binary payload, or false (default) to receive file metadata as JSON. |
| file_id | string | yes | The unique identifier of the file within the release. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug name. |
| version | string | yes | The release version identifier, typically a semantic version string or tag name. |
No output schema declared.
No examples provided.
get_release_file_project Get Release File ~156
Retrieve a file associated with a specific release, either as file metadata or raw file contents depending on the download parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| download | boolean | – | When true, returns the raw file contents as the response payload; when false or omitted, returns file metadata as JSON. |
| file_id | string | yes | The unique identifier of the file within the release. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL slug of the project within the organization. |
| version | string | yes | The version string that identifies the release (e.g., semantic version or commit hash). |
No output schema declared.
No examples provided.
get_replay_count_for_issues_or_transactions Get Replay Count for Issues or Transactions ~154
Retrieve the count of replays associated with specified issues, transactions, or replay IDs within an organization. Use the query parameter to filter by issue ID, transaction name, or replay ID.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | Optional list of environment names to narrow results to specific deployment environments. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| query | string | – | Required search query using Sentry query syntax to specify which replays to count. Must include exactly one of: issue.id (for issues), transaction (for transactions), or replay_id (for specific repla… |
No output schema declared.
No examples provided.
get_replay_deletion_job Get Replay Deletion Job ~139
Retrieve the status and details of a specific replay batch deletion job by its ID. Use this to monitor the progress and outcome of a deletion operation.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | The unique identifier of the replay deletion job. This must be a positive integer representing the specific job you want to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. This scopes the request to a specific organization. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL-friendly slug. This scopes the request to a specific project within the organization. |
No output schema declared.
No examples provided.
get_replay_instance Get Replay Instance ~219
Retrieve detailed information about a specific replay session by its ID. Returns comprehensive replay data including metadata, events, and user interactions.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | Optional environment name to filter the replay data. Must be a non-empty string if provided. |
| field | array | – | Optional list of specific fields to include in the response. Only the specified fields will be marshaled in the output; invalid field names will be rejected. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. Required to scope the replay to the correct organization. |
| per_page | integer | – | Optional limit on the number of rows to return in the result set. Useful for paginating large replay datasets. |
| query | string | – | Optional structured query string to filter the replay output. Must be a non-empty string if provided and should follow the API's query syntax. |
| replay_id | string | yes | The unique identifier of the replay to retrieve, formatted as a UUID. This must be a valid UUID string. |
No output schema declared.
No examples provided.
get_repository Get Repository ~93
Retrieves detailed metadata for a single repository within an organization, identified by its owner and repository name.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| owner | string | yes | The owner identifier of the repository, typically a user or team name within the organization. |
| repository | string | yes | The name of the repository to retrieve. |
No output schema declared.
No examples provided.
get_repository_sync_status Get Repository Sync Status ~84
Retrieves the synchronization status of repositories for an integrated organization, showing which repositories are currently syncing and their progress.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| owner | string | yes | The repository owner identifier, typically a username or organization name that owns the repositories being queried. |
No output schema declared.
No examples provided.
get_service_hook Get Service Hook ~93
Retrieve a specific service hook configured for a project. Returns the hook's configuration and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| hook_id | string | yes | The unique identifier (GUID) of the service hook to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
get_source_map_debug_for_event Get Source Map Debug for Event ~166
Retrieve source map resolution errors for a specific stack frame and exception within an event, helping diagnose why source maps failed to map minified code back to original sources.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The event identifier as a UUID that uniquely identifies the error event to debug. |
| exception_idx | integer | yes | The zero-based index of the exception within the event's exception chain to analyze for source map resolution issues. |
| frame_idx | integer | yes | The zero-based index of the stack frame within the exception to analyze for source map resolution issues. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL-friendly slug. |
No output schema declared.
No examples provided.
get_spike_protection_notification_action Get Spike Protection Notification Action ~94
Retrieve a specific Spike Protection Notification Action that notifies organization members when spike detection is triggered. This action defines how and which members are alerted through services like Slack or email.
| Name | Type | Req | Description |
|---|---|---|---|
| action_id | integer | yes | The numeric identifier of the notification action to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. Use whichever format you have available. |
No output schema declared.
No examples provided.
get_tag_values_for_issue Get Tag Values for Issue ~130
Retrieve all values associated with a specific tag key for an issue, with optional filtering by environment. Results are paginated and return at most 1000 values.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | Optional list of environment names to filter tag values by. When specified, only values from the listed environments are returned. |
| issue_id | integer | yes | The numeric identifier of the issue to query for tag values. |
| key | string | yes | The tag key name to retrieve associated values for. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. |
No output schema declared.
No examples provided.
get_team Get Team ~177
Retrieve detailed information about a specific team within an organization. Use organization and team identifiers (IDs or slugs) to fetch the team resource with optional expansion of related data.
| Name | Type | Req | Description |
|---|---|---|---|
| collapse | string | – | Comma-separated list of data fields to exclude from the response. Supports `organization` to omit the parent organization details. |
| expand | string | – | Comma-separated list of related data to include in the response. Supports `projects` to include team projects and `externalTeams` to include external team integrations. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. This scopes the team lookup to a specific organization. |
| team_id_or_slug | string | yes | The team identifier, either the numeric ID or the URL-friendly slug. Combined with the organization identifier to uniquely identify the team. |
No output schema declared.
No examples provided.
get_test_results_aggregates_for_repository Get Test Results Aggregates for Repository ~148
Retrieves aggregated test result metrics for a specific repository within an organization, with optional filtering by branch. Metrics can be scoped to a particular time period via query parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Optional branch name to filter results. When omitted, metrics are aggregated across all branches of the repository. |
| organization_id_or_slug | string | yes | The organization identifier, either as a numeric ID or URL-friendly slug. This determines which organization's data is accessed. |
| owner | string | yes | The owner or account name that owns the repository. Used to scope the repository lookup within the organization. |
| repository | string | yes | The name of the repository for which to retrieve test result metrics. |
No output schema declared.
No examples provided.
link_external_team Link External Team ~221
Link a team from an external provider (such as GitHub, Slack, Jira, or GitLab) to a Sentry team, enabling cross-platform team synchronization and integration.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | – | The unique identifier of the external team or user within the provider system. This field is optional and may be required depending on the provider. |
| external_name | string | yes | The name or identifier of the external team as it appears in the provider system. |
| integration_id | integer | yes | The numeric ID of the integration configuration that connects Sentry to the external provider. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| provider | string | yes | The external provider platform. Supported providers include GitHub, GitHub Enterprise, Jira Server, Slack, Slack Staging, Perforce, GitLab, Microsoft Teams, and custom SCM systems. |
| team_id_or_slug | string | yes | The team identifier, either the numeric ID or the URL slug of the team within the organization. |
No output schema declared.
No examples provided.
link_external_user Link External User ~213
Link a user from an external provider (such as GitHub, Slack, Jira, or GitLab) to a Sentry user account, enabling cross-platform identity mapping and integration.
| Name | Type | Req | Description |
|---|---|---|---|
| external_id | string | – | The unique user identifier or account ID assigned by the external provider. This is optional if the external name is sufficient for identification. |
| external_name | string | yes | The display name or username associated with the user in the external provider system. |
| integration_id | integer | yes | The numeric ID of the integration configuration that connects Sentry to the external provider. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| provider | string | yes | The external provider platform. Supported providers include GitHub, GitHub Enterprise, Jira Server, Slack, Slack Staging, Perforce, GitLab, Microsoft Teams, and custom SCM systems. |
| user_id | integer | yes | The numeric ID of the Sentry user to link to the external provider. |
No output schema declared.
No examples provided.
list_alerts List Alerts ~81
Retrieve a list of alerts for an organization. This endpoint is currently in beta and supports the New Monitors and Alerts feature.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL slug of the organization. |
| query | string | – | Optional search query to filter alerts by name, status, or other alert properties. |
No output schema declared.
No examples provided.
list_checkins_for_monitor List Check-ins for Monitor ~90
Retrieve all check-ins recorded for a specific monitor, showing the history of uptime verification events.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id_or_slug | string | yes | The monitor identifier, which can be either the numeric ID or the URL-friendly slug of the monitor within the organization. |
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
No output schema declared.
No examples provided.
list_checkins_for_monitor_in_project List Check-ins for Monitor in Project ~139
Retrieve all check-ins recorded for a specific monitor within a project. Check-ins represent heartbeat or status update events tracked by the monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| monitor_id_or_slug | string | yes | The monitor identifier, either the numeric ID or the URL-friendly slug. This specifies which monitor's check-ins to retrieve. |
| organization_id_or_slug | string | yes | The organization identifier, either the numeric ID or the URL-friendly slug. This scopes the request to a specific organization. |
| project_id_or_slug | string | yes | The project identifier, either the numeric ID or the URL-friendly slug. This scopes the request to a specific project within the organization. |
No output schema declared.
No examples provided.
list_clicked_nodes List Clicked Nodes ~201
Retrieve all DOM nodes that were clicked during a session replay, including their RRWeb node IDs and exact click timestamps. Use this to understand user interaction patterns within a specific replay.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | array | – | Filter results to include only clicks from sessions in specified environments. Provide as a list of environment names. |
| organization_id_or_slug | string | yes | The organization identifier, either its unique ID or URL-friendly slug. |
| per_page | integer | – | Limit the number of results returned. Maximum allowed is 100 (default). |
| project_id_or_slug | string | yes | The project identifier, either its unique ID or URL-friendly slug. |
| query | string | – | Filter results using Sentry's query syntax to narrow down clicks by transaction, release, or other attributes. Supports boolean operators (AND, OR) and comma-separated value lists. |
| replay_id | string | yes | The unique identifier (UUID format) of the replay session to retrieve click data from. |
No output schema declared.
No examples provided.
list_data_forwarders_for_organization List Data Forwarders for Organization ~67
Retrieves all data forwarders configured for a specific organization. Data forwarders enable automatic forwarding of events and data to external destinations.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
No output schema declared.
No examples provided.
list_debug_information_files List Debug Information Files ~102
Retrieve all debug information files (dSYMs and other debug symbols) associated with a specific project. These files are used for symbolication and error tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| organization_id_or_slug | string | yes | The organization identifier, which can be either the numeric ID or the URL-friendly slug of the organization. |
| project_id_or_slug | string | yes | The project identifier, which can be either the numeric ID or the URL-friendly slug of the project within the organization. |
No output schema declared.
No examples provided.
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 48 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.