# Source-backed dependency evidence for Sentry issues (`rare_sunset/sentry-dependency-evidence`) Actor

Unofficial Sentry integration; not affiliated with Sentry. Read a Sentry issue through an MCP connector, match explicit dependency clues against authoritative release pages, and optionally add a reviewable evidence note.

- **URL**: https://apify.com/rare\_sunset/sentry-dependency-evidence.md
- **Developed by:** [Abdulrahman Baidaq](https://apify.com/rare_sunset) (community)
- **Categories:** Developer tools, Integrations, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Source-backed dependency evidence for Sentry issues

This Actor reads one Sentry issue through a user-authorized MCP connector, compares explicit dependency/version/error clues with a small list of authoritative public release pages, and produces a reviewable evidence note. Writing the note is off by default.

It deliberately does not claim that a textual release-note match proves root cause. The output uses `review_recommended`, `possible_evidence`, or `insufficient_evidence` and preserves source URLs and SHA-256 receipts.

### Local tests

```powershell
python -m unittest discover -s tests -v
```

### Safety boundary

- The Actor receives only the selected connector ID, never the underlying Sentry credential.
- The input schema declares only Sentry's `execute_sentry_tool` catalog wrapper; the Actor routes it to `get_issue_details` and, after approval, `add_issue_note`.
- `write_note` defaults to `false`; inspect `NOTE_PREVIEW` before enabling it.
- Only explicit HTTPS evidence URLs are fetched, with time and byte limits.

# Actor input Schema

## `issue_url` (type: `string`):

Full URL of the Sentry issue to inspect.

## `sentry_connector` (type: `string`):

Authorized Sentry MCP connector. Credentials remain in Apify's connector proxy.

## `dependency_name` (type: `string`):

Exact package or dependency name to investigate; the Actor does not infer causality.

## `observed_version` (type: `string`):

Exact dependency version observed in the affected application or event.

## `error_terms` (type: `array`):

Short literal terms that should be matched in supplied authoritative documentation.

## `evidence_urls` (type: `array`):

One to five explicit public HTTPS pages maintained by the dependency project.

## `write_note` (type: `boolean`):

Off by default. Review NOTE\_PREVIEW before enabling this mutation.

## Actor input object example

```json
{
  "error_terms": [],
  "write_note": false
}
```

# Actor output Schema

## `evidence` (type: `string`):

No description

## `report` (type: `string`):

No description

## `notePreview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("rare_sunset/sentry-dependency-evidence").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("rare_sunset/sentry-dependency-evidence").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call rare_sunset/sentry-dependency-evidence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,rare_sunset/sentry-dependency-evidence"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/00eoVU4hmZQXkfN3N/builds/DbW6qsMPYhf3BbwVN/openapi.json