# io.github.IDTitanium/clippy (remote · useclippy.cc)

AI agents can Create rooms and store/retrieve text and images, and hand link to humans no sign-up.

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `useclippy.cc`: 70/100 (this document), [markdown](https://verifymcp.io/servers/idtitanium-clippy/useclippy.md), [page](https://verifymcp.io/servers/idtitanium-clippy/useclippy)

## Channel facts

- Endpoint: `https://useclippy.cc/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-08-03.

- **Endpoint Security**: 63/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 (delete-item-tool).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1914 tokens (~191/item across 10 items; 9 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http idtitanium-clippy https://useclippy.cc/mcp
```

### Codex

```toml
[mcp_servers.idtitanium-clippy]
url = "https://useclippy.cc/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "idtitanium-clippy": {
      "type": "remote",
      "url": "https://useclippy.cc/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add idtitanium-clippy --url https://useclippy.cc/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  idtitanium-clippy:
    url: "https://useclippy.cc/mcp"
```

### Other

```json
{
  "mcpServers": {
    "idtitanium-clippy": {
      "type": "http",
      "url": "https://useclippy.cc/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-08-03 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 67, +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-07-27 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 66)

First indexed and scored.

## MCP tools (9)

### `create-room-tool` (~109 tokens)

Create Clippy Room

Create a brand-new Clippy room and get back its 6-character code, a private owner_token, and a share URL. Use this when you want a fresh shared clipboard to push content to a user (hand them the URL) or to coordinate with other agents. Keep the owner_token private — it grants password control over the room.

Input parameters:

- `password` (string): Optional. Lock the new room with this password so only holders of the password (or the owner_token) can read/write it.

Output parameters:

- `code` (string): The new 6-character room code.
- `locked` (boolean): Whether the room is password-protected.
- `owner_token` (string): Private token granting password control over the room. Keep secret.
- `url` (string): Human-shareable URL that opens the room on any device.

### `store-item-tool` (~214 tokens)

Store Item in Clippy Room

Post a piece of text to a Clippy room so it appears on every device and agent watching that room. The room is created automatically if it does not exist yet. Subscribed devices receive a push notification. This is how you "send" something to a user or leave a note for another agent. Returns the stored item.

Input parameters:

- `device` (string): Optional short label for who is posting (max 64 chars). Defaults to "AI Agent" so humans can tell agent posts apart.
- `owner_token` (string): Optional. The room owner_token; bypasses the password on a locked room.
- `password` (string): Required only if the room is password-protected and you are not using owner_token.
- `room` (string, required): The 6-character room code (or a Clippy share URL / #CODE link). The room is created if new.
- `text` (string, required): The text content to store (a snippet, link, message, etc.). Up to 200,000 characters.

Output parameters:

- `code` (string): The room code the item was stored in.
- `item` (object): The stored item.
- `url` (string): Human-shareable URL that opens the room on any device.

### `store-image-tool` (~271 tokens)

Store Image in Clippy Room

Post one or more images (PNG, JPEG, GIF, or WEBP) to a Clippy room so they appear on every device watching it, optionally with a text caption. Pass each image as a base64 string or a data: URI. The room is created if it does not exist. Subscribed devices get a push notification. Returns the stored item, including direct URLs to fetch each image.

Input parameters:

- `device` (string): Optional short label for who is posting (max 64 chars). Defaults to "AI Agent".
- `images` (array, required): One or more images, each a base64-encoded PNG/JPEG/GIF/WEBP or a data: URI (e.g. "data:image/png;base64,iVBOR..."). Up to 10 images, 10 MB each.
- `owner_token` (string): Optional. The room owner_token; bypasses the password on a locked room.
- `password` (string): Required only if the room is password-protected and you are not using owner_token.
- `room` (string, required): The 6-character room code (or a Clippy share URL / #CODE link). The room is created if new.
- `text` (string): Optional caption to store alongside the image(s). Up to 200,000 characters.

Output parameters:

- `code` (string): The room code the image was stored in.
- `item` (object): The stored item, including image URLs.
- `url` (string): Human-shareable URL that opens the room on any device.

### `list-items-tool` (~207 tokens)

List Clippy Room Items

Read the items in a Clippy room (newest first). Use this to pick up text a user or another agent left for you, or to see what is currently in a shared room. Pass `since` (a millisecond timestamp from a previous call) to fetch only items added after that point. Image items include direct image URLs.

Input parameters:

- `limit` (integer): Optional. Maximum number of items to return (1–100). Defaults to 100.
- `owner_token` (string): Optional. The room owner_token; bypasses the password on a locked room.
- `password` (string): Required only if the room is password-protected and you are not using owner_token.
- `room` (string, required): The 6-character room code (or a Clippy share URL / #CODE link).
- `since` (integer): Optional. Return only items created strictly after this Unix timestamp in milliseconds. Use the `now` value from a previous call to poll incrementally.

Output parameters:

- `code` (string): The room code that was read.
- `count` (integer): Number of items returned.
- `items` (array): The matching items, newest first.
- `locked` (boolean): Whether the room is password-protected.
- `now` (integer): Server time in Unix milliseconds; pass as `since` next call to poll incrementally.

### `room-status-tool` (~80 tokens)

Clippy Room Status

Check whether a Clippy room exists, whether it is password-protected, and how many items it holds — without reading the contents. Handy before deciding to read or write, or to confirm a code a user gave you is valid.

Input parameters:

- `room` (string, required): The 6-character room code (or a Clippy share URL / #CODE link).

Output parameters:

- `code` (string): The room code that was checked.
- `exists` (boolean): Whether the room currently exists.
- `itemCount` (integer): Number of items currently in the room.
- `locked` (boolean): Whether the room is password-protected.
- `url` (string): Human-shareable URL for the room.

### `update-item-tool` (~177 tokens)

Update Clippy Item

Edit the text of an existing item in a Clippy room, identified by its item id (the `id` field returned by store-item / list-items). Image bytes are immutable; this changes only the text.

Input parameters:

- `item_id` (string, required): The item id (UUID) to edit, as returned in the `id` field of a stored/listed item.
- `owner_token` (string): Optional. The room owner_token; bypasses the password on a locked room.
- `password` (string): Required only if the room is password-protected and you are not using owner_token.
- `room` (string, required): The 6-character room code (or a Clippy share URL / #CODE link).
- `text` (string, required): The new text. For a text-only item this cannot be empty — delete it instead.

Output parameters:

- `code` (string): The room code containing the item.
- `item` (object): The updated item.

### `delete-item-tool` (~136 tokens)

Delete Clippy Item

Delete a single item from a Clippy room by its item id (the `id` returned by store-item / list-items). Any images attached to the item are removed too. This cannot be undone.

Input parameters:

- `item_id` (string, required): The item id (UUID) to delete.
- `owner_token` (string): Optional. The room owner_token; bypasses the password on a locked room.
- `password` (string): Required only if the room is password-protected and you are not using owner_token.
- `room` (string, required): The 6-character room code (or a Clippy share URL / #CODE link).

Output parameters:

- `code` (string): The room code that was targeted.
- `deleted` (boolean): Whether an item was actually deleted (false if it did not exist).

### `clear-room-tool` (~119 tokens)

Clear Clippy Room

Delete ALL items in a Clippy room (and their images). Use with care — this wipes everything shared in the room and cannot be undone. The room itself continues to exist and can be reused.

Input parameters:

- `owner_token` (string): Optional. The room owner_token; bypasses the password on a locked room.
- `password` (string): Required only if the room is password-protected and you are not using owner_token.
- `room` (string, required): The 6-character room code (or a Clippy share URL / #CODE link).

Output parameters:

- `cleared` (integer): Number of items that were deleted.
- `code` (string): The room code that was cleared.

### `set-room-password-tool` (~125 tokens)

Set Clippy Room Password

Lock or unlock a Clippy room. Requires the room owner_token (returned by create-room). Pass a password to lock the room; pass an empty password to remove the lock. Only the owner can change this.

Input parameters:

- `owner_token` (string, required): The room owner_token proving you own this room. Required.
- `password` (string): The new password to lock the room with. Pass an empty string to remove the password and make the room open.
- `room` (string, required): The 6-character room code (or a Clippy share URL / #CODE link).

Output parameters:

- `code` (string): The room code whose lock state changed.
- `locked` (boolean): Whether the room is now password-protected.

## Diagnostics

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

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 68
- 2026-07-29: 68
- 2026-07-28: 67
- 2026-07-27: 66
- 2026-07-26: 66

## Links

- Remote endpoint: https://useclippy.cc/mcp
- Repository: https://github.com/IDTitanium/clippy
- Website: https://useclippy.cc/
- Changelog RSS feed: https://verifymcp.io/servers/idtitanium-clippy/useclippy/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/idtitanium-clippy/useclippy/changelog.json
- HTML version of this page: https://verifymcp.io/servers/idtitanium-clippy/useclippy