Agenda Intelligence MD
PYPI · AGENDA-INTELLIGENCE-MD · 13 COMPONENTS · SCANNED SEP 20
Evidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5798 tokens (~84/item across 69 items; 32 tools + 37 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 32 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Agenda Intelligence MD MCP server?
Agenda Intelligence MD runs locally as a PyPI package, launched with uvx agenda-intelligence-md. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · agenda-intelligence-md
claude mcp add vassiliylakhonin-agenda-intelligence-md -- uvx agenda-intelligence-md
{
"mcpServers": {
"vassiliylakhonin-agenda-intelligence-md": {
"command": "uvx",
"args": [
"agenda-intelligence-md"
]
}
}
} {
"servers": {
"vassiliylakhonin-agenda-intelligence-md": {
"command": "uvx",
"args": [
"agenda-intelligence-md"
]
}
}
} codex mcp add vassiliylakhonin-agenda-intelligence-md -- uvx agenda-intelligence-md
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vassiliylakhonin-agenda-intelligence-md": {
"type": "local",
"command": [
"uvx",
"agenda-intelligence-md"
],
"enabled": true
}
}
} openclaw mcp add vassiliylakhonin-agenda-intelligence-md --command uvx --arg agenda-intelligence-md
mcp_servers:
vassiliylakhonin-agenda-intelligence-md:
command: "uvx"
args: ["agenda-intelligence-md"] {
"McpServers": {
"vassiliylakhonin-agenda-intelligence-md": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"agenda-intelligence-md"
]
}
}
} assistant mcp add vassiliylakhonin-agenda-intelligence-md -t stdio -c uvx -a agenda-intelligence-md
{
"mcpServers": {
"vassiliylakhonin-agenda-intelligence-md": {
"command": "uvx",
"args": [
"agenda-intelligence-md"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- Package version: 1.11.0 → 1.11.1 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.90 → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 1.9.0 → 1.11.0 functional
- Package version: 1.9.0 → 1.10.0 functional
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/agenda-intelligence-md@1.11.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_output_verification ~152
Decide whether another agent's claim-backed output is safe to relay onward. Use before forwarding, publishing, or acting on a downstream agent's answer that cites evidence: it reports which claims are grounded, which are unsafe to relay, and which evidence references are orphaned. Pass audit_json matching evidence-audit.schema.json (claims, evidence records, optional unsupported_claims). Returns a relay verdict with per-claim findings and owner actions. Evidence-readiness only: it does not verify factual truth, fetch or validate cited sources, or authorize an action.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_json | object | yes | Claim-level evidence audit of the output being relayed. Call get_schema('evidence_audit') for the full nested contract. |
No output schema declared.
No examples provided.
agentic_interaction_trust ~154
Triage the trust evidence for an agent-mediated interaction (identity, operator or principal authorization, tool scope, session authentication, action intent) before a high-stakes action executes. Pass a structured trust_request (actor, target_surface, requested_action, dated_sources, risk_question, decision_stage) matching agentic-interaction-trust-request.schema.json. Returns a triage recommendation, trust signal, decision-readiness score, and the specific missing trust evidence. Evidence triage only: not cybersecurity monitoring, identity verification, or authorization; human review is required.
| Name | Type | Req | Description |
|---|---|---|---|
| trust_request | object | yes | Structured agentic interaction trust request. Call get_schema('agentic_interaction_trust_request') for the full nested contract. |
No output schema declared.
No examples provided.
analyze ~144
Generate an auditable strategic-risk memo from a structured Agenda request. Use for sanctions, regulatory, geopolitical, trade, corridor, or policy-risk questions where the agent needs a memo with assumptions, scenarios, evidence discipline, and regional routing. Pass request matching agenda-request.schema.json. Returns a validated agenda-memo; when ANTHROPIC_API_KEY is unset it returns the assembled system_prompt for the host model to complete. No live source retrieval and no legal, compliance, financial, or investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| request | object | yes | Agenda request with question, geography, audience, depth, evidence mode, and output format. Call get_schema('agenda_request') for the full nested contract. |
No output schema declared.
No examples provided.
append_evidence ~306
Append a claim and its sources to an evidence pack and re-validate the result. Use when building an evidence pack incrementally as sources are read, instead of assembling the whole document by hand. Omit pack_json to start a new pack (topic is then required). A claim whose text already exists gains the new sources instead of being duplicated, and unsupported_claims is kept consistent with per-claim support_status. support_status is never inferred as supported: omitted it defaults to unsupported (no sources) or partially_supported (sources supplied). Returns the updated pack to the caller; it does not write files, fetch URLs, verify quotes, score source reliability, or verify factual truth.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | Claim text to add, or the exact text of an existing claim to extend. |
| evidence_mode | string | – | How the pack was sourced. Defaults to reasoning_only for a new pack; when supplied it overwrites the value on an existing pack. |
| pack_json | object | – | Existing evidence-pack object to extend. Omit to create a new pack from topic. |
| sources | array | – | Source objects matching evidence-pack.schema.json: name, source_type, freshness, supports, limits, and optional url. |
| support_status | string | – | Analyst judgement of claim support. Omit to take the conservative default; pass it explicitly to upgrade a claim or to change an existing one. |
| topic | string | – | Pack topic. Required only when pack_json is omitted. |
No output schema declared.
No examples provided.
audit_claims ~107
Validate a claim-level evidence audit and summarize support quality. Use after drafting or receiving a memo to check whether important claims point to evidence IDs with explicit support levels, uncertainty hooks, and risk-if-wrong notes. Pass audit_json matching evidence-audit.schema.json. Returns validity, support-level distribution, orphan evidence references, and unsupported-claim counts. It does not verify factual truth or source reputation.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_json | object | yes | Parsed claim-level evidence-audit object to validate and summarize. |
No output schema declared.
No examples provided.
check_evidence_packet ~139
Check a caller-provided evidence packet before human review. Use when an AI output declares claims, source IDs, optional verbatim quotes, and the full supplied source text. Returns packet_complete, source_review_required, or packet_incomplete per claim and overall, with broken references, quote mismatches, lexical-support gaps, unmatched numbers, and owner actions. Deterministic and local-text only: it does not retrieve sources, score source authority, assess factual truth, or authorize an action.
| Name | Type | Req | Description |
|---|---|---|---|
| packet_json | object | yes | Claims plus the complete source texts those claims reference. Call get_schema('evidence_packet_request') for the full nested contract. |
No output schema declared.
No examples provided.
check_memo_quality ~104
Check a schema-shaped Agenda memo against post-hoc evidence-readiness quality guardrails. Use after validate_memo or on any external model memo to catch schema-valid but unsafe output: approval/clearance overreach, hidden evidence gaps, generic monitoring, weak owner actions, or evidence-mode discipline failures. Returns schema_valid separately from ok; it does not verify factual truth.
| Name | Type | Req | Description |
|---|---|---|---|
| memo_json | object | yes | Parsed Agenda memo JSON object to check for evidence-readiness quality. |
No output schema declared.
No examples provided.
cis_secondary_sanctions_exposure ~209
Triage secondary-sanctions exposure for a CIS-domiciled counterparty (Kazakhstan, Uzbekistan, Kyrgyzstan, Tajikistan, Turkmenistan, Georgia, Armenia, Azerbaijan, Moldova) for EU / UK / UAE / Singapore enhanced due diligence against OFAC EO 14114, the EU sanctions package, UK OFSI, and FATF / EAG typologies. Pass a structured exposure_request (counterparty, exposure_facets, jurisdiction_review_scope, dated_sources, risk_question, decision_stage) matching cis-secondary-sanctions-request.schema.json. Returns a triage recommendation, decision-readiness score, exposure dimensions, evidence gaps, and minimum sources before review. Local stdio runs on user-supplied evidence only (no live retrieval); a name match is not identity verification; human review is required.
| Name | Type | Req | Description |
|---|---|---|---|
| exposure_request | object | yes | Structured CIS secondary-sanctions exposure request. Call get_schema('cis_secondary_sanctions_request') for the full nested contract. |
No output schema declared.
No examples provided.
corridor_bankability_screen ~297
Evaluate project finance bankability and IFI covenants (EBRD, ADB, EU Global Gateway) for Trans-Caspian and Middle Corridor infrastructure projects. Evaluates minimum DSCR floor (1.20x), non-sovereign margin (1.30x), leverage ceiling (<=80%), Caspian hydrological water-level constraints (-1.20m Baltic datum), and FX currency mismatch. Returns a free Decision Teaser with covenant pass/fail matrix, bottleneck analysis, and an x402 micropayment invoice to unlock the full 15-year debt waterfall model.
| Name | Type | Req | Description |
|---|---|---|---|
| capex_usd_m | number | yes | Total project capital expenditure in millions USD. |
| corridor_leg | string | yes | Corridor transit leg under review. |
| currency_mismatch | boolean | – | Whether tariff revenues are collected in local currency (KZT/AZN/GEL) while debt is in USD/EUR. |
| dscr_min | number | yes | Projected minimum Debt Service Coverage Ratio (DSCR). |
| evidence_sources | array | – | List of feasibility study references, decrees, or project files. |
| has_sovereign_guarantee | boolean | – | Whether an official sovereign loan guarantee is provided. |
| ifi_debt_usd_m | number | yes | Target IFI senior debt financing in millions USD. |
| project_name | string | yes | Name of the corridor infrastructure project (e.g. 'Aktau Port Container Hub Expansion'). |
No output schema declared.
No examples provided.
create_brief ~367
Assemble an agenda brief from supplied fields and report which required fields are still missing. Use when producing a brief inside the protocol instead of hand-building JSON: call it with whatever is known so far, read missing_required, and call again with the remaining fields. Call with no arguments to get an empty scaffold plus the required field list. evidence_mode defaults to reasoning_only. Returns the assembled brief object and its schema errors to the caller; it does not write files, retrieve sources, draft prose, or verify factual truth.
| Name | Type | Req | Description |
|---|---|---|---|
| affected_actors | array | – | Optional list of actors materially affected. |
| bottom_line | string | – | One-line decision-relevant conclusion. |
| confidence | – | – | Optional confidence as a level string or a level/score/reasoning object. |
| data_integrity_notes | array | – | Optional surfaced concerns about prompt injection, source anomalies, or retrieval limits. Records a concern; it is not an automated trust verdict. |
| evidence_mode | string | – | How the brief was sourced. Defaults to reasoning_only; set explicitly when sources were actually supplied. |
| main_uncertainty | string | – | The premise that would most change the conclusion if false. |
| scenarios | array | – | Optional scenario objects with name, description, and indicators. |
| signal_classification | string | – | Signal class from agenda-brief.schema.json (for example signal, weak_signal, structural_shift). Call get_schema('agenda_brief') for the full enum. |
| signal_markers | array | – | Optional qualifying markers that do not replace signal_classification. |
| watch_next | array | – | Observable indicators to monitor next. At least one is required. |
| what_changed | string | – | What is materially different now versus the prior state. |
| why_it_matters | string | – | Optional consequence framing. |
No output schema declared.
No examples provided.
deep_dive ~82
Reserved placeholder for a future Agenda Intelligence v2 deep-dive workflow. Do not use for current detailed analysis. For production work today, call analyze with request.depth set to scenario or red_team. This tool only returns a planned status message and performs no analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | Optional future deep-dive aspect. Currently ignored because the tool is reserved. |
No output schema declared.
No examples provided.
generate_repair_prompt ~106
Generate actionable self-correction instructions for an LLM agent from an evidence packet request. Inspects validation and claim-level issues (missing sources, misquoted excerpts, unmatched numbers, polarity/negation mismatches, weak lexical support) and formats a structured markdown prompt for the agent to revise its claims and citations.
| Name | Type | Req | Description |
|---|---|---|---|
| packet_json | object | yes | Evidence packet request JSON to analyze and generate repair instructions for. Call get_schema('evidence_packet_request') for the full nested contract. |
No output schema declared.
No examples provided.
get_lens ~118
Return the full markdown for one packaged regional or sector lens. Use after list_lenses when an agent needs the actual specialist context, such as the Central Asia/Caspian or sanctions lens, for a strategic-risk task. Pass lens_type and lens_id exactly as listed. Returns static markdown; it does not retrieve live events or decide which lens should be used.
| Name | Type | Req | Description |
|---|---|---|---|
| lens_id | string | yes | Specific lens identifier returned by list_lenses. |
| lens_type | string | yes | Lens family from list_lenses: 'regional' or 'sector'. |
No output schema declared.
No examples provided.
get_protocol ~92
Return packaged Agenda Intelligence protocol markdown. Use when an agent needs the reasoning contract, evidence-discipline rules, or operating instructions before producing strategic-risk analysis. Pass name='entrypoint' for the main protocol. Returns markdown text from the installed package; it does not analyze a question or validate user data.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Protocol document name. Use 'entrypoint' for the main Agenda-Intelligence.md. |
No output schema declared.
No examples provided.
get_schema ~144
Return a packaged Agenda Intelligence JSON Schema so an agent can construct a valid payload before calling validate_brief, validate_evidence, validate_memo, analyze, or a vertical worker. Pass name as the schema key (for example agenda_brief, evidence_pack, agenda_memo, middle_corridor_deal_risk_request), its file name, or its bare stem; omit name to list the available schema keys. Returns the schema document and its version. Contract discovery only: it does not validate data, fill in a template, or verify factual truth.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Schema key, file name, or bare stem. Omit to list all available schema names. |
No output schema declared.
No examples provided.
get_signal ~85
Return one packaged strategic-risk signal markdown file by ID. Use after list_signals when an agent needs the full text of a specific archived signal for context or examples. Pass signal_id without the .md extension. Returns static markdown from the installed package; it does not fetch live updates.
| Name | Type | Req | Description |
|---|---|---|---|
| signal_id | string | yes | Signal identifier returned by list_signals, without a file extension. |
No output schema declared.
No examples provided.
grounded_check ~187
Check whether a caller-supplied corpus of source texts lexically supports each claim. Use when you have claims plus the full text of the sources they should rest on and need a deterministic grounded/weakly_grounded/ungrounded verdict per claim before human review. Pass request_json matching grounded-check-request.schema.json (claims with claim_id/claim_text and optional verbatim quotes, corpus documents with corpus_id/text). Returns per-claim grounding status, coverage, best-matching passage, unmatched numeric values, quote checks, and owner actions. Local-text only: no outbound requests, no source discovery, no source-reliability scoring, and no factual-truth verification — grounding in a wrong corpus does not make a claim true.
| Name | Type | Req | Description |
|---|---|---|---|
| request_json | object | yes | Grounded-check request: claims (claim_id, claim_text, optional quotes) plus corpus documents (corpus_id, text). |
No output schema declared.
No examples provided.
gulf_maritime_exposure ~209
Triage maritime sanctions and chokepoint-disruption exposure for a vessel/voyage transiting the Strait of Hormuz, Persian/Arabian Gulf, Gulf of Oman, Bab-el-Mandeb, or Red Sea (Iran-oil, Russia price-cap, dark-fleet, STS transfer, flag-hopping, P&I gap, AIS manipulation). Pass a structured exposure_request (vessel/voyage, route, cargo, counterparties, dated_sources, risk_question, decision_stage) matching gulf-maritime-exposure-request.schema.json. Returns a triage recommendation, exposure signal, decision-readiness score, supplied vs. minimum-required sources, and evidence gaps. Pre-compliance evidence triage only: no live retrieval, does not resolve vessel ownership or verify identity, no legal or sanctions advice; human review is required.
| Name | Type | Req | Description |
|---|---|---|---|
| exposure_request | object | yes | Structured Gulf maritime exposure request. Call get_schema('gulf_maritime_exposure_request') for the full nested contract. |
No output schema declared.
No examples provided.
kazakhstan_market_entry_readiness ~172
Grade a Kazakhstan market-entry file (distribution, import, service, showroom, EPC, renewable-energy, infrastructure, technology-transfer, or partner-entry) against a staged source-requirement taxonomy before a launch, budget, or partner commitment. Pass a structured readiness_request (entry_mode, sector, market_entry_file, dated_sources, decision_stage) matching market-entry-readiness-request.schema.json. Returns a gate decision, readiness label, evidence gaps, claim audit, owner actions, and watch-next indicators. Evidence triage only: not legal, compliance, customs, tax, sanctions, or launch-authorization advice; no live retrieval; human review is required.
| Name | Type | Req | Description |
|---|---|---|---|
| readiness_request | object | yes | Structured Kazakhstan market-entry readiness request. Call get_schema('market_entry_readiness_request') for the full nested contract. |
No output schema declared.
No examples provided.
list_lenses ~95
List packaged regional and sector lens IDs available to Agenda Intelligence. Use before get_lens when an agent needs to discover which geography or sector reference packs can be loaded. Optionally filter by lens_type='regional' or 'sector'. Returns metadata only; it does not return full lens markdown or run analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| lens_type | string | – | Optional filter. Use 'regional' for geography lenses or 'sector' for sector lenses. |
No output schema declared.
No examples provided.
list_signals ~70
List packaged strategic-risk signal records vendored from Global Think Tank Analyst. Use to discover available signal IDs before calling get_signal, or to show a static archive index inside an agent workflow. Returns the packaged signals/index.json snapshot. Read-only and offline: it does not fetch live news or update the archive.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_source_categories ~65
List source requirement category slugs packaged with Agenda Intelligence. Use this first when you do not know which category to pass to source_plan or source_coverage. Returns category IDs and per-pack counts. Discovery only: it does not discover sources, validate coverage, or verify factual truth.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
middle_corridor_deal_risk ~183
Screen a Kazakhstan / Middle Corridor (Trans-Caspian) trade deal for sanctions-adjacent and corridor risk before signature, shipment, insurer handoff, or committee review. Pass a structured deal_risk_request (route, cargo, counterparties, dated_sources, risk_question, decision_stage) matching middle-corridor-deal-risk-request.schema.json. Returns a triage recommendation, risk signal, decision-readiness score, supplied vs. minimum-required source categories, evidence gaps, and a high-risk-jurisdiction presence flag. Pre-compliance evidence triage only: no live retrieval, no factual-truth verification, no legal or sanctions advice; human review is required.
| Name | Type | Req | Description |
|---|---|---|---|
| deal_risk_request | object | yes | Structured Middle Corridor deal-risk request. Call get_schema('middle_corridor_deal_risk_request') for the full nested contract. |
No output schema declared.
No examples provided.
pre_action_check ~110
Route a caller-controlled action to continue, request_evidence, require_approval, or stop using caller-supplied claim evidence, risk tier, policy checks, and an optional external approval reference. Resubmit the same run_id after adding evidence or approval. Readiness only: the tool does not authenticate, authorize, enforce, persist state, or perform the action.
| Name | Type | Req | Description |
|---|---|---|---|
| action_request | object | yes | Structured pre-action check request. Call get_schema('pre_action_check_request') for the full nested contract. |
No output schema declared.
No examples provided.
score_output ~115
Score a before/after pair of agenda-analysis text with the bundled heuristic rubric. Use in evals or demos to compare whether an Agenda Intelligence rewrite improved structure, evidence labeling, uncertainty handling, and decision-readiness. Pass before_text and after_text as plain strings. Returns a heuristic score and breakdown; it is not a factuality, legal, compliance, or investment judgment.
| Name | Type | Req | Description |
|---|---|---|---|
| after_text | string | yes | Revised analysis text to score against the protocol rubric. |
| before_text | string | yes | Original analysis text before Agenda Intelligence processing. |
No output schema declared.
No examples provided.
source_coverage ~116
Diagnose whether an evidence pack covers the must_check source types for a category. Use after collecting evidence to find source gaps before relying on a memo. Pass evidence_json and optionally category; if category is omitted, the tool uses evidence_json.source_category. Returns matched and missing source types. It does not discover new sources, verify truth, or change validate_evidence results.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional source requirement category slug; overrides evidence_json.source_category. |
| evidence_json | object | yes | Parsed evidence pack to compare against source requirements. |
No output schema declared.
No examples provided.
source_plan ~112
Return required source categories for a strategic-risk evidence pack. Use before collection or review to know which source types should be checked for a domain such as sanctions, elections, conflict, cyber, or energy. Pass the source category slug as category. Returns a checklist of must_check and optional source types; it does not search the web, fetch documents, or validate an evidence pack.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Source requirement category slug, for example sanctions, elections, or energy. Call list_source_categories for the full set. |
No output schema declared.
No examples provided.
validate_brief ~93
Validate a caller-provided agenda brief against agenda-brief.schema.json. Use before running scoring, evidence audit, or publication steps to catch missing sections and schema drift. Pass the parsed brief object as brief_json. Returns validation status and schema errors only; it does not judge factual truth, retrieve sources, or improve the brief.
| Name | Type | Req | Description |
|---|---|---|---|
| brief_json | object | yes | Parsed agenda brief JSON object to validate against the bundled schema. |
No output schema declared.
No examples provided.
validate_evidence ~98
Validate a caller-provided evidence pack against evidence-pack.schema.json. Use when you need to confirm that claims, evidence IDs, provenance fields, and optional source_category metadata are structurally usable by Agenda Intelligence. Pass the parsed evidence pack as evidence_json. Returns schema validity and errors; it does not verify whether evidence is true, current, or sufficient.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_json | object | yes | Parsed evidence-pack JSON object to validate against the bundled schema. |
No output schema declared.
No examples provided.
validate_memo ~89
Validate an Agenda memo against agenda-memo.schema.json. Use after a host model or external process drafts a memo and before treating it as an Agenda Intelligence artifact. Pass the parsed memo as memo_json. Returns validity and schema errors; it does not score truthfulness, retrieve sources, or rewrite the memo.
| Name | Type | Req | Description |
|---|---|---|---|
| memo_json | object | yes | Parsed Agenda memo JSON object to validate against the output schema. |
No output schema declared.
No examples provided.
verify_claims ~116
Issue a bounded factual Claim Verdict from caller-supplied evidence records. Evaluates freshness, authoritative source class, independent source groups, conflicts, jurisdiction, and exact subject identifiers as of a declared date. Returns verified, contradicted, partially_supported, unresolved, or not_verifiable. No source discovery or live retrieval; verified means the declared evidence threshold is met, not absolute truth. Human review remains required.
| Name | Type | Req | Description |
|---|---|---|---|
| request_json | object | yes | Claim verification request. Call get_schema('claim_verification_request') for the full nested contract. |
No output schema declared.
No examples provided.
verify_quotes ~171
Check whether quoted fragments appear in caller-provided source text. Use when you have local excerpts and need to catch citation drift or misquoted snippets. Accepts an evidence pack (sources/evidence items with a quote) or an evidence-audit doc with claims[].supporting_quotes; span checks carry the originating claim_id. Pass pack_json plus texts mapping evidence_id to plain text. Returns present, absent, and missing_source_text results. Local-text only: it does not make outbound requests, discover sources, score source reputation, gather news, or verify factual truth.
| Name | Type | Req | Description |
|---|---|---|---|
| pack_json | object | yes | Evidence pack (evidence IDs + quote fragments) or evidence-audit doc (claims with supporting_quotes) to check. |
| texts | object | – | Optional mapping from evidence_id to caller-provided plain source text. |
No output schema declared.
No examples provided.
What is the Agenda Intelligence MD MCP server?
Agenda Intelligence MD is an MCP server listed in the public MCP registry as io.github.vassiliylakhonin/agenda-intelligence-md. Evidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs. This page covers its PyPI package (agenda-intelligence-md).
Is the Agenda Intelligence MD MCP server safe to use?
Agenda Intelligence MD scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agenda Intelligence MD MCP server expose?
Agenda Intelligence MD exposes 32 tools: validate_brief, validate_evidence, check_evidence_packet, audit_claims, get_protocol, and 27 more. Their descriptions and schemas cost roughly 4,607 tokens of context every time the server is loaded.
Is the Agenda Intelligence MD MCP server still maintained?
Agenda Intelligence MD is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.