Developer · Remote MCP server
Cortex
Syslog receiver and MCP server for homelab log intelligence.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
tv.tootie/cortex- Version
- 3.9.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-07-11
- Updated
- 2026-07-11
- Publisher
- tv.tootie · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain tootie.tv · how
- Repository
- github.com/jmagar/cortex
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://cortex.tootie.tv/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/jmagar/cortex:v3.9.0 | - | stdio |
How to connect Cortex
Cortex is a remote MCP server: there is nothing to install. Its endpoint is https://cortex.tootie.tv/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/jmagar/cortex:v3.9.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e CORTEX_RECEIVER_HOST -e CORTEX_TOKEN -e CORTEX_RECEIVER_PORT ghcr.io/jmagar/cortex:v3.9.0. It reads these environment variables: CORTEX_RECEIVER_HOST (required), CORTEX_TOKEN (secret) and CORTEX_RECEIVER_PORT; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"cortex": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"CORTEX_RECEIVER_HOST",
"-e",
"CORTEX_TOKEN",
"-e",
"CORTEX_RECEIVER_PORT",
"ghcr.io/jmagar/cortex:v3.9.0"
],
"env": {
"CORTEX_RECEIVER_HOST": "<value>",
"CORTEX_TOKEN": "<secret>",
"CORTEX_RECEIVER_PORT": "<value>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from tv.tootie
| Server | Runs |
|---|---|
| Gotify MCPMCP server for self-hosted Gotify push notifications and message management. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| corpusAI Cloud PricingCloud, GPU and LLM token prices with index fixings. Pay per call over x402 or with a prepaid key. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| CorralSearch code and symbols across every clone in your Corral workspace. Zero network calls. | Local · stdio |
| corralctlSearch code and symbols across every clone in your corralctl workspace. Zero network calls. | Local · stdio |
| CortexLocal repo context for coding assistants with semantic search and graph relationships. | Local · stdio |
| Cortex GatewaySelf-hosted federated MCP gateway: one OAuth 2.1 MCP server in front of N apps, user-level scopes. | Remote & Local · HTTPLive check: sign-in required |
| Cortex RMCPSelf-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS. | Local · stdio |
| Cortex RMCPRust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation. | Local · stdio |
| CosmicManage Cosmic CMS content, media, object types, and AI generation from any MCP client. | Remote & Local · HTTP, stdio |