ExoSense MCP Server
by diodechain
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port | 9000 |
| LOG_LEVEL | No | Python logging level (default: INFO). Use 'WARNING' in production to cut log I/O overhead. | INFO |
| LISTEN_HOST | No | Bind address for the HTTP MCP server | 127.0.0.1 |
| DIODE_CLIENT | No | Omit or 'embedded' (default) — run Diode in this process. Set to 'container' only when a sidecar publishes Diode. | embedded |
| HTTP_STREAMING | No | Set to 'Private' for backward compatibility (optional) | |
| EXOSENSE_ORIGIN | No | Host name of the solution being referenced | https://exosense.com |
| EXOSENSE_API_URL | No | GraphQL endpoint for ExoSense | https://api.exosense.com |
| DIODE_JOIN_ADDRESS | No | Diode join address for private networks (optional) | |
| EXOSENSE_AUTH_TOKEN | No | Default authentication token (optional, required for private mode) |
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/diodechain/exosense-pymcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server