# io.github.jyswee/buggazi (remote · mcp.buggazi.com)

Project management for coding agents. Bugs, features, sprints. Streamable HTTP + SSE remotes.

- Trust score: 64/100 (medium)
- Change this week: +31
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

> **Recent critical change**: Authorization (2026-09-20). See the changelog below before you install this server.

## Components

- remote · `mcp.buggazi.com`: 70/100, [markdown](https://verifymcp.io/servers/jyswee-buggazi/mcp.md), [page](https://verifymcp.io/servers/jyswee-buggazi/mcp)
- remote · `mcp.buggazi.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/jyswee-buggazi/mcp-2.md), [page](https://verifymcp.io/servers/jyswee-buggazi/mcp-2)
- npm · `buggazi`: 36/100, [markdown](https://verifymcp.io/servers/jyswee-buggazi/buggazi.md), [page](https://verifymcp.io/servers/jyswee-buggazi/buggazi)

## Channel facts

- Endpoint: `https://mcp.buggazi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.14.33`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (buggazi_signup).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 185 tokens (~92/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.jyswee/buggazi MCP server?

io.github.jyswee/buggazi is a hosted endpoint at https://mcp.buggazi.com/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.

### Claude

```bash
claude mcp add --transport http jyswee-buggazi 'https://mcp.buggazi.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jyswee-buggazi": {
      "url": "https://mcp.buggazi.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jyswee-buggazi": {
      "type": "http",
      "url": "https://mcp.buggazi.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jyswee-buggazi]
url = "https://mcp.buggazi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jyswee-buggazi": {
      "type": "remote",
      "url": "https://mcp.buggazi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jyswee-buggazi --url 'https://mcp.buggazi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jyswee-buggazi:
    url: "https://mcp.buggazi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jyswee-buggazi": {
      "Transport": "http",
      "Url": "https://mcp.buggazi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jyswee-buggazi -t streamable-http -u 'https://mcp.buggazi.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jyswee-buggazi": {
      "type": "http",
      "url": "https://mcp.buggazi.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 64, +1)

- [critical regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] MCP protocol: unverified → pass

### 2026-09-19 (score 63, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: fail → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-09-16 (score 63, +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.

### 2026-09-15 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-14 (score 62, +29)

- [critical regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Destructive annotations: pass
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: fair
- [functional] First check of Schema quality: fail

### 2026-09-13 (score 33)

First indexed and scored.

## MCP tools (2)

### `buggazi_get_started` (~34 tokens)

Explains what Buggazi is and how to activate this MCP server (no API key on this session yet).

### `buggazi_signup` (~151 tokens)

Create a new Buggazi tenant. Email is OPTIONAL — you do not need to ask the human first. Returns an API key (shown once) that is LIVE immediately with full access for a 48-hour activation window, and unlocks all Buggazi tools in this session immediately. Before the window closes, a human completes a $0 card-auth to start the free 7-day trial and the same key keeps working.

Input parameters:

- `email` (string): Human email (optional). If given, the $0 card-auth trial link is also emailed here.
- `name` (string): Project display name (optional)
- `slug` (string, required): Short project slug, e.g. "my-app"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jyswee-buggazi/mcp-2#diagnostics

## Score history

- 2026-09-20: 64
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 63
- 2026-09-16: 63
- 2026-09-15: 62
- 2026-09-14: 62
- 2026-09-13: 33

## Common questions

### What is the io.github.jyswee/buggazi MCP server?

io.github.jyswee/buggazi is an MCP server listed in the public MCP registry as io.github.jyswee/buggazi. Project management for coding agents. Bugs, features, sprints. Streamable HTTP + SSE remotes. This page covers its hosted endpoint (https://mcp.buggazi.com/mcp).

### Is the io.github.jyswee/buggazi MCP server safe to use?

io.github.jyswee/buggazi scores 64 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 io.github.jyswee/buggazi MCP server expose?

io.github.jyswee/buggazi exposes 2 tools: buggazi_get_started, buggazi_signup. Their descriptions and schemas cost roughly 185 tokens of context every time the server is loaded.

### Does the io.github.jyswee/buggazi MCP server require authentication?

No. We connected to io.github.jyswee/buggazi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.jyswee/buggazi MCP server still maintained?

io.github.jyswee/buggazi 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.

## Links

- Remote endpoint: https://mcp.buggazi.com/mcp
- Repository: https://github.com/jyswee/buggazi
- Website: https://buggazi.ai/
- Changelog RSS feed: https://verifymcp.io/servers/jyswee-buggazi/mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/jyswee-buggazi/mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/jyswee-buggazi/mcp-2