mcp-nexus
by ykq007
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | The host address for the server to listen on. | 0.0.0.0 |
| PORT | No | The port for the server to listen on. | 8787 |
| DATABASE_URL | No | Connection string for the database. For local setups, a file-based SQLite DB is recommended. | file:./tavily_bridge.db |
| BRAVE_API_KEY | No | A Brave Search API key. If set, this single key will be used. For multi-key support, add keys via the Admin UI. | |
| BRAVE_MAX_QPS | No | Max requests per second to the Brave API to stay within rate limits. | 1 |
| BRAVE_OVERFLOW | No | Behavior when the request queue is full: fallback_to_tavily, queue, or error. | fallback_to_tavily |
| ADMIN_API_TOKEN | No | Bearer token for accessing the Admin API. | (generated in example) |
| MCP_COOLDOWN_MS | No | Cooldown period in milliseconds for an upstream API key after a failure. | 60000 |
| MCP_MAX_RETRIES | No | Maximum number of retries for failed upstream requests. | 2 |
| ENABLE_QUERY_AUTH | No | If true, also allow passing the MCP client token via query string instead of Authorization header. | false |
| BRAVE_MAX_QUEUE_MS | No | Max time a request can wait in the queue before failing or falling back to Tavily. | 30000 |
| SEARCH_SOURCE_MODE | No | Defines the search behavior: tavily_only, brave_only, combined, or brave_prefer_tavily_fallback. | brave_prefer_tavily_fallback |
| BRAVE_HTTP_TIMEOUT_MS | No | Per-request HTTP timeout for the Brave API. | 20000 |
| BRAVE_MIN_INTERVAL_MS | No | Overrides BRAVE_MAX_QPS with a fixed minimum interval between requests. | |
| KEY_ENCRYPTION_SECRET | No | A 32-byte (256-bit) secret key used for encrypting and decrypting upstream API keys stored in the database. | (generated in example) |
| TAVILY_USAGE_LOG_MODE | No | Log level for Tavily tool usage: none, hash, preview, or full. | preview |
| TAVILY_USAGE_HASH_SECRET | No | Optional secret for creating a keyed HMAC-SHA256 hash of queries instead of a plain SHA256. | |
| TAVILY_USAGE_SAMPLE_RATE | No | Optional sampling rate (0.0 to 1.0) for logging usage events. | |
| MCP_RATE_LIMIT_PER_MINUTE | No | Max requests per minute per client token. | 60 |
| TAVILY_CREDITS_COOLDOWN_MS | No | Cooldown duration for a key that has fallen below the minimum credit threshold. | 300000 |
| TAVILY_CREDITS_CACHE_TTL_MS | No | Duration to cache Tavily credit information before it's considered stale. | 60000 |
| TAVILY_USAGE_RETENTION_DAYS | No | Optional retention period for usage logs. | |
| TAVILY_CREDITS_MIN_REMAINING | No | Credit threshold at which a Tavily key will be automatically put into cooldown status. | 1 |
| TAVILY_KEY_SELECTION_STRATEGY | No | Strategy for picking an upstream Tavily key when multiple are active: round_robin or random. | round_robin |
| TAVILY_CREDITS_REFRESH_LOCK_MS | No | Lock duration to prevent concurrent credit refreshes for the same key. | 15000 |
| MCP_GLOBAL_RATE_LIMIT_PER_MINUTE | No | Max requests per minute across all clients. | 600 |
| TAVILY_USAGE_CLEANUP_PROBABILITY | No | The probability (0.0 to 1.0) that a cleanup of old usage logs is triggered on a new usage event. | 0.001 |
| TAVILY_CREDITS_REFRESH_TIMEOUT_MS | No | Timeout for the upstream Tavily credits API request. | 5000 |
| ADMIN_KEY_REVEAL_RATE_LIMIT_PER_MINUTE | No | Max key reveal attempts per minute in the Admin UI. | 20 |
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 | |
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/ykq007/mcp-nexus'
If you have feedback or need assistance with the MCP directory API, please join our Discord server