janus-kinematic-drive
Official<!-- mcp-name: io.github.janus-ubos-republic/janus-kinematic-drive -->
# Janus Kinematic Drive MCP - retired
> **Do not send USDC or any other payment for this package or its tools.**
> The hosted Janus service and its self-service and pay-per-call payment paths
> are unavailable. No payment sent through instructions from an older release
> can provision a service or purchase a tool call.
`ubos-janus-mcp` is retained as a historical record of UBOS's earlier
deterministic-retrieval work. Version `0.1.4` is an inactive, fail-closed
retirement release. It exposes one local `service_status` MCP tool and makes no
network requests.
## Successor
The proven retrieval and evidence mechanisms continue inside **Sovereign Desk**,
a provider-neutral resident harness for coding agents. Read-only contract parity
has been exercised through isolated Codex, Claude, and Gemini hosts.
That proof does not establish shared writes, multi-agent coordination, durable
cross-provider memory, clean-machine installation, or customer value. OpenClaw
has not been tested and is not claimed as supported.
The current managed Sovereign Desk pilot, its proof boundary, and its contact
path are published at <https://welcome-to-ubos.com/>. This retired repository is
not an order or payment surface. Contact: <info@welcome-to-ubos.com>.
## Historical installation
Existing users may install the retirement release to replace older payment
instructions with a local status notice:
```bash
pip install --upgrade ubos-janus-mcp==0.1.4
```
The source remains available for provenance under the MIT license. Historical
benchmarks describe deterministic retrieval fixtures, not the retired hosted
service or a guarantee of generated-answer quality.
TDQS
Scored across 8 tools
Most tools are clearly distinct: provisioning, checkout, checkout status, instance status, pricing, store listing, store calling, and concierge all map to different actions. The main potential confusion is between kinematic_checkout and kinematic_provision (both lead to getting a drive) and between kinematic_checkout_status and kinematic_status, but the descriptions clarify the differences well.
The server uses consistent snake_case and useful prefixes like kinematic_ and ubos_store_, but the naming style is mixed: some tools are verb-led (kinematic_provision, kinematic_checkout), while others are noun-led (kinematic_pricing, kinematic_status). The pattern is readable and scannable, but it is not a uniform verb_noun convention.
Eight tools is a well-scoped set for this server's purpose. Each tool covers a distinct aspect of Kinematic Drive access, checkout, status, pricing, and UBOS store usage, with no obvious bloat or excessive granularity.
The core lifecycle is covered: request, checkout, checkout status, instance status, pricing, and concierge support. Minor gaps exist, such as no explicit cancellation or deprovisioning tool and no direct status endpoint for a provision request, but these are workable gaps given the concierge and live data grounding.