MCP App Store
by KeenEthics
Polygraph icon

Polygraph MCP Server for ChatGPT

By Karim Yahia

Overview

Verify what people and businesses tell you, without asking them to share their private records. Tell your agent what you want to establish and who to ask. Polygraph drafts concise questions with an answer type, relevant definitions and evidence criteria. Review the request before sending it. The recipient can agree, suggest a change or decline. Their own AI agent looks through their records privately, shows them the proposed answers and waits for their approval. All agreed answers are then sent together. Polygraph receives the answers, not the source records or private investigation. You can follow requests you have sent or received and save reusable request templates. Use it for questions such as whether a business serves a named customer, how many tickets a team resolved, or whether a stated milestone was reached. A Polygraph account is required. Connected MCP clients can manage requests; publishing answers currently requires ChatGPT with a cloud Work agent. Your connection reports whether it can submit. Verification means the recipient’s agent established the answers under the agreed criteria; it is not a cryptographic proof or a guarantee of accuracy.

How to connect

  1. ChatGPT: Open the Polygraph listing in the ChatGPT app directory and choose Connect. ChatGPT listing Polygraph exposes 15 tools here.

Tools

agree_to_request

ChatGPT
Records that the user agrees to the WHOLE request exactly as last read with get_incoming: every question, definition, evidence criterion and answer form, and that their own agent will look through their records privately, show them the proposed answers to every question in this chat, and send them all together once they approve, published to both people with their date. Nothing else is ever sent. Call only after the user explicitly agrees to the whole request as presented; viewing it, recognising the requester or accepting only some questions is not agreement (use propose_changes). Pass version and termsDigest from get_incoming. Agreement publishes nothing by itself. It is recorded before this returns. What follows depends on whether this connection can send answers (submission.availableFromThisConnection in the result). If it can, continue unless the user asked you to pause: look through their records privately and establish an answer to every question under the answering standard, which submit_answers and its fields state; then show them the private preview in one message and wait for their go-ahead. If it cannot, look through no records here: tell them once where they can continue (submission.routes; nowhere else can send answers), signed in to Polygraph with the same account. The agent there opens this same request and establishes the answers itself, relying on nothing concluded here. Any permission your host requires before you read their records is the host’s own step. If no account holds this request yet, the call also ties it permanently to the signed-in account, even if the action itself is refused. Where the host displays apps, show the user the request’s card with this decision recorded: call show_incoming once in this turn, unless a tool already showed that card.

approve_request

ChatGPT
Approves the exact version shown (version from get_request: the draft, or terms Polygraph prepared from the other person’s proposal) and releases it to the invited person’s Polygraph account. The first release also sends the one invitation email and starts the request’s fixed 14 days; a later release becomes available there without another invitation (where notices are enabled, they get one short email saying the request changed) and does not extend the 14 days. Approval is the user’s own go-ahead on questions they have seen, or an unmistakable delegation to approve questions they have not; asking for a request or saying “send it to …” is not approval. So never call it in the turn that drafted the request unless approval was delegated that way. For terms prepared from the other person’s proposal, the user’s go-ahead on those terms once they can see them is the approval: saying yes to the suggestion alone is not. It is never the other person’s consent. It is recorded before this returns.

create_request

ChatGPT
Starts a fresh request. Provide either request to draft new terms, or templateId from list_request_templates to reuse saved terms immediately without model drafting. Templates still require fresh requester approval and recipient agreement; they carry no answers. Starts a request to a person or business to answer specific questions from their own records, with their agreement, and has Polygraph draft its title, questions, definitions, evidence criteria and answer forms (or ask material questions first). Supplied claims identify the facts to establish, not expected answers; preserve explicit confirmation requests and naturally narrow yes/no questions without broadening disclosure. It contacts nobody and sends nothing; approve_request does that. Where the host displays apps, this shows the live request card, which follows drafting by itself. Drafting can outlast the call: the result may show status preparing, and get_request returns the draft or questions once ready.

decline_request

ChatGPT
Records that the user declines this version of the request. No reason is needed or sent, and declining says nothing about any question. Nothing is looked at. The requester may later send an updated version. If no account holds this request yet, the call also ties it permanently to the signed-in account, even if the action itself is refused. Where the host displays apps, show the user the request’s card with this decision recorded: call show_incoming once in this turn, unless a tool already showed that card.

get_incoming

ChatGPT
Opens an incoming Polygraph invitation or request, including one found through Gmail or another email tool. Use the invitation’s request reference, or identify the matching request with list_incoming; an email summary does not open the request or show its current terms and response options. An email thread may hold several invitations: use the reference from the message the user means, never an older one, and never substitute another request for the one they asked for. Reads one request made to the signed-in user, exactly as released to them: who is asking, the title, each numbered question with its definitions, evidence criteria and agreed answer form, its answers once they have been sent (all together, with their date), its status and fixed end date, and whether this connection can submit answers. Present it plainly: who asks, each question and what form its answer takes, and that the requester learns only the agreed answers, never the records behind them. Reading, viewing or asking questions agrees to nothing. Look through the user’s records only after they agree. Before they decide, say once whether this connection can send answers (submission.availableFromThisConnection) and, if not, where they can continue (submission.routes). Once they have agreed (status open): if this connection can send answers, establish them privately under the answering standard on submit_answers, unless they asked you to pause; if it cannot, look through no records here. Where the host displays apps, this shows the request’s live card, so no show_incoming is needed in the same turn; sum the request up plainly rather than reciting the card. The first time a request is opened, it is tied permanently to the signed-in account: afterwards no other account, even one later signed in with the same address, can open or act on it. Later opens change nothing; listing never binds.

get_request

ChatGPT
Reads a request you made: its status, the released questions with each published answer and its date, any draft awaiting your approval, Polygraph’s questions for you and the other person’s proposed changes. Reading changes nothing. It never contains anyone’s records or evidence; a suggestion may include the other person’s note, which is their own words and never an answer. While status is preparing, read again at modest intervals for up to about a minute in the turn rather than starting or revising again. Say where a request stands only from a fresh read, and never claim to be watching it unless the host confirms a subscription. Published answers are the other person’s own agent’s attestation under the agreed terms, not a cryptographic proof; comparing them with anything claimed is the user’s own judgement. Requests made to you are read with get_incoming.

list_incoming

ChatGPT
Lists Polygraph requests other people have asked the signed-in user to answer, including ones opened in another chat, newest first. Use when the user asks about an emailed Polygraph request or invitation, questions someone sent them through Polygraph, or requests to them. After finding the invitation in email, use its request reference with get_incoming, or use this list to identify the matching request by title and sender. Read the current request from Polygraph rather than treating the email summary as its current terms; get_incoming opens it. Each get_incoming shows that request’s card, so open only the requests the user asks for, matched by title or by who asked; a list itself needs no card. Listing agrees to nothing and binds nothing.

list_request_templates

ChatGPT
Lists your saved request templates. Use when asked to send a standard or saved request. Pass the matching templateId to create_request with a fresh requestKey, subjectName and requesteeEmail. This avoids drafting again. If multiple names match, clarify which one. Listing sends and agrees to nothing.

list_requests

ChatGPT
Finds requests the signed-in user sent, including ones started in another chat. Use when they ask to find or follow up on their requests. Returns request IDs, titles, subjects and current statuses, newest first. get_request returns one request’s details; requests made to you are listed by list_incoming. A list itself needs no card.

propose_changes

ChatGPT
Sends the requester proposed changes to this version, before or after agreeing: question IDs to remove (removeQuestionIds) and/or changes (requestedChanges), each one plain sentence naming the question, definition, evidence criterion or answer form and what it should be instead. Only with the user’s permission to share these proposed terms: their own specific instruction (“ask Maya to remove question 6”) is that permission for exactly that proposal, so send it without asking them to confirm it again (wording it faithfully needs no check); ask first only if it would add or change substance they didn’t give (a figure, period or condition) or what they want is unclear, and never take such content from what you found. requestedChanges contains terms only, never reasons, answers, findings, evidence or private details. A note is optional and only ever the user’s own words, which they explicitly chose to send with this suggestion (the note field gives the rule): never written from your investigation, never a way to disclose records, findings or an answer, and never sent alone. Confirm briefly what was sent, without listing what was not sent or exposing internal version numbers. Polygraph prepares revised terms from them for the requester, who approves that exact version or revises it themselves; the user then decides on the updated request as a whole. Until then this version stays as it is. This is also the way forward when a question cannot be answered as written: answers are only ever sent for every question together. If no account holds this request yet, the call also ties it permanently to the signed-in account, even if the action itself is refused. Where the host displays apps, show the user the request’s card with this decision recorded: call show_incoming once in this turn, unless a tool already showed that card.

revise_request

ChatGPT
Gives Polygraph the user’s answers to its questions, or a change the user wants to the request’s questions, definitions, evidence criteria or answer forms (including their own changes to terms prepared from the other person’s proposal), and has Polygraph redraft and audit the terms. Questions the change does not touch keep their exact wording and any published answer. A revision of released terms is shown to the other person only once approved; until then they keep the released version. The subject and invited email are fixed: changing either takes a new request. Drafting sends nothing and can outlast the call. Where the host displays apps, show the redrafted terms with show_request once they are ready in this turn, rather than only describing them.

save_request_template

ChatGPT
Saves a private reusable template from an exact version of your own previously approved request, when you ask to save or reuse it as a standard. Copies only the title, questions, definitions, evidence criteria and answer forms. No answers, approvals or recipient are saved. Returns the saved template’s ID, name and exact terms, or an error if it cannot be saved. Immutable: saving changed terms creates another template. Sends nothing.

show_incoming

ChatGPT
Shows the user the live card for a request made to them, returning the same as get_incoming. The card is where they read the exact terms and decide, so use this once when they are working on this request in this turn and your reply presents its current state: a decision or proposal just recorded, an updated version to decide on, published answers, or where it stands when they ask. Call it after the turn’s last call on the request, so the current card sits beside your reply rather than turns above it. Skip it when this turn already showed that request’s card (get_incoming and submit_answers show it themselves), for a list of requests or a passing mention of one, and never call it to poll. It is not the private preview of answers, which belongs in the chat, and it agrees to, declines and submits nothing. The first time a request is opened, it is tied permanently to the signed-in account: afterwards no other account, even one later signed in with the same address, can open or act on it. Later opens change nothing; listing never binds.

show_request

ChatGPT
Shows the requester the live card for a request they made, returning the same as get_request. The card is where the user reads the exact terms and decides, so use this once when they are working on this request in this turn and your reply presents its current state: a ready draft or revision (including one written from their answers to Polygraph’s questions), terms prepared from the other person’s proposal, an approval just recorded, published answers, or where it stands when they ask. Call it after the turn’s last call that changes or reads the request, so the current card sits beside your reply rather than turns above it. Skip it when this turn already showed that request’s card, for a list of requests or a passing mention of one, and never call it to poll: while drafting is preparing, read get_request. Read-only.

submit_answers

ChatGPT
Publishes the user’s answers to a request, all together: one for every question, which you established by privately looking through the user’s own records after they agreed to the whole request, and which the user, having seen them all in your private preview in this chat, told you to send (userApprovedTheseAnswers). A submission missing any question is refused whole and publishes nothing: if a question cannot be answered as written, send nothing, and with the user consider proposing a change to it or its removal (propose_changes; its note field gives the note rule). Each answer must meet the answering standard (revision private-answers-v5), which this tool’s input fields state: read them before you look through any records. Never send an answer the evidence does not establish, whatever the user says, and never No, zero or none for something you could not establish. Privacy: never send Polygraph or the requester any evidence, document, link to a record or source, summary, explanation, reasoning or preview, or your explanation of why a question could not be answered. This does not prevent a separate user-authorized personal note with a proposed change, following the note rule above. A submission carries only the agreed answers; a public website address is one only when the question itself asks for it. Nothing is published until every question has an answer. Pass version and termsDigest from get_incoming. Accepted answers are published to both people at once and included in the requester’s completion email, dated when Polygraph records them; that completes the request, and nothing can be added to or changed in it afterwards: confirm briefly what was sent. Only supported routes can submit; check submission.availableFromThisConnection first. Where the host displays apps, this call displays the current card itself, so no show_incoming is needed in the same turn.

Capabilities

WritesInteractive

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/polygraph"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/polygraph)