Connect your
assistant

Explore planned assistant connections, their readiness and their access requirements.

Live now: the public, read-only MCP server at /api/mcp (the method and the moat powers). Tools for your own readings are coming.

Planned connection flow; the brand glyph illustrates the interface and represents no company reading.

Choose your client

Choose a client to inspect readiness; setup instructions arrive with its connection.

Coming soon

A connection inside Claude.ai is planned. It will need the upcoming OAuth sign-in flow.

Sign-in: OAuth sign-in is coming soon. No account connection is available yet.
Starting access: Read your own saved readings. Your assistant will not set or change the Moat Index.
Setup readiness: Waiting for the live OAuth connection and approved client instructions.

Setup instructions are not available yet. Copying stays off until the approved instructions are ready.

No token, password or deck is requested in this preview.

These planned controls are required before connections launch.

MoatDefender computes the reading.Assistants will request readings without computing or influencing the Moat Index.

Approve token spending first.A human must approve the cost before a spending call. Agents get read-only access.

Manage connections in Settings.Connection management and revocation are planned release requirements.

Example prompts for the planned tools. These are not connected controls or live results.

“Explain the Moat Index bands and what evidence strengthens a reading.”

Coming: public method connection.

“Show my latest readings with their confidence, date and rubric version.”

Planned account lookup. Read-only access required.

“What evidence would demonstrate switching costs?”

Coming: public power connection.

Moat Index is an AI-generated opinion, not investment advice.