Bright

Ask Bright from your assistant.

Add Bright to an AI assistant and it can bring you Bright Weekly, look up a record, or check a claim you heard. The evidence and its limits come with every answer.

Add the connector

In your assistant’s connector or app settings, add a custom connector with this address:

https://brightaifuture.com/api/mcp

It works with assistants that support remote Model Context Protocol (MCP) connectors over HTTP. No account, key or sign-in is needed, and every tool is read-only. Bright does not certify compatibility with any assistant it has not tested.

Things to ask

What the connector can do

What it won’t do

Bright does not issue automated verdicts. When your assistant checks a claim, Bright returns the records whose evidence bears on it, with their evidence states and limitations, and says so when it has no record. Only editorially approved editions of Bright Weekly are available; drafts never are. Nothing your assistant sends changes Bright. Bright receives only the tool requests your assistant sends, including the question or search terms needed for that request; it cannot browse your other conversations or files.

Keep the limits attached

Every Bright item keeps a claim, its evidence state, its nearest limitation and its primary sources together. The connector asks assistants to keep them together too, to cite the primary source for the underlying finding, and to link the Bright record.

Privacy

Bright logs the tool called, whether it succeeded and how long it took, plus a coarse assistant family when an assistant connects. It does not log your questions, searches or claims, or any account or device identifier. Details are in the privacy notice and the terms.

For developers

The connector uses MCP Streamable HTTP in stateless JSON mode: POST JSON-RPC to /api/mcp. The same records are available over HTTP at /api/weekly, /api/claims, /api/discovery, /api/guides and /api/models. See the agent guide and OpenAPI 3.1.