Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PARANOID_PAYERNoPath to a Solana keypair file (the JSON the Solana CLI writes) whose wallet holds USDC. Needed only to buy questions. If you already have questions on paranoid.red, run `node connect.mjs` once and paste the connector code from the Keys tab instead.

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
askA

Ask one of PARANOID's AI models a question in private. The question goes with a fresh zero-knowledge key made on this computer, so the gateway cannot tell who asked or tie it to any other question. Spends the model's price in questions (see the models tool).

modelsA

List PARANOID's models and how many questions one message to each costs.

balanceA

How many questions this membership has left and the last day they can be used.

buyA

Buy a new membership with an x402 payment in USDC on Solana from the wallet in PARANOID_PAYER: 0.002 USDC a question plus a 0.30 USDC setup fee, 250 questions at least. A membership already here that still has questions is kept in a file beside the new one.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a clearly distinct role: buy is for purchasing a membership, ask for querying a model, balance for checking remaining questions, and models for listing prices. The only mild overlap is that buy and balance both deal with membership questions, but the descriptions keep them separable.

Naming Consistency3/5

Names mix verb-style (buy, ask) with noun-style (balance, models), and one is plural while the rest are singular. They remain short and readable, but there is no predictable verb_noun pattern an agent could generalize from.

Tool Count4/5

Four tools is a tight, well-scoped surface for a pay-per-question AI service, with each tool earning its place. It sits at the low end of the ideal range, but nothing feels redundant or missing at this scope.

Completeness4/5

The core lifecycle is covered: discover prices (models), purchase (buy), query (ask), and check remaining balance. Minor gaps exist around managing multiple memberships (e.g. listing or removing an existing membership kept beside a new one), but core workflows have no dead ends.

Maintenance

ActivityNo data
ResponsivenessOutdated data