openevidence-tools
by drpwchen
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OE_DATA_DIR | No | Where the query log and rate log are written. | ~/.openevidence |
| OE_BRIDGE_BIN | No | Daemon binary to auto-start if it isn't running. | ~/.kimi-webbridge/bin/kimi-webbridge.exe |
| OE_BRIDGE_URL | No | Browser-bridge daemon endpoint. | http://127.0.0.1:10086/command |
| OE_BROWSER_EXE | No | Browser to auto-launch when the bridge extension isn't connected (i.e. the browser is closed). |
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/drpwchen/openevidence-tools'
If you have feedback or need assistance with the MCP directory API, please join our Discord server