Getting Started
Stand Behind It readiness tools
This page explains how the paid MCP-backed tools move from a public Suite Spot page into a subscriber account. The short version: free users get one capped front door, subscribers get Nora and Serena, and the server saves the results to their account history.
Current build state
June 25, 2026
The production MCP server is live at mcp.provenanceai.app.
The OpenRouter usage you are seeing is expected from production smoke tests: Sonnet for paid readiness/voice calls and Haiku for the free front door.
The remaining launch gate is the billing-to-entitlement handoff: after payment, the LMS must write the subscriber row that unlocks the paid tools.
How a subscriber gets the tools
The MCP server is not something a normal customer needs to understand. They interact with Suite Spot pages. The site handles account identity, entitlement, and server calls behind the scenes.
Start with the free check
A visitor pastes a writing sample into the free front-door tool. That call uses the low-cost Haiku path, daily limits, burst limits, and identical-input caching.
Subscribe when they need the full pass
The paid path is the Stand Behind It readiness suite: Nora checks authorship readiness, Serena builds the voice profile, and persistence saves account history.
The site identifies the account
The LMS or Suite Spot account layer sends the subscriber account id to the MCP server using the private internal key. The browser never receives that key.
The MCP server checks entitlement
The server reads pmcp_entitlement in the LMS Supabase project. Active or past-due subscribers get the full result; free or lapsed users get a clean upgrade path.
The result is saved back to the account
Serena writes or updates pmcp_voice_profile. Nora appends pmcp_readiness_event. The user receives profile_ref or event_ref so the history is durable.
The v1 tool surface
Version one stays deliberately small. One free front door. Two subscriber tools. No course corpora, no fourth agent, no detector-bypass positioning.
score_voice_authenticityFree front doorA capped, rate-limited first scan that shows the writer where the draft reads generic and what kind of ownership work is needed.
analyze_writing_voiceSubscriber toolSerena Voss builds the account-level voice profile: rhythm, register, vocabulary range, and stylistic fingerprints.
check_authorship_readinessSubscriber toolNora Whitfield checks whether the writer can stand behind the draft under review from a professor, editor, client, or colleague.
What the customer sees
A free visitor sees a limited writing check and a reason to subscribe. They do not see API keys, server URLs, database tables, or model routing.
A subscriber sees full Nora and Serena outputs, plus saved references. The saved references matter because the product becomes account memory, not just a prompt they could copy once and cancel.
What stays private
The browser calls the LMS. The LMS calls the MCP server. The private internal key and Supabase service credentials stay on the server side.
If entitlement is missing or stale, the paid tools fail closed. The user gets a clean paused or upgrade response, not raw infrastructure errors.
Operator checklist
This is the short launch checklist for Christopher and the build team. When these are all true, the tool can move from working server to customer-ready subscription.
- OpenRouter key has a hard monthly limit set.
- MCP_SERVER_URL in the LMS project points to mcp.provenanceai.app.
- MCP_INTERNAL_KEY matches in both provenance-lms and provenanceai-mcp.
- PayPal checkout writes pmcp_entitlement for the buying user.
- Production smoke returns a non-null profile_ref and event_ref for a real entitled account.
Next build move
Connect checkout to entitlement.
The MCP server is ready. The practical product is ready when a real payment creates the subscriber row, the LMS passes the account id, and the page returns saved refs without manual test setup.