Jitsu is an open-source event data platform that collects activity from websites, apps, and servers and sends it to data warehouses and other tools. Data teams use it as a self-hosted or hosted alternative to Segment for building real-time data pipelines. The catalogue includes add-ons for working with Jitsu.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/jitsucom/jitsuWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/jitsucom/jitsu/mcp)<a href="https://agentmods.dev/mcp/jitsucom/jitsu/mcp"><img src="https://agentmods.dev/badge/mcp/jitsucom/jitsu/mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/jitsucom/jitsu/mcp"><img src="https://agentmods.dev/badge/mcp/jitsucom/jitsu/mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "mcp": { "url": "https://use.jitsu.com/mcp", "type": "streamable-http" } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A 06eb90a07669
mcp is an MCP server published in the GitHub repository jitsucom/jitsu (5,108 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
gopls
MCP server "gopls" as configured in fredrikaverpil/dotfiles. Launched with gopls mcp.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
manifold
MCP server "manifold" as configured in nonchan7720/manifold. Runs in Docker (ghcr.io/nonchan7720/manifold:v1.9.0). Needs 2 environment variables to run.
tela
Self-hostable team wiki; agents read & write it via MCP; Atlas turns your repo into a cited wiki. Runs locally from the tela-mcp npm package. Needs 2 environment variables to run.
gha-doctor
MCP server "gha-doctor" as configured in linnea-bakshi/gha-doctor. Runs in Docker (ghcr.io/linnea-bakshi/gha-doctor:0.66.0). Needs 1 environment variable to run.
mcp-clickhouse
ClickHouse query & management for AI agents — SQL-classified read/write/destructive gating. Runs locally from the @dockndevai/mcp-clickhouse npm package. Needs 4 environment variables to run.