Lobu is answering right now. Last checked 5 min ago. Last commit 22 Sep 2026.
Shared, permission-aware company context for AI agents, with provenance, approvals and audit.
What the code does
We read the source, 9 h ago · rules 3dff92dd89df
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.
execFileSync(cmd, ["--version"], { stdio: "ignore", env: process.env });
const rel = path.join('dist-mcp-apps', appDir, relPath);
return `Update ${entityLabel} ${fieldNoun}: ${fieldList}`;
USER 0
import { existsSync, readdirSync, readFileSync, statSync } from "node:fs";
: "https://api.telegram.org";
Object.assign(process.env, runtime.env);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
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.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
claude mcp add lobu --transport http https://lobu.ai/mcp{
"mcpServers": {
"lobu": {
"url": "https://lobu.ai/mcp"
}
}
}[mcp_servers.lobu]
url = "https://lobu.ai/mcp"{
"mcpServers": {
"lobu": {
"url": "https://lobu.ai/mcp"
}
}
}{
"mcpServers": {
"lobu": {
"url": "https://lobu.ai/mcp"
}
}
}This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://lobu.ai/mcp | streamable-http | sign-in | 676 ms | 5 min ago |
Alternatives to Lobu
same job, measured the same wayGovernance middleware for AI agents: permission gates, approvals, compliance scanning, audit ledger.
Governance runtime for AI agents with signed provenance, compliance audits, and OSINT.
Christian source evidence for AI agents, with provenance, tradition coverage, and citation checks.
Governed execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals.
Provenance-aware memory for AI agents: quarantine, abstention gate, supersession-with-history.
Runtime permission, approval, and audit layer for AI agent tool execution.
AI agent governance with resolved business context, current decisions, provenance, and supersession.
OAuth 2.1 short-link tools for AI agents with scoped tokens, approvals, audit logs, and revocation.
Lobu — questions
Answers built from our own checks of this server.