Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Spot AI MCP (Unofficial)

PYPI · SPOT-AI-MCP · SCANNED SEP 21

Unofficial community MCP server for the Spot AI camera and video-intelligence REST API. Read-only.

Available components

−12 this week 64 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 654 tokens (~65/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 90% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Spot AI MCP (Unofficial) server?

Spot AI MCP (Unofficial) runs locally as a PyPI package, launched with uvx spot-ai-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · spot-ai-mcp

# add to Claude Code
claude mcp add phil-bryant-spot-ai-mcp -- uvx spot-ai-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "phil-bryant-spot-ai-mcp": {
      "command": "uvx",
      "args": [
        "spot-ai-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "phil-bryant-spot-ai-mcp": {
      "command": "uvx",
      "args": [
        "spot-ai-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add phil-bryant-spot-ai-mcp -- uvx spot-ai-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "phil-bryant-spot-ai-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "spot-ai-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add phil-bryant-spot-ai-mcp --command uvx --arg spot-ai-mcp
# ~/.hermes/config.yaml
mcp_servers:
  phil-bryant-spot-ai-mcp:
    command: "uvx"
    args: ["spot-ai-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "phil-bryant-spot-ai-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "spot-ai-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add phil-bryant-spot-ai-mcp -t stdio -c uvx -a spot-ai-mcp
// mcp.json
{
  "mcpServers": {
    "phil-bryant-spot-ai-mcp": {
      "command": "uvx",
      "args": [
        "spot-ai-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −14
    • Malware scan: pass → unverified security
  • 16 Sept 26 +15
    • Malware scan: unverified → pass security
  • 15 Sept 26 −14
    • Malware scan: pass → unverified security
  • 14 Sept 26 +15
    • Malware scan: unverified → pass security
  • 13 Sept 26 −14
    • Malware scan: pass → unverified security
  • 12 Sept 26 +15
    • Malware scan: unverified → pass security
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed pypi/spot-ai-mcp@0.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~654 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_camera ~27

Get details for a single camera by id.

NameTypeReqDescription
camera_idnumberyesCamera id

No output schema declared.

No examples provided.

get_camera_count ~19

Get the number of enabled cameras in the organization.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_intelligence ~179

Get intelligence events and summary for a camera: counting, idle, or presence of people, vehicles, or forklifts over a date range.

NameTypeReqDescription
camera_idnumberyesCamera id
end_datestringyesRFC3339 end of the date range
end_timestringOptional daily window end, HH:mm:ss (default 23:59:59)
entitystringyes
metricstringyes
start_datestringyesRFC3339 start of the date range, e.g. 2026-08-01T00:00:00Z
start_timestringOptional daily window start, HH:mm:ss (default 00:00:00)
thresholdnumberMinimum entities in frame to count as an event (default 1)

No output schema declared.

No examples provided.

get_live_stream_urls ~59

Get a URL to a live stream of up to 4 cameras. Generates a viewing URL for the authenticated caller; modifies nothing.

NameTypeReqDescription
camera_idsarrayyesIds of the cameras to create live urls for (1 to 4)

No output schema declared.

No examples provided.

get_lpr_report ~63

Get the license-plate-recognition report for an LPR-enabled camera.

NameTypeReqDescription
camera_idnumberyesCamera id (must be LPR enabled)
queryobjectOptional extra query parameters (e.g. date filters) passed through verbatim

No output schema declared.

No examples provided.

get_zones ~27

List the zones defined on a camera.

NameTypeReqDescription
camera_idnumberyesCamera id

No output schema declared.

No examples provided.

list_appliances ~56

List appliances (Intelligent Video Recorders) for the org. Paginated via cursor.

NameTypeReqDescription
cursorstringPagination cursor from a previous response's 'next' field
limitnumberMax results per page

No output schema declared.

No examples provided.

list_cameras ~63

List cameras for the org (id, name, status, location, IP, MAC, appliance). Paginated via cursor.

NameTypeReqDescription
cursorstringPagination cursor from a previous response's 'next' field
limitnumberMax results per page

No output schema declared.

No examples provided.

list_locations ~72

List locations (id and name) the API key has access to. Paginated: pass the response's 'next' value back as 'cursor' until it is null.

NameTypeReqDescription
cursorstringPagination cursor from a previous response's 'next' field
limitnumberMax results per page

No output schema declared.

No examples provided.

spot_api_get ~89

Escape hatch: perform a GET against any documented Spot AI API path (https://developers.spot.ai/llms.txt lists them). Example path: /v1/integrations. Only GET is supported; this server is read-only.

NameTypeReqDescription
pathstringyesAPI path starting with /v1/ or /v2/
queryobjectQuery parameters as a flat object

No output schema declared.

No examples provided.

Common questions

What is the Spot AI MCP (Unofficial) server?

Spot AI MCP (Unofficial) is listed in the public MCP registry as io.github.phil-bryant/spot-ai-mcp. Unofficial community MCP server for the Spot AI camera and video-intelligence REST API. Read-only. This page covers its PyPI package (spot-ai-mcp).

Is the Spot AI MCP (Unofficial) server safe to use?

Spot AI MCP (Unofficial) scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Spot AI MCP (Unofficial) server expose?

Spot AI MCP (Unofficial) exposes 10 tools: list_locations, list_cameras, get_camera, get_camera_count, list_appliances, and 5 more. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.

Is the Spot AI MCP (Unofficial) server still maintained?

Spot AI MCP (Unofficial) is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.