Skip to main content
Glama
neopunisher
by neopunisher

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PASTEBIN_DEV_KEYYesYour Pastebin developer API key
PASTEBIN_USER_KEYNoUser Key returned by login (required for private/list/delete)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
loginA

Login to Pastebin to get a User API Key for private pastes and listing.

create_pasteC

Create a new paste on Pastebin.

list_user_pastesB

List your pastes (requires login).

delete_pasteA

Delete a paste (requires login/api_user_key).

stopA

Stop the MCP server. This will terminate the process.

get_trending_pastesB

Get the top trending pastes on Pastebin.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: authentication (login), discovery (get_trending_pastes), creation (create_paste), listing (list_user_pastes), deletion (delete_paste), and lifecycle (stop). There is no meaningful overlap between any two tools, so an agent can easily select the right one.

Naming Consistency4/5

Most tools follow a clean verb_noun pattern (get_trending_pastes, create_paste, list_user_pastes, delete_paste), which is highly predictable. However, login and stop are bare verbs that break the pattern, a minor deviation.

Tool Count5/5

Six tools is well within the sweet spot and each maps to a real operation in the Pastebin domain (auth, discovery, CRUD-ish paste management, shutdown). No tool feels redundant or padded.

Completeness3/5

Core lifecycle is present (login, create, list, delete, trending), but there is no tool to retrieve/view a specific paste by key or URL, which is a fundamental read operation for a Pastebin server. This notable gap will force agents to work around the missing read capability.