Should my agent depend on the MCP server com.meta-council/decision-intelligence?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Meta Council

com.meta-council/decision-intelligence

Multi-expert decision intelligence with transparent synthesis and auditable workflows.

— the operator's own registry description reported

Publisher com.meta-council · first seen 2026-08-12 · endpoint https://meta-council.com/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

119

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.447 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency105 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools119

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_ae41222c7316afc818511056 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

add_invoice_line_item add_outreach_lead advance_workflow approve_consulting_deliverable approve_consulting_document_revision approve_content_asset ask_legal assign_leads_to_campaign campaign_pipeline_stats complete_sales_task convert_deal_to_invoice convert_lead_to_deal create_accounting_run create_consulting_client create_consulting_deliverable create_consulting_document_revision create_consulting_engagement create_content_asset create_content_asset_revision create_deal create_invoice create_marketing_audience create_marketing_brand create_marketing_campaign create_outreach_campaign create_outreach_pitch delete_accounting_run draft_outreach_email estimate_cost get_accounting_run get_agent_detail get_api_key_info get_consulting_engagement get_content_asset get_content_calendar get_deal get_deal_health get_invoice get_invoice_aging get_marketing_audience get_marketing_brand get_marketing_campaign get_meta_council_platform_metrics get_sales_analytics get_sales_recommendations get_session get_settings get_ticket_burndown get_ticket_projects get_visualization get_workflow_session get_workspace_metrics initialize_consulting_milestones list_accounting_runs list_agents list_campaign_replies list_campaign_triggers list_consulting_clients list_consulting_engagements list_content_assets list_deals list_invoices list_marketing_audiences list_marketing_brands list_marketing_campaigns list_meta_council_feedback list_outreach_campaigns list_panels list_sales_tasks list_workflows locus_determine_from_scores log_deal_activity mark_invoice_paid mint_child_api_key outreach_analytics preview_accounting_ticket_sync recommend_panel reject_content_asset reopen_consulting_deliverable rotate_api_key run_council run_workflow score_locus_case search_outreach_leads send_invoice submit_consulting_deliverable submit_content_asset submit_meta_council_feedback sync_accounting_tickets ticket_archive ticket_batch_create ticket_claim ticket_comment ticket_create ticket_dependency_add ticket_dependency_list ticket_dependency_remove ticket_get ticket_list ticket_plan ticket_scenario_create ticket_scenario_list ticket_scenario_revise ticket_update ticket_validation_finalize triage_meta_council_feedback update_consulting_client update_consulting_deliverable update_consulting_document_revision update_consulting_engagement update_consulting_milestone update_content_asset update_deal update_invoice update_marketing_audience update_marketing_brand update_marketing_campaign update_outreach_lead_status void_invoice

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	119/119	✓
has a description	119/119	✓
description is substantive	119/119	✓
parameters are typed	119/119	✓
parameters are described	51/119	51/119

119 of 119 tools graded · 119 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

2.5.0

server version meta-council

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-08-14	inventory	tools 106 → 119
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:18Z	ok_tools	200	105	2025-06-18
2026-08-12T05:33:34Z	ok_tools	200	136	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.meta-council/decision-intelligence.svg)](https://robinsaige.com/s/com.meta-council/decision-intelligence)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview