spot-ai-mcp
Related Servers
Alternatives to spot-ai-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceGives MCP clients read-only access to every GET endpoint of Apple's Campaign Management v5 and Apple Ads Platform v1 APIs across multiple ad accounts, over stdio or Streamable HTTP. It exposes one tool per endpoint with per-account OAuth handling, pagination, and structured errors, while excluding all mutation and POST-only reporting endpoints.193 npmMIT
- AlicenseAqualityDmaintenanceEnables querying and exploring Cribl Stream and Edge deployments, providing access to worker groups, fleets, sources, destinations, pipelines, routes, event breakers, and lookups through a structured interface.73MIT No Attribution
- AlicenseAqualityAmaintenanceEnables MCP-aware agents to read and explore Oracle Cloud Infrastructure — listing, fetching, and searching across 39 resource types spanning Identity, Compute, Block Volume, Networking, Object Storage, and OKE. Runs locally over stdio using credentials from ~/.oci/config, with fail-closed safety gates and audit logging governing future write operations.4Apache 2.0
- FlicenseAqualityAmaintenanceEnables read-only inspection of configured WordPress and Joomla GMC Builder sites: listing site aliases and platforms, running an authenticated connectivity probe, retrieving up to ten builder element type names, and summarizing locally supplied layout JSON into node counts and types. It runs locally over stdio with credential environment variables, a fixed GET allowlist, and rate-limited requests.4-

sifflet-mcpofficial
AlicenseAqualityDmaintenanceEnables data observability operations with the Sifflet platform. Supports exploring assets, monitors, incidents, generating monitor-as-code YAML from descriptions, and performing impact analysis.107MIT- AlicenseAqualityAmaintenanceLets an AI agent read a Pyxis dashboard's analytics — overviews, funnels, devices, acquisition, backend requests, visits and project settings — using a read-only access token created by an admin and revocable at any time. It runs locally over stdio, holds no state, and exposes only GET-style reads of the live Pyxis API.161,507 npmMIT
TDQS
Scored across 10 tools
Most tools target clearly distinct resources and actions (locations, cameras, appliances, zones, intelligence, LPR). The main overlaps are get_camera_count versus list_cameras (count is derivable) and spot_api_get, which by design overlaps with everything as an escape hatch, but it is explicitly framed as a generic fallback.
Nine of ten tools follow a clean verb_noun pattern (list_locations, get_camera, get_zones, etc.) using get_/list_ prefixes. The single outlier is spot_api_get, which uses a noun_verb ordering, a minor deviation.
Ten tools is well within the ideal range and each one covers a distinct read operation. No redundant or filler tools; the set is tightly scoped to a read-only camera/security API.
The surface covers the core domain: locations, cameras, appliances, zones, intelligence events, LPR, and live streams. Minor gaps exist (no get_location or get_appliance detail), but the spot_api_get escape hatch lets agents reach any documented endpoint, mitigating dead ends.