Oculus MCP
Related Servers
Alternatives to Oculus MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to observe local codebases in real time through a secure, read-only MCP interface, providing workspace snapshots, git history and diffs, cross-project search, and project reality coverage without write access.MIT
- AlicenseNot gradedqualityAmaintenanceRead-only local MCP server for inspecting AgentInspect TypeScript AI-agent traces. Lists runs, exposes bounded causal-failure and TraceFacts evidence, evaluates TraceContract checks, compares runs, and creates share-checked evidence without mutating traces or invoking agent tools.777 npm165MIT
- FlicenseDqualityAmaintenanceProvides read-only, structured access to Yasin ecosystem information (project registry, documentation, GitHub state, diagnostics) through the MCP protocol, enabling AI agents to query without direct repository access.223-
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that provides AI agents with live, structured workspace awareness, including project listing, git status, and budgeted context packing, minimizing token usage.22 npm2MIT
- FlicenseAqualityCmaintenanceA read-only MCP server that lets AI assistants inspect local workspace files, search context, view git diffs, and fetch a fixed GitHub profile, all within a sandboxed stdio transport.5-
- AlicenseAqualityAmaintenanceA secure, local-first MCP server for read-only inspection and troubleshooting of development environments, exposing narrow, typed, auditable capabilities for repository inspection, log summarization, Docker review, and security scanning without granting unrestricted machine access.8MIT
TDQS
Scored across 4 tools
The list_* tools target distinct resources (projects, inspections, saved items), and get_inspection_context has a specific retrieval role. However, list_inspections and list_saved_items both concern persisted metadata, which could cause minor initial ambiguity.
All tool names use consistent snake_case with clear list_ or get_ prefixes and noun phrases. The pattern is predictable and readable throughout.
Four tools is lean but reasonable for a focused read-only inspection and cache server. Each tool covers a distinct read operation, though the surface could potentially benefit from additional targeted operations.
The tools cover listing tracked projects, inspections, saved items, and retrieving cached inspection context, but there are no create, update, delete, or refresh operations for these entities. This may be intentional for a read-only surface, but notable lifecycle gaps remain.