Cortex is answering right now. Last checked 11 min ago. Last commit 1 Oct 2026.
Syslog receiver and MCP server for homelab log intelligence.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
if (!fs.existsSync(binary)) { const installer = path.resolve(__dirname, "..", "scripts", "install.js"); const install = spawnSync(process.execPath, [installer], { stdio: "inherit" }); if (install.status !== 0) fail("binary is not installed; postinstall may have failed"); }
DO UPDATE SET count_in_window = count_in_window + excluded.count_in_window",
source: Some("/var/run/docker.sock".to_string()),
anyhow::bail!("no hosts found in ~/.ssh/config");
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.
claude mcp add cortex --transport http https://cortex.tootie.tv/mcp
https://cortex.tootie.tv/mcp
[mcp_servers.cortex]
url = "https://cortex.tootie.tv/mcp"
{
"mcpServers": {
"cortex": {
"url": "https://cortex.tootie.tv/mcp"
}
}
}
{
"servers": {
"cortex": {
"type": "http",
"url": "https://cortex.tootie.tv/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://cortex.tootie.tv/mcp | streamable-http | needs auth | 81 ms | 11 min ago |
Syslog receiver and MCP server for homelab log intelligence.
Self-hosted homelab log intelligence over MCP, CLI, and REST with SQLite/FTS.
Rust MCP server for homelab logs, syslog, Docker logs, FTS search, and AI transcript correlation.
Remote MCP server for hotel rate monitoring, parity checks, and pricing intelligence via Apify.
ThousandEyes MCP Server for network intelligence: outages, anomalies, alerts, events, and tests.
MCP server for Yandex Metrika API — counters, goals, reports, segments, logs
MCP server for Cronometer — food logs, macros, fasting, biometrics, and recurring foods
Persistent memory for AI agents — log and recall conversation context over MCP.
Answers built from our own checks of this server.