RIGForge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RIGFORGE_MCP_TOKEN | No | Bearer token for authenticating HTTP MCP transport requests. | |
| RIGFORGE_SIGNING_KEY | No | The HMAC-SHA256 signing key used to seal and verify proof packets. Either this or RIGFORGE_SIGNING_KEY_FILE is required. | |
| RIGFORGE_MCP_TOKEN_FILE | No | Path to a file containing the bearer token. | |
| RIGFORGE_SIGNING_KEY_FILE | No | Path to a file containing the HMAC-SHA256 signing key. |
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
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/mrodgersjs-web/rigforge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server