Random.org MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAX_RETRIES | No | Maximum number of retries | 3 |
| RETRY_DELAY_MS | No | Delay between retries | 1000 |
| RANDOM_ORG_API_KEY | Yes | Your api.random.org API key | |
| REQUEST_TIMEOUT_MS | No | Request timeout in milliseconds | 10000 |
| RATE_LIMIT_BURST_SIZE | No | Burst size for rate limiting | 5 |
| RATE_LIMIT_REQUESTS_PER_SECOND | No | Rate limiting | 1 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generateIntegersC | Generate true random integers within a specified range |
| generateIntegerSequencesC | Generate sequences of true random integers |
| generateDecimalFractionsB | Generate true random decimal fractions between 0 and 1 |
| generateGaussiansC | Generate true random numbers from a Gaussian distribution |
| generateStringsC | Generate true random strings |
| generateUUIDsB | Generate true random UUIDs (version 4) |
| generateBlobsB | Generate true random binary data |
| getUsageB | Get API usage statistics |
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 8 tools
Every tool has a clearly distinct purpose focused on generating different types of random data or checking usage. The descriptions specify unique data types (blobs, decimal fractions, Gaussians, integers, sequences, strings, UUIDs) with no overlap in functionality. An agent can easily distinguish between them based on the specific random generation needed.
All tool names follow a consistent verb_noun pattern with 'generate' or 'get' as the verb and a descriptive noun (e.g., generateIntegers, generateUUIDs, getUsage). The naming is uniform across all tools, using camelCase consistently without any deviations or mixed conventions.
With 8 tools, this server is well-scoped for generating various types of random data and checking usage. Each tool serves a specific and necessary function in the domain of random number generation, covering common use cases without being excessive or lacking. The count is appropriate for the server's purpose.
The tool set provides complete coverage for the domain of random data generation, including integers, fractions, Gaussians, strings, UUIDs, blobs, sequences, and usage statistics. There are no obvious gaps; it supports a wide range of random generation needs and includes a utility tool for monitoring API usage, ensuring no dead ends for agents.