PA
CreationLoop design partners: company overview, partner offer, FAQ, and apply.
Nothing to run from here
BugTape demo is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read-only sample shop with captured bug evidence. No account or key needed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bugtape-demo-mcp https://app.bugtape.ai/demo/mcp
# 2 — ask your agent for something these tools do
# list_bugs, get_bug, get_bug_events and 11 more
BugTape demo costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BUAll 2 servers
bugtape2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bugtape-demo-mcp https://app.bugtape.ai/demo/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List bugs for the organization (flat, one row per deduplicated report). Supports filtering by status, severity, project, platform, deliveryFeed (all | urgent_critical | ui_ux), and text search. Each row includes affected_user_count, repeat_user_count, and user_spread (user_specific vs widespread). Diagnostic-class signals are excluded by default. Prefer list_bug_groups for grouped triage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Filter by bug status |
| severity | string | no | Filter by severity |
| projectId | string | no | Filter by project ID |
| platform | string | no | Only bugs with an occurrence captured on this platform |
| deliveryFeed | string | no | Delivery feed: all, urgent_critical (severity Score ≥ high and confidence ≥ 0.80), or ui_ux (is_ui_ux Noul ≥ 0.70). Defaults to the PAT or project setting. |
| search | string | no | Search text in title and description |
| limit | number | no | Number of results (default 20) |
| offset | number | no | Pagination offset |
Get full details of a bug including title, description, severity, status, reporters, AI summary, environment info, report count, affected_user_count, repeat_user_count, and user_spread (user_specific vs widespread). Use get_bug_users for the per-user roster.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bugId | string | yes | The bug ID |
Get session events for a bug (DOM, network, console, clicks, errors). Prefer passing occurrenceId so events are not mixed across captures.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bugId | string | yes | The bug ID |
| occurrenceId | string | no | Pin events to one occurrence (recommended) |
| type | string | no | Filter by event type (e.g., "click", "console-error", "network") |
| limit | number | no | Max events to return |
| offset | integer | no | Continue from the previous response nextOffset |
Build an agent-consumable reproduction pack: evidence (timeline, status, env) separate from inference (AI summary). Prefer occurrenceId so sessions are not interleaved. Not raw rrweb. Same pack as resources/read bugtape://bugs/{bugId}/repro.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bugId | string | yes | The bug ID |
| occurrenceId | string | no | Pin to one occurrence. If omitted, uses the latest occurrence when available. |
| eventLimit | number | no | Max raw events to scan before summarizing |
List all projects in the organization with their bug counts.
No parameter schema on file.
Get aggregate statistics for a project (server-computed over bugs in the elected delivery feed, not a sample): counts by status and severity, daily timeline, top unresolved bugs by report count, MTTR, health score, and previous-period comparison.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Project ID |
| days | number | no | Timeline window in days (default 30) |
| deliveryFeed | string | no | Delivery feed: all, urgent_critical, or ui_ux. Defaults to the PAT or project setting. |
List the individual occurrences grouped under a bug. Use this to see which users, sessions, releases, or environments were affected.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bugId | string | yes | The grouped bug ID |
| limit | number | no | Max occurrences to return |
| offset | number | no | Pagination offset |
Who hit this bug: one row per affected end user (the app's identify() userId, else reporter email, else an anonymous IP-hash key) with firstSeen, lastSeen, occurrenceCount, platforms (web/ios/…), lastRelease and lastOccurrenceId. Pass a row's userKey to get_user_timeline to see everything that user experienced across bugs, or to get_repro_context via occurrenceId=lastOccurrenceId.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bugId | string | yes | The grouped bug ID |
| limit | number | no | Max users to return (newest last-seen first) |
| offset | number | no | Pagination offset |
Get the most recent occurrences across the organization. Useful for live monitoring and tester workflows. Honors deliveryFeed (tool arg, else PAT / project).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Max live occurrences to return |
| deliveryFeed | string | no | Delivery feed: all, urgent_critical, or ui_ux. Defaults to the PAT or project setting. |
Return the credential workspace. Agent PATs resolve only their own workspace; human sessions use BUGTAPE_ORG_ID.
No parameter schema on file.
Get the full audit trail of status/severity changes and assignments on a bug, including who changed what and when.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bugId | string | yes | The bug ID |
Find other bugs similar to the given bug, ranked by similarity score (0-100, fingerprint + title overlap). Returns up to 5 matches. Useful before merging or triaging.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bugId | string | yes | The bug ID to find similar bugs for |
Grouped triage view: bugs collapsed across pages by error signature (one group per distinct error within a project, even when dedup created many bug rows). Each group includes projectId + groupKey (the stable group identity), a representative sampleBugId/sampleTitle, instanceCount, occurrenceCount, sessionCount, userCount, maxSeverity, topStatus, signalReason (why the classifier flagged it), brows
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | Filter by project ID |
| platform | string | no | Only groups with an occurrence captured on this platform |
| assignee | string | no | 'unassigned', or a user id from list_team — narrows to bugs assigned to that person (or none) |
| status | string | no | Filter by per-bug status (groups also expose aggregated topStatus) |
| severity | string | no | Filter by per-bug severity |
| search | string | no | Search text in title and description |
| deliveryFeed | string | no | Delivery feed: all, urgent_critical, or ui_ux. Defaults to the PAT or project setting. |
| unresolved | boolean | no | true = only groups whose aggregated topStatus is not resolved/silenced |
| sort | string | no | Sort key: last_seen (default), first_seen, count (occurrences), severity, title, signal (regressions first), assignee (display name, unassigned last) |
| direction | string | no | Sort direction for the chosen key (default desc; ties break on last_seen desc) |
| limit | number | no | Number of groups (default 20) |
| offset | number | no | Pagination offset |
Start here. Returns sentToYou first: bugs a person sent you with "Send to agent" (fix these first), then the prefiltered agent inbox: one row per signature group, new unique issues scored critical/high (or regressions). id is the best qualifying member. member_id_sample is at most 8 member ids; instance_count is the full count and instances_path lists the rest. Use this instead of list_b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | no | — |
| limit | number | no | — |
| since | string | no | ISO timestamp; only rows recommended after this |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install BugTape demo or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 27 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestacf3070d25235ecf498f6713c63165de54a8f7333c0fce8b5b790f398d71c8ad
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_bugs | no tags | |
| get_bug | no tags | |
| get_bug_events | no tags | |
| get_repro_context | no tags | |
| list_projects | no tags | |
| get_project_stats | no tags | |
| get_bug_occurrences | no tags | |
| get_bug_users | no tags | |
| get_live_occurrences | no tags | |
| get_current_org | no tags | |
| get_bug_history | no tags | |
| get_similar_bugs | no tags | |
| list_bug_groups | no tags | |
| list_recommended_critical | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestacf3070d25235ecf
Scanned2026-10-27
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish BugTape demo can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.