# Pebble (remote · shippebble.com)

Host the tools your AI builds — small internal tools in isolated microVMs, live for your team.

- Trust score: 36/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `shippebble.com`: 36/100 (this document), [markdown](https://verifymcp.io/servers/com-shippebble-pebble/shippebble.md), [page](https://verifymcp.io/servers/com-shippebble-pebble/shippebble)

## Channel facts

- Endpoint: `https://shippebble.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Pebble MCP server?

Pebble is a hosted endpoint at https://shippebble.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 com-shippebble-pebble 'https://shippebble.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-shippebble-pebble": {
      "url": "https://shippebble.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-shippebble-pebble]
url = "https://shippebble.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-shippebble-pebble:
    url: "https://shippebble.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-shippebble-pebble": {
      "type": "http",
      "url": "https://shippebble.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-18 (score 36, 0)

- [security regression] Transport: unverified → fail
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema.

### 2026-09-17 (score 36, +32)

- [security regression] HSTS header: unverified → fail
- [security regression] Transport: fail → unverified
- [security improvement] Authorization: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security] First check of Authorization: partial
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-09-15 (score 4)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-shippebble-pebble/shippebble#diagnostics

## Score history

- 2026-09-20: 36
- 2026-09-19: 36
- 2026-09-18: 36
- 2026-09-17: 36
- 2026-09-16: 4
- 2026-09-15: 4

## Common questions

### What is the Pebble MCP server?

Pebble is an MCP server listed in the public MCP registry as com.shippebble/pebble. Host the tools your AI builds, small internal tools in isolated microVMs, live for your team. This page covers its hosted endpoint (https://shippebble.com/mcp).

### Is the Pebble MCP server safe to use?

Pebble scores 36 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.

### Does the Pebble MCP server require authentication?

Its publisher declares no required credentials for Pebble. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Pebble MCP server still maintained?

Pebble is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 17 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://shippebble.com/mcp
- Website: https://shippebble.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-shippebble-pebble/shippebble.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-shippebble-pebble/shippebble.json
- HTML version of this page: https://verifymcp.io/servers/com-shippebble-pebble/shippebble