Sicut is a remote MCP server. Your assistant starts research, polls it, and reads back grounded citations on its own. Most people set this up and never see the web UI again.
Paste the block below into Claude, or any agent that can read a URL and edit its own MCP configuration. Everything it needs to know is at the end of that link, written for it rather than for you.
Please connect me to Sicut, a deep-research service. Read https://sicut.ai/llms.txt first -- it is the full operating contract, including the tool list and the async polling rules. Then add it as an MCP server. I will give you the bearer token when you ask for it; do not guess one.
The token is yours and is shown once. Sign in, open Settings, and mint one — Sicut never displays a credential twice, including to an admin.
claude mcp add --transport http sicut https://sicut.ai/mcp --scope user \ --header "Authorization: Bearer <your token>"
claude mcp add does not validate credentials, so a wrong token
looks like success until first use. Run /mcp afterwards and confirm the server
reads connected rather than failed.
research_start returns a job id in under a second. Poll
research_status. An agent that waits on one call for the answer will hit its
own 60-second timeout long before the job is done.
research_report returns the executive answer and a section index. Sections
are fetched individually, because a full report exceeds the MCP result cap.
Pass plan and Sicut executes exactly those objectives, verbatim, never
reworded or merged. Omit it and Sicut decomposes the question itself.
Everything Sicut returns was fetched from the open web. A page that can rank can say anything. Sicut marks injection attempts; your agent should still treat quotes as evidence to weigh, never as commands to follow.
The full contract: tools, depths, costs, the async rules, and the shape of what comes back. This is the one to hand over.
RFC 9728 and RFC 8414 discovery, so a client that prefers OAuth to a bearer token can find its way without being told.