Peer Review MCP Server
by raydollete
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | production switches the logger from pretty-printing to JSON. | |
| LOG_LEVEL | No | pino log level (fatal|error|warn|info|debug|trace). Logs go to stderr only. | info |
| PEER_TIMEOUT_MS | No | Per-source request timeout (includes retries). | 120000 |
| PEER_REVIEW_CONFIG | No | Path to the config file. | ./peer-review.config.json |
| PEER_CREDENTIAL_TTL_S | No | Cache TTL (seconds) for tokens minted via apiKeyCommand. | 3000 |
| PEER_MAX_OUTPUT_TOKENS | No | Max output tokens injected server-side into every peer call. | 8192 |
| PEER_REVIEW_DEADLINE_MS | No | Hard overall deadline for one peer_review call; on expiry in-flight calls are aborted and the accumulated (possibly degraded) result is returned. | 240000 |
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/raydollete/peer-review'
If you have feedback or need assistance with the MCP directory API, please join our Discord server