SentinelX Core MCP
by pensados
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_DIR | No | Directory for log files (e.g., /var/log/sentinelx-mcp). | |
| LOG_FILE | No | Path to the log file (e.g., /var/log/sentinelx-mcp/sentinelx-core-mcp.log). | |
| MCP_PORT | No | The port for the MCP server to listen on (e.g., 8098 or 8099). | |
| MCP_TOKEN | No | Optional token for MCP server authentication. | |
| AUTH_DEBUG | No | Enable debug logging for authentication (e.g., false). | |
| OIDC_ISSUER | Yes | The OIDC issuer URL for validating external MCP bearer tokens (e.g., https://auth.example.com/realms/sentinelx). | |
| RESOURCE_URL | No | The resource URL for the MCP server (e.g., https://sentinelx.example.com). | |
| OIDC_JWKS_URI | Yes | The JWKS URI for OIDC token validation (e.g., https://auth.example.com/realms/sentinelx/protocol/openid-connect/certs). | |
| SENTINELX_URL | Yes | The URL of the upstream SentinelX Core instance (e.g., http://127.0.0.1:8091). | |
| SENTINELX_TOKEN | Yes | The bearer token for authenticating with the upstream SentinelX Core API. | |
| OIDC_EXPECTED_AUDIENCE | No | Optional expected audience for OIDC token validation. |
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
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/pensados/sentinelx-core-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server