Model Context Protocol server

Any assistant can now ask why.

IQ.Agent puts the Singula decisioning engine on the wire. Claude, or any MCP client, can query the subscriber book in plain language and get back a priced, ranked action with the named signals that produced it. The engine stays server-side. Only the reasoning travels.

POST /mcp connecting to engine

What the assistant sends

–

What the engine returns

–

Because

pick a question above

Every action IQ Core proposes carries the signals that fired it. No recommendation is ever unattributable.

Agentic is the easy half. Accountable is the hard half.

An assistant wired to a database can launch a campaign. It cannot tell you why it chose that subscriber, that offer, or that moment. IQ.Agent is the same convenience with the reasoning intact.

Traceable

Every action names its evidence

Actions arrive with a because array of fired signals and the raw fact values behind each one. Six months later, the decision log reconstructs the call exactly.

Deterministic

The same facts give the same answer

Twenty-seven signals, a scored health model and an expected-value ranking. The language model reads the result. It does not invent it.

Governed

Nothing sends without a named human

Read tools are open. The proposal tool prepares an action and stops. Approval happens in the Singula console, by a person, against contact caps and offer governance.

Protected

The engine never leaves the server

Weights, thresholds and arbitration run inside the worker. Assistants receive decisions, never the decisioning.

Seven tools on the wire

Six read freely. One stops and waits for a person.

list_signals

The signal vocabulary: family, weight, and the facts each signal reads.

explain_signal

What one signal means and what has to be true for it to fire.

find_subscribers

Filter the book by status, moment, health band or fired signal.

rank_at_risk

Today's work queue, ordered by the expected value of acting.

get_decision

One subscriber's full packet: signals, evidence, scores, ranked actions.

segment_summary

Cohort shape by decision moment, with the value of the whole segment.

propose_action

Prepares the recommended action and returns it for approval. Sends nothing, changes nothing.

Human approval required

Connect it to Claude

Open Claude on desktop or web, then Customize, then Connectors. Custom connectors are not available in the mobile apps.
Click + next to Connectors, give it a name, and paste the endpoint below.
Under Request headers, add Authorization with the value Bearer <your token>, including the space.
Enable it in a chat with the + button, then Connectors.
Ask: which fifty subscribers should we work today, and why?

https://iq-agent.pages.dev/mcp

On a Team or Enterprise plan an Owner adds the connector once in Organization settings, then colleagues connect to it individually. Request header authentication is in beta and is still rolling out, so the field may not appear yet. The console above runs without a token because it can only fire five fixed queries.