Jeprum
The live control room for AI agents — see everything, set rules, stop anything.
What is Jeprum?
Jeprum is an open-source SDK that monitors and governs AI agents in real-time. It intercepts MCP tool calls, enforces guardrails (spending limits, tool blocking, rate limits), provides a kill switch, and ships telemetry to a cloud dashboard. Install in one command, integrate in 5 lines of code.
Quick Start
pip install jeprum
from jeprum import Jeprum
jp = Jeprum(api_key="jp_live_xxx", transport_mode="cloud")
monitored = jp.monitor(my_mcp_session, rules={
"max_spend_per_day": 10.0,
"blocked_tools": ["delete_*"]
})
result = await monitored.call_tool("search", {"query": "test"})
Features
- Real-time monitoring — every tool call captured with duration, cost, and I/O
- Guardrails — spending limits, tool blocking, rate limiting, alert patterns
- Kill switch — stop any agent remotely from the dashboard
- Cloud dashboard — live event timeline, cost tracking, agent management
- MCP-native — wraps ClientSession with zero agent code changes
- Non-blocking — telemetry shipping never slows your agent
- Open source — Apache 2.0
How It Works
Agent → Jeprum SDK (intercept + guardrails) → MCP Server → Tool
↓
Jeprum Cloud (dashboard, kill switch, audit trail)
The SDK wraps your MCP session. Every call_tool() is intercepted: guardrails are checked synchronously (before execution), events are shipped asynchronously (after execution). Your agent code doesn't change.
Configuration
rules = {
"max_spend_per_day": 10.0,
"blocked_tools": ["delete_*", "drop_*"],
"alert_on": ["payment.*", "transfer.*"],
"rate_limit": {"max_events": 100, "period_seconds": 60}
}
Cloud Dashboard
Sign up at jeprum.com to get an API key. The dashboard provides:
- Live event timeline with guardrail status
- Agent list with cost and status tracking
- Kill / pause / resume controls
- Cost-over-time charts
Documentation
Contributing
See CONTRIBUTING.md for development setup and guidelines.
License
Apache 2.0 — see LICENSE for details.
Built by Jithendra Siddartha, MS CS @ NYU Tandon.
Metadata
Release files for jeprum 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| jeprum-0.1.0.tar.gz | 66.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jeprum-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 85.0 kB
Release files / jeprum-0.1.0.tar.gz
| Download URL | jeprum-0.1.0.tar.gz |
|---|---|
| Size | 66.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a35793e7c60a0b7add2c7f03f34e6d11c4dcda4e39ccefc3a8400d2e60a64bf5
|
|
BLAKE2b-256 checksum How to use checksums |
88967fa9d30fb525ad4766ff797093a381c0fd4e37da1360316cfdf88243e639
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.10 {"installer":{"name":"uv","version":"0.10.10","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / jeprum-0.1.0-py3-none-any.whl
| Download URL | jeprum-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b91c8c21b16461fa89d49d301f9aadccc60b7c870e3d31302e21ad81bb82392
|
|
BLAKE2b-256 checksum How to use checksums |
6f62e04f609beec84c31cb9ef8520bd6b52dcc6f81b9f69262c77aada7474d88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.10 {"installer":{"name":"uv","version":"0.10.10","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for jeprum 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.