BugTape demo
REMOTE · APP.BUGTAPE.AI
Read-only sample shop with captured bug evidence. No account or key needed.
Available components
Last scanned (4 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1847 tokens (~131/item across 14 items; 14 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- Tool “get_bug” rewrote its description, which is the text the model reads security
- Tool “get_repro_context” rewrote its description, which is the text the model reads security
- Tool “list_bugs” rewrote its description, which is the text the model reads security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 73
First indexed and scored.
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 · Probed https://app.bugtape.ai/demo/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.bugtape.ai | CN=YE2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 686fc5da090c00b87674f3bbde73bceba50 |
| SANs: app.bugtape.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.bugtape.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| bugtape.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.bugtape.ai/demo/mcp | Verified | 200 | |
| http (plaintext) | http://app.bugtape.ai/demo/mcp | HTTPS enforced | 301 | https://app.bugtape.ai/demo/mcp |
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 →
get_bug Read an issue ~88
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. isExample: true marks BugTape's practice bug (see exampleNote).
| Name | Type | Req | Description |
|---|---|---|---|
| bugId | string | yes | The bug ID |
No output schema declared.
No examples provided.
get_bug_events Read captured events ~113
Get session events for a bug (DOM, network, console, clicks, errors). Prefer passing occurrenceId so events are not mixed across captures.
| Name | Type | Req | Description |
|---|---|---|---|
| bugId | string | yes | The bug ID |
| limit | number | – | Max events to return |
| occurrenceId | string | – | Pin events to one occurrence (recommended) |
| offset | integer | – | Continue from the previous response nextOffset |
| type | string | – | Filter by event type (e.g., "click", "console-error", "network") |
No output schema declared.
No examples provided.
get_bug_history Get Bug History ~43
Get the full audit trail of status/severity changes and assignments on a bug, including who changed what and when.
| Name | Type | Req | Description |
|---|---|---|---|
| bugId | string | yes | The bug ID |
No output schema declared.
No examples provided.
get_bug_occurrences Get Bug Occurrences ~67
List the individual occurrences grouped under a bug. Use this to see which users, sessions, releases, or environments were affected.
| Name | Type | Req | Description |
|---|---|---|---|
| bugId | string | yes | The grouped bug ID |
| limit | number | – | Max occurrences to return |
| offset | number | – | Pagination offset |
No output schema declared.
No examples provided.
get_bug_users Get Bug Users ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bugId | string | yes | The grouped bug ID |
| limit | number | – | Max users to return (newest last-seen first) |
| offset | number | – | Pagination offset |
No output schema declared.
No examples provided.
get_current_org Current workspace ~33
Return the credential workspace. Agent PATs resolve only their own workspace; human sessions use BUGTAPE_ORG_ID.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_live_occurrences Get Live Occurrences ~80
Get the most recent occurrences across the organization. Useful for live monitoring and tester workflows. Honors deliveryFeed (tool arg, else PAT / project).
| Name | Type | Req | Description |
|---|---|---|---|
| deliveryFeed | string | – | Delivery feed: all, urgent_critical, or ui_ux. Defaults to the PAT or project setting. |
| limit | number | – | Max live occurrences to return |
No output schema declared.
No examples provided.
get_project_stats Get Project Stats ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Timeline window in days (default 30) |
| deliveryFeed | string | – | Delivery feed: all, urgent_critical, or ui_ux. Defaults to the PAT or project setting. |
| projectId | string | yes | Project ID |
No output schema declared.
No examples provided.
get_repro_context Read issue evidence ~136
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. For an example bug (isExample: true) the pack is practice data and costs no credits.
| Name | Type | Req | Description |
|---|---|---|---|
| bugId | string | yes | The bug ID |
| eventLimit | number | – | Max raw events to scan before summarizing |
| occurrenceId | string | – | Pin to one occurrence. If omitted, uses the latest occurrence when available. |
No output schema declared.
No examples provided.
get_similar_bugs Get Similar Bugs ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bugId | string | yes | The bug ID to find similar bugs for |
No output schema declared.
No examples provided.
list_bug_groups List Bug Groups ~404
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), browsers/oses, platforms (web/ios/android/react-native/flutter/server — one issue can span several), and anyRegression. Pass both projectId and groupKey as one groupRefs entry to bulk_update_bugs. Legacy groupKeys are accepted only when unique across the organization and are rejected when ambiguous. Prefer this over list_bugs for triage.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | 'unassigned', or a user id from list_team — narrows to bugs assigned to that person (or none) |
| deliveryFeed | string | – | Delivery feed: all, urgent_critical, or ui_ux. Defaults to the PAT or project setting. |
| direction | string | – | Sort direction for the chosen key (default desc; ties break on last_seen desc) |
| limit | number | – | Number of groups (default 20) |
| offset | number | – | Pagination offset |
| platform | string | – | Only groups with an occurrence captured on this platform |
| projectId | string | – | Filter by project ID |
| search | string | – | Search text in title and description |
| severity | string | – | Filter by per-bug severity |
| sort | string | – | Sort key: last_seen (default), first_seen, count (occurrences), severity, title, signal (regressions first), assignee (display name, unassigned last) |
| status | string | – | Filter by per-bug status (groups also expose aggregated topStatus) |
| unresolved | boolean | – | true = only groups whose aggregated topStatus is not resolved/silenced |
No output schema declared.
No examples provided.
list_bugs List Bugs ~259
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. A new project holds one labelled example bug (isExample: true, title starts "Example: "); it is practice data, not from the app.
| Name | Type | Req | Description |
|---|---|---|---|
| deliveryFeed | string | – | 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. |
| limit | number | – | Number of results (default 20) |
| offset | number | – | Pagination offset |
| platform | string | – | Only bugs with an occurrence captured on this platform |
| projectId | string | – | Filter by project ID |
| search | string | – | Search text in title and description |
| severity | string | – | Filter by severity |
| status | string | – | Filter by bug status |
No output schema declared.
No examples provided.
list_projects List projects ~19
List all projects in the organization with their bug counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_recommended_critical Find urgent issues ~157
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_bugs for what to work on. Diagnostic, silenced, and agent-acked rows are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| projectId | string | – | – |
| since | string | – | ISO timestamp; only rows recommended after this |
No output schema declared.
No examples provided.
How do I install the BugTape demo MCP server?
BugTape demo is a hosted endpoint at https://app.bugtape.ai/demo/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · app.bugtape.ai
claude mcp add --transport http ai-bugtape-bugtape-demo 'https://app.bugtape.ai/demo/mcp'
What is the BugTape demo MCP server?
BugTape demo is an MCP server listed in the public MCP registry as ai.bugtape/bugtape-demo. Read-only sample shop with captured bug evidence. No account or key needed. This page covers its hosted endpoint (https://app.bugtape.ai/demo/mcp).
Is the BugTape demo MCP server safe to use?
BugTape demo scores 77 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 BugTape demo MCP server expose?
BugTape demo exposes 14 tools: list_bugs, get_bug, get_bug_events, get_repro_context, list_projects, and 9 more. Their descriptions and schemas cost roughly 1,713 tokens of context every time the server is loaded.
Does the BugTape demo MCP server require authentication?
No. We connected to BugTape demo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BugTape demo MCP server still maintained?
BugTape demo 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.