random-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address for http/sse | 127.0.0.1 |
| PORT | No | Bind port for http/sse | 8000 |
| APP_NAME | No | Name reported by server_info | random-mcp-server |
| RANDOM_SEED | No | Fixed seed for reproducible pools | |
| RANDOM_COUNT | No | Records generated per kind at start-up | 25 |
| MCP_TRANSPORT | No | Transport type: stdio, http, or sse | stdio |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Health/status of the server (the REST server's |
| list_recordsA | Return the seeded pool of records for Pass |
| get_recordA | Return a single record from |
| count_recordsA | Return the number of records available for |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: counting records, retrieving by ID, listing with options, and server health. No ambiguity among them.
Most tools follow verb_noun pattern (count_records, get_record, list_records), but server_info deviates as a noun_verb? phrase, causing minor inconsistency.
Four tools is well-scoped for a simple read-only data server, each tool earns its place without unnecessary complexity.
The server covers basic read operations (list, get, count) but lacks create, update, delete functionalities, leaving notable gaps for a full data API.