The client says the server needs authentication
The client says the server needs authentication
Run the client’s sign-in:
/mcp then Authenticate in Claude Code, codex mcp login fincept in Codex, the login action in Cursor or VS Code MCP settings.The connect page says an active plan is required
The connect page says an active plan is required
The account you signed in with has no active Exclusive Pro plan. Check it at fincept.in/enterprise/account, or sign in with the account that has it.
Every call returns upgrade_required
Every call returns upgrade_required
Your plan changed or lapsed after you connected. Renew or upgrade, then retry; there is no need to sign in again.
Calls stopped working after a while
Calls stopped working after a while
The connection was ended: a password change, a refresh token used twice, or more than 20 connections on the account. Sign in again from the client.
Codex asked me to sign in twice
Codex asked me to sign in twice
codex mcp add signs you in already. Running codex mcp login straight after starts a second sign-in. Both work; Codex keeps the second.PowerShell rejects && in a command
PowerShell rejects && in a command
Windows PowerShell 5.1 does not support
&&. Run each command on its own line, or use ;.The agent says a tool does not exist
The agent says a tool does not exist
Only the core set is listed. Ask the agent to use
fincept_search_tools, or name the tool. A name the catalog does not have returns unknown tool.A result says status partial
A result says status partial
The result was too large to send whole. The agent reads the rest with
fincept_read_result, or open artifacts[0].view_url in the browser. See large results.An engine tool returns validation_failed
An engine tool returns validation_failed
The message names the argument at fault. Common causes: series of different lengths in one table, too few observations for the model, a formula or column name the table lacks, asset weights or bounds that cannot be met, or a
$fincept path that does not exist in the referenced tool’s data.HTTP 429 Too Many Requests
HTTP 429 Too Many Requests
The account passed 120 requests per minute. Clients back off and retry; agents that loop over many symbols should use batch tools such as
market_get_quotes.