zenture MCP Server for ChatGPT
By zenture UG
Overview
Purpose: Evaluate selected AI answers, drafts and work steps against the task they were meant to complete. zenture helps you decide whether a result is supported by its sources, follows your requirements, or needs revision or human judgment. How it works: Select one answer or work artifact and provide its original task, including explicit requirements. The evaluation checks factual claims against the sources cited in the artifact and checks the result against that task. It does not rewrite the submitted work or guarantee that every claim is true. Tools: • 'run' starts an evaluation and returns its status and result ID. • 'get_run' follows that evaluation and returns its verdict, findings, evidence and coverage when available. • 'list_runs' finds your recent evaluations so you can reopen one. • 'cancel_run' requests cancellation when you ask to stop an active evaluation. • 'record_run_outcome' records your explicit feedback on a finished evaluation. Results and limits: Results distinguish ready, revise, human_review and insufficient_evidence. They show what was supported, which requirements were met, what could not be checked and what to do next. Coverage depends on the service and evaluation profile. zenture evaluates only work you select; it does not watch other chats or replace your judgment.
How to connect
- ChatGPT: Open the zenture listing in the ChatGPT app directory and choose Connect. ChatGPT listing zenture exposes 5 tools here.
Tools
get_run
ChatGPTlist_runs
ChatGPTrecord_run_outcome
ChatGPTrun
ChatGPTrun directly; that request is the user's consent for one Run, do not ask again. Ask one short question only if the task or the answer cannot be identified. How: task = the user's original instruction verbatim (not the check request; if there is none, the check request). artifact = the one answer the user points to, verbatim, links unchanged, none added. idempotency_key: omit it; the server creates one for a waiting call (pass your own only to control retries). wait_seconds 30, then get_run(wait_seconds=30) until the status is terminal. Queued starts may expire uncharged; result pending: read again. Note: statements are checked only against https links already in the answer; an answer without links usually ends in revise or human_review. Cost: each Run consumes account credits by profile (fast < standard < detailed). The charge is reported only in billing_summary; state only what it shows; billing pending is not final. Outcomes (acceptance_decision): ready = every criterion met, every factual statement supported. revise = a criterion not met, or a statement contradicted or without source. human_review = criteria ambiguous or conflicting, or statements that could not be verified. insufficient_evidence = a required evaluation could not be performed (e.g. a criterion not assessable), or more statements than the profile assesses (30 fast, 60 standard or detailed; the rest is reported as incomplete); nonfactual text is not a claim. completed is technical, not acceptance. Recovery: the same idempotency_key with the same inputs returns the same Run. After a disconnect never start again; find the Run with list_runs. too_many_outstanding_runs and price_ceiling_exceeded are not retryable for this request.Capabilities
Example Prompts
Click any prompt to copy it.
Links
Similar Apps
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/zenture"><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
[](https://mcp-app-store.keenethics-labs.com/app/zenture)





