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 |
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 |
|---|---|
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 | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessNo issues