Monta Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Monta Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An MCP (Model Context Protocol) server that wraps the Monta Python SDK to provide LLM-friendly access to the Monta EV charging API.
This MCP server exposes the following tools for interacting with Monta's EV charging platform:
get_charge_points - List all available charging stations with paginationget_charge_point - Get detailed information about a specific charging stationget_charges - View charging history/sessions with filtering optionsstart_charge - Start a charging session at a specific charge pointstop_charge - Stop an active charging sessionget_personal_wallet - View wallet balance and payment informationget_wallet_transactions - Get transaction history with filteringuv package manager (recommended) or pipgit clone <repository-url>
cd monta-mcp
uv syncgit clone <repository-url>
cd monta-mcp
pip install -e .The server requires Monta API credentials set as environment variables:
export MONTA_CLIENT_ID="your_client_id"
export MONTA_CLIENT_SECRET="your_client_secret"Visit Monta Public API Portal and follow the guide
The server can be run directly:
# Using the installed script (default log: ./monta-mcp.log)
monta-mcp
# With custom log file location
monta-mcp --log-file /path/to/custom.log
# With custom log level
monta-mcp --log-level DEBUG
# Or using Python module
python -m monta_mcpCommand-line Options:
--log-file PATH - Path to log file (default: ./monta-mcp.log)--log-level LEVEL - Logging level: DEBUG, INFO, WARNING, ERROR (default: INFO)You can test the server using the MCP Inspector tool:
npx @modelcontextprotocol/inspector monta-mcpThis will open a web interface where you can:
Add this configuration to your Claude Desktop config file:
MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"monta": {
"command": "monta-mcp",
"env": {
"MONTA_CLIENT_ID": "your_client_id",
"MONTA_CLIENT_SECRET": "your_client_secret"
}
}
}
}Or if using uv:
{
"mcpServers": {
"monta": {
"command": "uv",
"args": ["run", "monta-mcp"],
"env": {
"MONTA_CLIENT_ID": "your_client_id",
"MONTA_CLIENT_SECRET": "your_client_secret"
}
}
}
}With custom log location:
{
"mcpServers": {
"monta": {
"command": "uv",
"args": ["run", "monta-mcp", "--log-file", "/Users/you/logs/monta.log"],
"env": {
"MONTA_CLIENT_ID": "your_client_id",
"MONTA_CLIENT_SECRET": "your_client_secret"
}
}
}
}After adding the configuration, restart Claude Desktop. The Monta tools will be available in your conversations.
Once configured, you can ask Claude things like:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.