FALCON VERIFY
Documentation
FALCON Verify checks whether an AI's answer is supported by the evidence it was
given, and leaves a record a stranger can verify. It connects to Claude and ChatGPT as a
remote MCP server: one address, a sign-in or a token, nothing to install.
1. Connect an assistant
Claude: Settings → Connectors → Browse connectors, find FALCON Verify
and press Connect. ChatGPT: type @ in the message box, choose Plugins, find FALCON
Verify and press Install. Both open FALCON's page: sign in and press Approve. Nothing to
paste.
Any other client (Claude Code, the ChatGPT desktop app's MCP screen, Cursor, your own
code) uses the address https://falcon.1-i.ai/mcp with a connector token minted on the
Connect page after you sign in at https://falcon.1-i.ai/verify/.
Claude (claude.ai, Claude Desktop)
- In Claude, open Settings → Connectors → Browse connectors and find FALCON Verify.
- Press Connect. Claude opens FALCON's page: sign in the way you did here and press Approve.
- Start a new conversation with FALCON Verify on in the tools menu and say "verify that" after any answer.
ChatGPT
- In ChatGPT, type @ in the message box and choose Plugins, then find FALCON Verify and press Install.
- ChatGPT opens FALCON's page: sign in the way you did here and press Approve.
- Start a new chat with FALCON Verify enabled and say "verify that" after any answer.
Other clients: Claude Code, the ChatGPT desktop MCP screen, Cursor, your own code
- Every other MCP client uses the address https://falcon.1-i.ai/mcp with a connector token created on the Connect page.
- Claude Code: run claude mcp add --transport http falcon https://falcon.1-i.ai/mcp --header "Authorization: Bearer $FALCON_TOKEN" with the token exported as FALCON_TOKEN; claude mcp list shows falcon as connected.
- ChatGPT desktop MCP screen (Plugins → MCPs → Add server): name falcon, the address above, one header Authorization = Bearer <your token>; leave 'Bearer token env var' empty; save, switch falcon on, start a NEW chat and enable it.
- Any mcp.json client: type http, the address above, and the same Authorization header.
2. Confirm the connection
- Ask the assistant:
What FALCON tools do you have, and is FALCON ready?
It should list falcon_verify and say FALCON is ready.
- Ask it to verify a short answer. Every FALCON result ends with a line that begins with
FALCON's mark and reads like
Verified by FALCON Verify · run vf_… · 21 of 21 material claims decided, 0 unsupported (0%) · protocol v1.28 · chain of 11 entries verified. Verdicts without that
line did not come from FALCON.
- The Connect page in your workspace shows the most recent call once one has arrived.
3. What to say
- Verify the last answer
falcon verify the above response - Verify against facts you paste
Verify this answer with FALCON against these facts, and report each claim with its verdict: <answer> — facts: <the figures and text it should rest on> - Check a draft against a document
Use FALCON Verify to check this summary against the attached document. Send the document text as the evidence. List every unsupported claim and what would settle it. - Verify with your own claim list (free on every plan)
Run falcon_verify with claims = the statements I list below, in the output's own words, so no model extraction is needed: … - Confirm the connection
What FALCON tools do you have, and is FALCON ready?
falcon_verify | the check: an answer, the evidence, a verdict per claim, the attribution |
falcon_verify_status | a queued verification's state and final rate |
falcon_tool_readiness | whether FALCON can run right now: model, store, plan |
falcon_whoami | which tenant and credential the assistant is acting as |
falcon_account | the plan, the allowance left this month, when it resets |
Read-only tools carry the MCP readOnlyHint, so an assistant
may call them without asking each time; falcon_verify writes its own run record
and destroys nothing.
What a result means
- supported — Every material statement is backed by the evidence you gave.
- qualified — Supported, with a caveat named: a rounding, a period, a scope.
- more evidence needed — Something the answer asserts is not in the evidence; the result says what would settle it.
- execution problem — FALCON could not run the verification; it says why, and whether to retry.
A verification answers "is this supported by the evidence given", never "is this true".
One verification is up to 2,500 tokens of model work, counted at the model's own prices:
a passage the model reads from its cache counts a tenth, so checking many statements
against one document costs little more than checking one. A run whose statements you
list yourself calls no model and is never counted.
Plans
- Free — 25 verifications a month with FALCON finding the statements; listing the statements yourself is free and unlimited. No card.
- Starter — $8.99 a month, 150 verifications, then 9¢ each.
- Personal — $19 a month, 400 verifications, then 8¢ each.
- Team — $149 a month, 3,000 verifications pooled across 10 people, then 6¢ each.
- Pay as you go — no monthly fee, 10¢ per verification.
- Enterprise — a committed volume, single sign-on, a copy inside your own network, the offboarding certificate. Contact sales.
Your data