mcp-spatial-perception
Related Servers
Alternatives to mcp-spatial-perception
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access file systems, fetch web content, query databases, and execute shell commands through the standardized Model Context Protocol.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI applications to retrieve on-chain context from EVM-compatible blockchains via the Model Context Protocol.-

Allora MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceEnables AI systems to fetch machine learning inferences and prediction market data from the Allora Network through the Model Context Protocol.14 npm2MIT
Cheqd MCP Toolkitofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely manage decentralized identities, verifiable credentials, and trust registries on the Cheqd network via the Model Context Protocol.1Apache 2.0- AlicenseBqualityBmaintenanceDiscover, pay for, execute, and publish monetized APIs directly from your agent, settled per call in USDC over x402, through the Model Context Protocol.42235 npm37 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access real-time touchless gesture recognition, 3D hand landmarks, virtual key event injection, facial telemetry, sensitivity adjustment, and system health diagnostics through the Model Context Protocol.MIT
TDQS
Scored across 1 tool
With only a single tool in the set, there is no possibility of overlap or misselection. The purpose—fetching real-time edge-parsed detections from a DePIN node—is unambiguous.
The lone name query_spatial_feed follows a clean verb_noun snake_case convention that is easy to read. A single tool cannot demonstrate a consistent pattern across the set, so this is scored slightly below full marks.
One tool is too thin for a domain like spatial perception, which naturally involves node discovery, multi-region queries, and time-window filtering. A single feed reader leaves the server under-scoped.
The surface only supports fetching live detections; there is no way to list available nodes, filter by region/object class, or query historical data. These gaps will force agents into dead ends for anything beyond a raw live read.