Radiant MCP Server
Officialby Radiant-Core
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Bind address for the REST and SSE servers (loopback by default) | 127.0.0.1 |
| PORT | No | REST API port (also the SSE fallback port) | 3080 |
| SSE_PORT | No | SSE server port | 3090 |
| RXDC_PATH | No | Path to the rxdc RadiantScript compiler binary, used by radiant_compile_script | (auto-detected) |
| CORS_ORIGIN | No | CORS allowed origin (REST) | * |
| ELECTRUMX_SSL | No | Use TLS for a raw socket (ignored when ELECTRUMX_WSS=true) | true |
| ELECTRUMX_WSS | No | Connect over secure WebSocket (wss://host, port 443). Firewall-proof and works on mobile/corporate networks; requires Node 22+. Set false to use a raw TCP/SSL socket instead. | true |
| ELECTRUMX_HOST | No | ElectrumX server hostname | electrumx.radiantcore.org |
| ELECTRUMX_PORT | No | ElectrumX server port | 443 (wss) / 50012 (raw) |
| RADIANT_NETWORK | No | Network: mainnet or testnet | mainnet |
| RADIANT_API_TOKEN | No | Bearer token required for key-handling REST endpoints. When unset, those endpoints are loopback-only | (unset) |
| RADIANT_TEST_MODE | No | When set (and not 0/false), blocks real transaction broadcasts | (unset) |
| RADIANT_KEYRING_FILE | No | Path to the server-side keyring (must be 0600 on POSIX) | ~/.radiant-mcp/keyring.json |
| RADIANT_RESPONSE_FORMAT | No | Value formatting in responses: satoshis, rxd, or both (satoshis ~halves token cost on balance/UTXO-heavy calls) | both |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Radiant-Core/radiant-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server