io.github.IDTitanium/clippy
REMOTE · USECLIPPY.CC · SCANNED SEP 20
AI agents can Create rooms and store/retrieve text and images, and hand link to humans no sign-up.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete-item-tool). See how to fix → View diagnostics → Fail
- 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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 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
How do I install the io.github.IDTitanium/clippy MCP server?
io.github.IDTitanium/clippy is a hosted endpoint at https://useclippy.cc/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 · useclippy.cc
claude mcp add --transport http idtitanium-clippy 'https://useclippy.cc/mcp'
{
"mcpServers": {
"idtitanium-clippy": {
"url": "https://useclippy.cc/mcp"
}
}
} {
"servers": {
"idtitanium-clippy": {
"type": "http",
"url": "https://useclippy.cc/mcp"
}
}
} [mcp_servers.idtitanium-clippy] url = "https://useclippy.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"idtitanium-clippy": {
"type": "remote",
"url": "https://useclippy.cc/mcp",
"enabled": true
}
}
} openclaw mcp add idtitanium-clippy --url 'https://useclippy.cc/mcp' --transport streamable-http
mcp_servers:
idtitanium-clippy:
url: "https://useclippy.cc/mcp" {
"McpServers": {
"idtitanium-clippy": {
"Transport": "http",
"Url": "https://useclippy.cc/mcp"
}
}
} assistant mcp add idtitanium-clippy -t streamable-http -u 'https://useclippy.cc/mcp'
{
"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.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 20 Sept 2026 · Probed https://useclippy.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=useclippy.cc | CN=WE1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 82541d9b27cc4ca40e1bf0fb2319093e |
| SANs: useclippy.cc | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of useclippy.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| useclippy.cc. | 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 |
| content-security-policy | default-src 'self'; img-src 'self' data: blob:; style-src 'self' 'unsafe-inline'; script-src 'self'; font-src 'self' data:; connect-src 'self'; worker-src 'self'; manifest-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=(), usb=(), magnetometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://useclippy.cc/mcp | Verified | 200 | |
| http (plaintext) | http://useclippy.cc/mcp | HTTPS enforced | 301 | https://useclippy.cc/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 →
clear-room-tool Clear Clippy Room ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The 6-character room code (or a Clippy share URL / #CODE link). |
| Name | Type | Req | Description |
|---|---|---|---|
| cleared | integer | yes | Number of items that were deleted. |
| code | string | yes | The room code that was cleared. |
No examples provided.
create-room-tool Create Clippy Room ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| password | string | – | Optional. Lock the new room with this password so only holders of the password (or the owner_token) can read/write it. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The new 6-character room code. |
| locked | boolean | yes | Whether the room is password-protected. |
| owner_token | string | yes | Private token granting password control over the room. Keep secret. |
| url | string | yes | Human-shareable URL that opens the room on any device. |
No examples provided.
delete-item-tool Delete Clippy Item ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | 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 | yes | The 6-character room code (or a Clippy share URL / #CODE link). |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The room code that was targeted. |
| deleted | boolean | yes | Whether an item was actually deleted (false if it did not exist). |
No examples provided.
list-items-tool List Clippy Room Items ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The room code that was read. |
| count | integer | yes | Number of items returned. |
| items | array | yes | The matching items, newest first. |
| locked | boolean | yes | Whether the room is password-protected. |
| now | integer | yes | Server time in Unix milliseconds; pass as `since` next call to poll incrementally. |
No examples provided.
room-status-tool Clippy Room Status ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| room | string | yes | The 6-character room code (or a Clippy share URL / #CODE link). |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The room code that was checked. |
| exists | boolean | yes | Whether the room currently exists. |
| itemCount | integer | yes | Number of items currently in the room. |
| locked | boolean | yes | Whether the room is password-protected. |
| url | string | yes | Human-shareable URL for the room. |
No examples provided.
set-room-password-tool Set Clippy Room Password ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| owner_token | string | yes | 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 | yes | The 6-character room code (or a Clippy share URL / #CODE link). |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The room code whose lock state changed. |
| locked | boolean | yes | Whether the room is now password-protected. |
No examples provided.
store-image-tool Store Image in Clippy Room ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | – | Optional short label for who is posting (max 64 chars). Defaults to "AI Agent". |
| images | array | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The room code the image was stored in. |
| item | object | yes | The stored item, including image URLs. |
| url | string | yes | Human-shareable URL that opens the room on any device. |
No examples provided.
store-item-tool Store Item in Clippy Room ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The 6-character room code (or a Clippy share URL / #CODE link). The room is created if new. |
| text | string | yes | The text content to store (a snippet, link, message, etc.). Up to 200,000 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The room code the item was stored in. |
| item | object | yes | The stored item. |
| url | string | yes | Human-shareable URL that opens the room on any device. |
No examples provided.
update-item-tool Update Clippy Item ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | 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 | yes | The 6-character room code (or a Clippy share URL / #CODE link). |
| text | string | yes | The new text. For a text-only item this cannot be empty — delete it instead. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The room code containing the item. |
| item | object | yes | The updated item. |
No examples provided.
What is the io.github.IDTitanium/clippy MCP server?
io.github.IDTitanium/clippy is an MCP server listed in the public MCP registry as io.github.IDTitanium/clippy. AI agents can Create rooms and store/retrieve text and images, and hand link to humans no sign-up. This page covers its hosted endpoint (https://useclippy.cc/mcp).
Is the io.github.IDTitanium/clippy MCP server safe to use?
io.github.IDTitanium/clippy scores 82 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.IDTitanium/clippy MCP server expose?
io.github.IDTitanium/clippy exposes 9 tools: create-room-tool, store-item-tool, store-image-tool, list-items-tool, room-status-tool, and 4 more. Their descriptions and schemas cost roughly 1,438 tokens of context every time the server is loaded.
Does the io.github.IDTitanium/clippy MCP server require authentication?
No. We connected to io.github.IDTitanium/clippy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.IDTitanium/clippy MCP server still maintained?
io.github.IDTitanium/clippy 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.