Agenda Intelligence MD
MCP serverDev toolsYour AI can check whether briefs, memos, and evidence packs are ready to be trusted before you share or act on them. This integration adds the ability to validate, audit, and score documents that depend on evidence, so weak spots surface before they cause problems.
Use Agenda Intelligence MD in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Agenda Intelligence MD and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the strategic risk triage tool from Agenda Intelligence MD
No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.
Details
Available today. Use it from your connected AI after setup.
No key or account is asked for. Not verified by us yet: Ahel has not run a call through it.
After adding it, share a brief, memo, or evidence pack with your AI and ask it to check whether the evidence is ready. Start with a document you are about to send to someone else.
What your AI can do with it
- Validate briefs and memos before they go out
- Audit evidence packs for gaps
- Score how ready a document's evidence is
- Check any brief, memo, or evidence pack on request
Install Agenda Intelligence MD
The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http --scope user agenda-intelligence-md 'https://agendamcp.dpdns.org/mcp/agent'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://agendamcp.dpdns.org/mcp/agentAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=agenda-intelligence-md&config=eyJ1cmwiOiJodHRwczovL2FnZW5kYW1jcC5kcGRucy5vcmcvbWNwL2FnZW50In0=Open the link and Cursor adds the server at that address.
ChatGPT
https://agendamcp.dpdns.org/mcp/agentIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add agenda-intelligence-md --url 'https://agendamcp.dpdns.org/mcp/agent'Run it once, then sign in with codex mcp login agenda-intelligence-md if the server asks for an account.
From the project's README
As published by vassiliylakhonin/agenda-intelligence-md in README.md.
A deterministic evidence-packet linter for claim-backed AI output. Supply claims, source references, quotations, and source text; receive broken-reference, quote, number, lexical-support, and evidence-gap findings before human review.
Use it to make an AI answer's evidence trail inspectable in a local workflow, agent pipeline, or CI job. Packet completeness is not factual truth, source authenticity, or permission to act.
First run
Python 3.9 or later, from a checkout:
python3 -m venv .venv
.venv/bin/python -m pip install -e .
.venv/bin/agenda-intelligence check examples/evidence-packet/request.json
.venv/bin/agenda-intelligence check examples/evidence-packet/request.json --format json
For the versioned package, use python -m pip install "agenda-intelligence-md==1.16.0" instead of the editable install. The example commands above use files from this checkout.
The bundled synthetic packet reports packet_status=packet_complete and factuality=not_assessed. A stale or inaccurate source can still pass. Add --strict when packet findings should fail a CI step.
For document-based review, start with the local-file review guide and example manifest:
.venv/bin/agenda-intelligence review examples/evidence-review/manifest.json --format html
For a RAG answer with inline citations and retrieved chunk texts, use the Output Verification adapter. It assembles the packet locally and returns line-level findings and repair guidance:
.venv/bin/agenda-intelligence review-answer examples/output-verification/rag-answer.json
.venv/bin/agenda-intelligence review-answer examples/output-verification/rag-answer-revised.json --strict
The original fictional answer routes to revision; the corrected answer routes to human review. Both run without a wallet, model API key or network. A runnable LangGraph handoff shows a bounded repair loop. The adapter is included in version 1.15.0. To use your own answer without cloning this repository, follow the standalone quickstart.
The evidence-packet contract
| Input | Check |
|---|---|
| Claims and source IDs | References resolve within the supplied packet |
| Declared quotes | Quotations match the supplied source text |
| Claim wording and numbers | Deterministic support heuristics, unmatched numbers, and negation checks |
| Findings | Packet status, evidence gaps, and reviewer actions |
These checks use supplied text. They do not retrieve missing sources or establish semantic entailment. Lexical overlap can miss paraphrases and accept misleadingly similar wording. See request and response Schemas, evidence audit, and the factuality boundary.
Processed documents and tool results are data, never instructions. Before consequential action, record the goal, trusted evidence, unreliable evidence, assumptions, intended action, and stop/escalation conditions. Human review remains necessary.
Interfaces
| Interface | Start here |
|---|---|
| CLI and Python service | Quickstart, check_evidence_packet in services.py |
| MCP | MCP.md; launch agenda-intelligence-mcp from the installed environment |
| CI evidence linting | GitHub Action, with text, JSON, or SARIF output |
| Agent repair loops | Integration guides |
| Protected agent actions | Interaction Trust + Vizier gate |
| MCP pre-release checks | MCP Integration Check CLI / Action |
| Agent checkout experiments | ACP sandbox readiness check |
| HTTP and A2A | HTTP shell and A2A adapter |
The core checker is deterministic, stateless, and usable without a model API key. Optional generation and document adapters have separate dependencies. Core packet checks do not persist inputs or fetch outside sources.
Compatibility profiles and adapters
The repository also retains its strategic-intelligence shell, regional references, domain profiles, and Cloudflare deployments. The worker guide explains profile-specific behaviour; deployment documentation describes the hosted implementation.
Hosted demos expose their maintained inputs through live agent cards. Their verdicts are review prompts, not clearance. Trace IDs are not attestations. Signed readiness receipts, where configured, bind a gate result to a request/action; they do not establish source truth or grant permission.
The Output Verification gate does not permit relay based on caller-declared evidence. Workflow operators must authenticate actors, record approvals, and enforce boundaries. Vizier provides a separate delegation-policy layer; loading this checker alone does not enforce it.
Hosted pricing and limits belong to each profile's maintained configuration. Payment interoperability remains experimental and is not certified for standard x402 clients. Hosted demos have no autonomous live source retrieval.
What this is / What this is not
This is an evidence contract, deterministic preflight, and reviewer-facing tooling. It does not certify factual accuracy, provide legal or financial clearance, authenticate another agent, or replace an operator's action controls.
Global Think Tank Analyst owns the general reasoning method. Central Asia & Caspian and Gulf & Middle East own regional depth. Vendored compatibility references here are derived copies.
Examples and Status
- Runnable examples and Before / after.
- EU AI Act example: a dated source-backed snapshot, requiring current-source checks before reuse.
- Evaluation notes: tested behaviours and limitations.
- AnalysisBank: inspectable stored analysis and retrieval examples.
- Adoption record: the evidence for usage claims; demos and tests alone do not establish customer demand.
Implemented surfaces include packet schemas, the Python service, CLI checking, local-file review, and MCP. Hosted workers and optional agent/transaction examples require their own integration and operational review. Their presence does not establish production reliability or independently validated usefulness.
Documentation and development
Read AGENTS.md, source policy, security policy, and local checks before contributing. Contracts live under schemas/v1/; CHANGELOG.md records releases, and Roadmap records direction.
make ci
Run make verify-local when changing Worker, discovery, runtime, or validation-guard code. Packaged data mirrors must be updated with their canonical files when applicable.
MIT license for the code. The bundled official ACP schema retains its Apache-2.0 license and NOTICE.
Tools it offers (3)
What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.
strategic_risk_triagefleet_directorycorridor_bankability_screen
Signals
- GitHub stars
- 8
- Forks
- 1
- Last commit
- Sep 2026
- Weekly downloads
- 229
Advanced
- Delivery
- agenda-intelligence-md MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
io-github-vassiliylakhonin-agenda-intelligence-md- Source
- github.com/vassiliylakhonin/agenda-intelligence-md
- Hosted endpoint
https://agendamcp.dpdns.org/mcp/agent
github.com/vassiliylakhonin/agenda-intelligence-md