Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"muntu": {
"url": "https://api.muntuai.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:MUNTU_AGENT_KEY}"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
This repository contains the public documentation, manifest, and reference clients for the live MuntuAI MCP server. The runnable server implementation lives in the main Muntu backend.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'requests' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Requests has Insecure Temp File Reuse in its extract_zipped_paths() utility function
### Impact The `requests.utils.extract_zipped_paths()` utility function uses a predictable filename when extracting files from zip archives into the system temporary directory. If the target file already exists, it is reused without validation. A local attacker with write access to the temp directory could pre-create a malicious file that would be loaded in place of the legitimate one. ### Affected usages **Standard usage of the Requests library is not affected by this vulnerability.** Only app
Requests vulnerable to .netrc credentials leak via malicious URLs
### Impact Due to a URL parsing issue, Requests releases prior to 2.32.4 may leak .netrc credentials to third parties for specific maliciously-crafted URLs. ### Workarounds For older versions of Requests, use of the .netrc file can be disabled with `trust_env=False` on your Requests Session ([docs](https://requests.readthedocs.io/en/latest/api/#requests.Session.trust_env)). ### References https://github.com/psf/requests/pull/6965 https://seclists.org/fulldisclosure/2025/Jun/2
Requests `Session` object does not verify requests after making first request with verify=False
When using a `requests.Session`, if the first request to a given origin is made with `verify=False`, TLS certificate verification may remain disabled for all subsequent requests to that origin, even if `verify=True` is explicitly specified later. This occurs because the underlying connection is reused from the session's connection pool, causing the initial TLS verification setting to persist for the lifetime of the pooled connection. As a result, applications may unintentionally send requests w
PYSEC-2023-74
Requests is a HTTP library. Since Requests 2.3.0, Requests has been leaking Proxy-Authorization headers to destination servers when redirected to an HTTPS endpoint. This is a product of how we use `rebuild_proxies` to reattach the `Proxy-Authorization` header to requests. For HTTP connections sent through the tunnel, the proxy will identify the header in the request itself and remove it prior to forwarding to the destination server. However when sent over HTTPS, the `Proxy-Authorization` header
PYSEC-2018-28
The Requests package before 2.20.0 for Python sends an HTTP Authorization header to an http URI upon receiving a same-hostname https-to-http redirect, which makes it easier for remote attackers to discover credentials by sniffing the network.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in marketing
DataForSEO API modelcontextprotocol server
MCP server for the PostFast API — schedule and manage social media posts via AI tools
Claude Code plugin: 115 commands, 25 agents, 64 scripts, 67 MCP servers, 143 reference files. Eval/QA layer (hallucination detection, claim verification, A+ through F grading). Multilingual (Sarvam AI, DeepL, Google Cloud Translation). Full execution with approval workflow.
A free SEO research tool using Model Context Protocol (MCP) powered by Ahrefs data. Get backlink analysis, keyword research, traffic estimation, and more — directly in your AI-powered IDE.
MCP Security Weekly
Get CVE alerts and security updates for io.github.design-smith/muntuai-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
This repository contains the public documentation, manifest, and reference clients for the live MuntuAI MCP server. The runnable server implementation lives in the main Muntu backend.
The official Model Context Protocol (MCP) server for MuntuAI — giving AI agents programmatic access to email outreach campaigns, lead management, domain infrastructure, and real-time workspace events.
MuntuAI is an AI-native email outreach platform. This MCP server lets external agents (Claude, Cursor, custom scripts) connect to a MuntuAI workspace and perform actions: create campaigns, import leads, verify domains, send emails, and subscribe to webhook events — all through a standard MCP interface over HTTP.
Protocol: Model Context Protocol over HTTP (JSON-RPC 2.0)
Transport: Streamable HTTP (text/event-stream or application/json)
Server protocol revision: 2025-03-26
Server URL: https://api.muntuai.com/api/mcp
Log in to app.muntuai.com, go to Settings → Agent Keys, and create a key. Choose the autonomy level that matches what your agent needs:
| Level | What it can do |
|---|---|
observer | Read anything — campaigns, leads, domains, senders, events |
copilot | Read + create and modify — campaigns, domains, senders, leads, webhooks |
autonomous | Everything above + pause, resume, delete |
You will see the raw key once: mnt_<keyId>.<secret>. Copy it immediately.
Security note: store the raw agent key in an environment variable or secret manager. Do not commit it to source control or paste it into shared files.
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"muntu": {
"url": "https://api.muntuai.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:MUNTU_AGENT_KEY}"
}
}
}
}
Cursor (.cursor/mcp.json or Settings → MCP):
{
"mcpServers": {
"muntu": {
"url": "https://api.muntuai.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:MUNTU_AGENT_KEY}"
}
}
}
}
Python:
pip install requests
export MUNTU_AGENT_KEY="mnt_YOUR_KEY_HERE"
python clients/python/muntu_mcp_client.py list-campaigns
Recommended:
export MUNTU_SESSION_ID="$(uuidgen)"
Muntu uses the optional MUNTU_SESSION_ID to group requests into one logical MCP session for session-scoped safety controls and budgeting.
Once connected, ask your agent:
"List all campaigns in my MuntuAI workspace"
The agent will call resources/read on muntu://campaigns/{workspaceId} and return the campaign list.
Or via Python CLI:
python clients/python/muntu_mcp_client.py list-campaigns
python clients/python/muntu_mcp_client.py list-domains
python clients/python/muntu_mcp_client.py list-emails
| Resource | URI | Description |
|---|---|---|
| workspace | muntu://workspace/{id} | Profile, policy, infrastructure counts |
| domains | muntu://domains/{id}?cursor=0&limit=50 | All domains with DNS and verification state |
| senders | muntu://senders/{id}?cursor=0&limit=50 | All email accounts with status |
| campaigns | muntu://campaigns/{id}?cursor=0&limit=20 | Unified campaign list |
| campaign-plans | muntu://campaign-plans/{id}?cursor=0&limit=20 | Draft review queue |
| events | muntu://events/{id}?cursor=0 | Recent system events (filterable) |
Grouped by domain — see tools/README.md for the full index.