Source-backed dependency evidence for Sentry issues avatar

Source-backed dependency evidence for Sentry issues

Pricing

Pay per usage

Go to Apify Store
Source-backed dependency evidence for Sentry issues

Source-backed dependency evidence for Sentry issues

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.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Abdulrahman Baidaq

Abdulrahman Baidaq

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

20 days ago

Last modified

Share

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

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.