Developer Tools

yakbin.io

A developer-focused pastebin MCP server for creating, reading, inspecting, and bundling shareable text/file snippets with secret scanning.

1 endpoint11 known toolsFirst detected October 2, 2026Last detected October 2, 2026

ENDPOINT 1

https://yakbin.io/mcp

No auth detected

MCP server metadata

Name: Yakbin
Version: sha-2266016

Capabilities

tools

Server instructions

yakbin shares text between people and agents. - Use create_paste / create_bundle to hand off logs, diffs and files as a link. - Use read_paste and read_bundle to read one back. They return a token-budgeted slice by default; narrow with lines, grep or tail instead of asking for everything. - Content is stored exactly as given. scan_text reports possible secrets without storing anything; pass redact=true to mask them or strict=true to refuse. - get_comments (with wait_seconds) lets you wait for a person's reply on a paste.

Known tools 11

create_paste

Store text and get a shareable link.

Inferred read-only

read_paste

Read a paste.

Inferred read-only

paste_info

Metadata for a paste: size, sha256, expiry, whether secrets were found.

Inferred read-only

scan_text

Check text for possible secrets without storing it.

Inferred read-only

create_bundle

Store several files (logs, diff, prompt, config…) under one link so they can be read together.

Inferred read-only

read_bundle

Read a bundle: every file in one LLM-ready document within a token budget, or one file if path is given.

Inferred read-only

comment

Add a comment to a paste, optionally on a range of lines.

Inferred read-only

get_comments

Get comments on a paste.

Inferred read-only

create_link

Make a time-limited read link for one of your pastes, so you can share a private paste.

Inferred read-only

list_pastes

List your account's recent pastes.

Inferred read-only

delete_paste

Delete one of your pastes.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.yakbin]
url = "https://yakbin.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "yakbin": {
      "type": "http",
      "url": "https://yakbin.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: yakbin
Remote MCP URL: https://yakbin.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "yakbin": {
      "url": "https://yakbin.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "yakbin": {
      "type": "http",
      "url": "https://yakbin.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "yakbin",
  "transport": "streamable-http",
  "url": "https://yakbin.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.