An earlier version of this post claimed that ShiftSee had launched a hosted MCP endpoint with OAuth scopes, hard caps, anomaly detection, and complete audit logging. The code did not support those claims. We have removed them rather than leave prospective users with a fictional integration surface.
What exists
The repository contains a Node.js MCP server with 32 tools. A compatible local client launches the process and communicates over stdio. It can register email-verified business and shifter identities without a pre-created account or API key, then stores refreshable sessions in a local encrypted vault. Existing ssk_live_… personal keys remain available as a compatibility option.
The tools cover registration, AI passports, account context, profiles and media, connections, shifts, clock events, recorded livestream deliverables, notifications, reviews, and a payment handoff. The payment tool creates a five-minute, single-use confirmation URL. A signed-in owner must review that page before ShiftSee invokes the normal payment flow; the MCP process never charges directly.
What does not exist
There is no hosted ShiftSee MCP URL, remote streaming transport, MCP OAuth flow, MCP-specific scope model, enforceable MCP quota or spend-cap layer, anomaly detector, or complete live tool-call audit. Personal API keys are unscoped credentials, so they must be handled like passwords.
The mcp_call_log database migration is reserved schema, not evidence of a working audit product. Demo refreshes do not fabricate rows in it.
Who should use it
This is a developer preview for people who can build the repository and run a command-based local MCP server. It is not a hosted one-click connector and should not be represented as one.