Open Archives MCP Server
by coret
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port | 3001 |
| NODE_ENV | No | Set to 'production' for JSON logs | |
| CACHE_TTL | No | Fallback cache TTL in seconds | 3600 |
| LOG_LEVEL | No | Log level: trace, debug, info, warn, error, fatal | info |
| REDIS_URL | No | Redis connection URL (db 5) | redis://localhost:6379/5 |
| OPENAPI_PATH | No | Path or URL to OpenAPI spec | ../api/openapi.yaml |
| UPSTREAM_BASE | No | Upstream API base URL | https://api.openarchieven.nl/1.1 |
| RATE_LIMIT_RPS | No | Upstream requests per second | 4 |
| ALLOWED_ORIGINS | No | Extra Origin headers allowed on the MCP endpoint (comma-separated) |
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/coret/openarchieven-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server