super-log Cloud is answering right now. Last checked moments ago. Last commit 1 Oct 2026.
Read your team's hosted journal from an AI agent: every machine's streams, in hub order.
We read the source, 1 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.
child = spawn(command[0], command.slice(1), { stdio: ['inherit', 'pipe', 'pipe'] });
out = subprocess.run(
if (std::FILE* p = ::popen(cmd.c_str(), "r")) {
import { createReadStream, existsSync, readdirSync, readFileSync, statSync } from 'node:fs';
await fetch(`https://api.telegram.org/bot${tgToken}/sendMessage`, {
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 0 min ago.
claude mcp add super-log-cloud --transport http https://api.super-log.com/mcp
https://api.super-log.com/mcp
[mcp_servers.super-log-cloud]
url = "https://api.super-log.com/mcp"
{
"mcpServers": {
"super-log-cloud": {
"url": "https://api.super-log.com/mcp"
}
}
}
{
"servers": {
"super-log-cloud": {
"type": "http",
"url": "https://api.super-log.com/mcp"
}
}
}
This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://api.super-log.com/mcp | streamable-http | needs key | 39 ms | 0 min ago |
Query your local super-log bench from an AI agent - read-only log tools over the hub.
Your agents' personal cloud database: records and logs every agent you connect can save and read.
AI trading journal: your agent logs trades from chart screenshots and checks your own rules.
Host apps in the EU from your assistant: App Store, Docker, GitHub, databases, logs.
One number per AI agent: route MCP calls to any agent, every call sealed in an on-chain log.
Mine your AI coding session logs into a you.md profile with dated receipts, for an agent to read.
Calorie and macro diary your AI fills in: log meals from text or photos, refine later, track goals.
Read a project's prompts, logs and agents, and send new work to the agent on your own machines.
Answers built from our own checks of this server.