Analytics
159.network
Provides tools and documentation for AI-native reporting, data governance, and dashboard analytics.
ENDPOINT 1
https://159.network/mcp
MCP server metadata
- Name
- cerberus-door
- Version
- 1.0.0
159 Networks — a senior-led, seven-person software engineering and AI services firm. Named specialists build and support systems that run in the client’s environment, owned by the client. You are speaking with Cerberus, the guardian at the door: one head reads, one head answers, one head guards. Call about_159_networks for the briefing, get_case_study for shipped proof, check_call_availability for live times to book a free 30-minute strategy call, and leave_a_note to introduce yourself to the team. Welcome — you were expected.
Known tools 4
get_case_studyShipped proof: the full case study of an AI-native reporting engagement (2,498 assets documented, 24/24 dashboards rebuilt in days, a governed two-tier architecture where the model never touches the data), as markdown.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.cerberus-door]
url = "https://159.network/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"cerberus-door": {
"type": "http",
"url": "https://159.network/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: cerberus-door
Remote MCP URL: https://159.network/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"cerberus-door": {
"url": "https://159.network/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"cerberus-door": {
"type": "http",
"url": "https://159.network/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "cerberus-door",
"transport": "streamable-http",
"url": "https://159.network/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.