Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
skuuy_get_egress_ipA

Returns the caller's public egress IP address (or caller's connecting IP in hosted mode) with geolocation, ASN/ISP, and datacenter/proxy detection. Use to verify which IP and country your traffic exits from, or to confirm a VPN/proxy is active. No parameters needed.

skuuy_list_proxiesA

Lists tested-live public proxies (HTTP/HTTPS/SOCKS4/SOCKS5) across 150+ countries, periodically health-checked for latency and anonymity. Filter by protocol, country, anonymity tier (L1 Elite = no forwarding headers, L2 Anonymous, L3 Transparent), and max latency. Each entry includes last_checked so you can judge freshness. Free public proxies are inherently unreliable — always implement retry/fallback.

skuuy_generate_totpA

Generates a time-based one-time password (RFC 6238 TOTP) from a base32 secret. PRIVACY: the secret is processed ephemerally in memory, never logged or stored. By sending the secret you opt in to server-side generation (the browser vault at 2fa.skuuy.com remains the zero-knowledge alternative). Compatible with Google Authenticator / Authy / Microsoft Authenticator secrets.

skuuy_create_temp_inboxA

Creates a disposable email inbox for sign-ups and verifications. Inbox self-destructs after TTL (default 30 minutes). Pair with skuuy_read_inbox to poll incoming mail and auto-extracted OTP codes.

skuuy_read_inboxA

Reads messages in a temp inbox created by skuuy_create_temp_inbox. Each message includes plain-text body and auto-extracted 4-8 digit OTP codes and action links (e.g. password-reset URLs) when detected. Poll this after triggering a verification email.

skuuy_resolve_dnsA

Resolves DNS records for a domain. Without 'locations', performs a single edge-resolver lookup. With 'locations', returns a propagation matrix across global edge PoPs (useful to verify DNS changes propagated worldwide). Supports A, AAAA, CNAME, MX, TXT, NS, SOA with DNSSEC validation status.

skuuy_check_portsA

Checks whether common service ports are open (TCP connect) on a host. ABUSE GUARD: only a fixed allowlist of common ports may be tested (22 SSH, 80 HTTP, 443 HTTPS, 3306 MySQL, 5432 Postgres, 6379 Redis, 51820 WireGuard). Arbitrary port ranges are rejected. Strictly rate-limited. Intended for diagnosing your own deployments and firewall/NAT traversal — not for scanning third parties.

skuuy_check_security_headersA

Audits a URL's security posture: security headers (HSTS, CSP, X-Frame-Options, Permissions-Policy, etc.), full redirect chain, and TLS certificate health (issuer, expiry, days remaining). Use for pre-deploy checks or auditing any site's hardening.

skuuy_read_urlA

Fetches any public URL and returns clean markdown (ads, cookie banners, nav chrome, and script tags stripped; JS-rendered pages rendered best-effort). Privacy: zero-log, the fetch is not associated with you. Honest scope: soft paywalls and JS pages handled best-effort; hard anti-bot challenges (interactive CAPTCHA) are not bypassed.

skuuy_create_webhook_binA

Creates an ephemeral webhook-catcher URL (bin.skuuy.com/w/) that records incoming HTTP requests with full headers and body. Point a third-party callback (Stripe, GitHub, your own API) at it while debugging, then inspect with skuuy_get_bin_requests. Auto-deleted after TTL.

skuuy_get_bin_requestsA

Lists HTTP requests captured by a webhook bin created with skuuy_create_webhook_bin: method, headers, query params, and body (truncated at 1 MB). Poll this after triggering the callback you are debugging (allow ~3-5 seconds for edge KV propagation).

skuuy_hash_encodeA

One-shot hashing/encoding utilities: SHA-256, SHA-512, Base64 encode/decode, UUID v4, and cryptographically random password generation. (MD5 included for legacy checksum verification only — do not use for security.)

skuuy_search_public_apisA

Use this when you need a free public REST API for a task — weather data, crypto prices, geocoding, news, AI models, etc. Searches Skuuy's live directory of 41 health-checked public APIs (no API key required for most). Returns the API name, what it does, its category, auth requirement, docs link, and a testable sample endpoint you can call immediately. Results are verified alive by continuous edge health probes.

skuuy_drop_fileA

Uploads or mirrors an inline file (base64 string or remote fetch URL) into an ephemeral public download URL with automatic TTL expiration. Use this when transferring files, charts, CSVs, logs, or binaries between agents, subagents, or to users without blowing token limits on inline data. Free tier: 25 drops/day.

skuuy_pasteA

Creates an ephemeral, cleanly-rendered shareable text or Markdown paste page with syntax highlighting and zero-script secure viewer. Use this when sharing code snippets, logs, prompt templates, or long markdown reports with users or other agents without formatting loss. Free tier: 25 pastes/day.

skuuy_rpcA

Sends a read-only JSON-RPC call through the Skuuy Private RPC Relay (rpc.skuuy.com) — zero-log, no API key, no signup. 12 EVM chains: eth, base, arb, op, bnb, polygon, avax, linea, bera, blast, scroll, zksync. Free tier: 2,500 calls/day/IP on the relay (quota is shared when called via the hosted MCP server). Write methods like eth_sendRawTransaction are rejected server-side.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 16 tools

Disambiguation4/5

Each tool targets a distinct capability (DNS, ports, headers, hashing, RPC, file/paste sharing, temp inbox, webhook bin, proxies, TOTP), and the create/read pairs (temp_inbox, webhook_bin) are naturally complementary rather than overlapping. The only mild overlap is between skuuy_drop_file and skuuy_paste, both being ephemeral content-sharing tools, but the file-vs-text distinction is stated clearly.

Naming Consistency4/5

All tools share the skuuy_ prefix and snake_case, with a mostly predictable verb_noun pattern (get_egress_ip, list_proxies, create_temp_inbox, read_inbox, resolve_dns, check_ports). A few names are terser and noun-like (paste, rpc, hash_encode) rather than pure verb_noun, a minor deviation from the dominant convention.

Tool Count4/5

16 tools is on the higher side, but the server is explicitly a multi-domain utility toolkit spanning networking, security, crypto, ephemeral sharing, and dev debugging, so each tool maps to a distinct capability rather than redundancy. Nothing feels padded, though it sits just above the comfortable mid-range.

Completeness4/5

Because the server spans many small utility domains, coverage is judged per-area: egress/proxy, DNS, port checks, security audit, URL fetch, hashing, temp inbox, webhook capture, file/paste sharing, API directory, and read-only RPC all have their core operation represented. Minor gaps exist (e.g., no delete/close for inbox or bin beyond TTL self-expiry, no write RPC by design), but these are intentional or trivially workaroundable.

Maintenance

ActivityMaintained
ResponsivenessNo issues