Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Meta Council

REMOTE · META-COUNCIL.COM · SCANNED SEP 22

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

Available components

0 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 24424 tokens (~136/item across 179 items; 179 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 150 breaking changes, 0 auth/transport breaks, 29 additions. See how to fix → Fail
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 41% of tool parameters carry a description.Partial
  • Structured output schemas are declared (6% of tools); any adoption earns full credit.Pass
Tool Safety97
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 7 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_saved_view" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 180 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
Install

How do I install the Meta Council MCP server?

Meta Council is a hosted endpoint at https://meta-council.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · meta-council.com

# add to Claude Code
claude mcp add --transport http com-meta-council-decision-intelligence 'https://meta-council.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-meta-council-decision-intelligence": {
      "url": "https://meta-council.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-meta-council-decision-intelligence": {
      "type": "http",
      "url": "https://meta-council.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-meta-council-decision-intelligence]
url = "https://meta-council.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-meta-council-decision-intelligence": {
      "type": "remote",
      "url": "https://meta-council.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-meta-council-decision-intelligence --url 'https://meta-council.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-meta-council-decision-intelligence:
    url: "https://meta-council.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-meta-council-decision-intelligence": {
      "Transport": "http",
      "Url": "https://meta-council.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-meta-council-decision-intelligence -t streamable-http -u 'https://meta-council.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-meta-council-decision-intelligence": {
      "type": "http",
      "url": "https://meta-council.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 22 Sept 26 0
    • Tool “create_scope_baseline” rewrote its description, which is the text the model reads security
    • Tool “get_scope_baseline” rewrote its description, which is the text the model reads security
    • Tool “get_ticket_burndown” rewrote its description, which is the text the model reads security
    • Tool “get_workflow_session” rewrote its description, which is the text the model reads security
    • Tool “run_workflow” rewrote its description, which is the text the model reads security
    • Tool “ticket_get” rewrote its description, which is the text the model reads security
    • The server now declares the “resources” capability functional
    • Server version: 2.6.0 → 2.11.0 functional
    • New tool “get_delivery_timeline” functional
    • New tool “get_feature_delivery_summary” functional
    • New tool “get_ticket_attention_policy” functional
    • New tool “get_ticket_attention_queue” functional
    • New tool “get_ticket_attention_review” functional
    • New tool “get_ticket_delivery_plan” functional
    • New tool “get_ticket_label_cohort” functional
    • New tool “get_ticket_label_history” functional
    • New tool “list_ticket_delivery_plan_history” functional
    • New tool “save_ticket_attention_policy” functional
    • New tool “save_ticket_attention_review” functional
    • New tool “save_ticket_delivery_plan” functional
    • New tool “ticket_comments” functional
    • “get_ticket_burndown” added an optional parameter “baseline_id” cosmetic
  • 21 Sept 26 0
    • Tool “execute_saved_view” rewrote its description, which is the text the model reads security
    • Tool “list_saved_views” rewrote its description, which is the text the model reads security
    • Server version: 2.5.0 → 2.6.0 functional
    • New tool “compare_scope_baseline” functional
    • New tool “create_scope_baseline” functional
    • New tool “get_scope_baseline” functional
    • New tool “list_scope_baselines” functional
    • New tool “plan_council” functional
    • “list_saved_views” added an optional parameter “cursor” cosmetic
    • “list_saved_views” reworded the description of “limit” cosmetic
  • 15 Sept 26 −7
    • Stability: pass → fail security
    • A breaking change shipped without a version bump: still 2.5.0 security
    • Tool “create_workflow_template” rewrote its description, which is the text the model reads security
    • Tool “update_workflow_template” rewrote its description, which is the text the model reads security
    • Tool coverage: 100% → 6% functional
    • Tool “account_export” dropped its output schema functional
    • Tool “add_invoice_line_item” dropped its output schema functional
    • Tool “add_outreach_lead” dropped its output schema functional
    • Tool “advance_workflow” dropped its output schema functional
    • Tool “approve_consulting_deliverable” dropped its output schema functional
    • Tool “approve_consulting_document_revision” dropped its output schema functional
    • Tool “approve_content_asset” dropped its output schema functional
    • Tool “archive_saved_view” dropped its output schema functional
    • Tool “ask_legal” dropped its output schema functional
    • Tool “assign_leads_to_campaign” dropped its output schema functional
    • Tool “audit_export” dropped its output schema functional
    • Tool “campaign_pipeline_stats” dropped its output schema functional
    • Tool “complete_sales_task” dropped its output schema functional
    • Tool “convert_deal_to_invoice” dropped its output schema functional
    • Tool “convert_lead_to_deal” dropped its output schema functional
    • Tool “create_accounting_run” dropped its output schema functional
    • Tool “create_consulting_client” dropped its output schema functional
    • Tool “create_consulting_deliverable” dropped its output schema functional
    • Tool “create_consulting_document_revision” dropped its output schema functional
    • Tool “create_consulting_engagement” dropped its output schema functional
    • Tool “create_content_asset” dropped its output schema functional
    • Tool “create_content_asset_revision” dropped its output schema functional
    • Tool “create_deal” dropped its output schema functional
    • Tool “create_invoice” dropped its output schema functional
    • Tool “create_marketing_audience” dropped its output schema functional
    • Tool “create_marketing_brand” dropped its output schema functional
    • Tool “create_marketing_campaign” dropped its output schema functional
    • Tool “create_monitor” dropped its output schema functional
    • Tool “create_outreach_campaign” dropped its output schema functional
    • Tool “create_outreach_pitch” dropped its output schema functional
    • Tool “create_portfolio_snapshot” dropped its output schema functional
    • Tool “create_portfolio_snapshot_note” dropped its output schema functional
    • Tool “create_saved_view” dropped its output schema functional
    • Tool “create_workflow_template” dropped its output schema functional
    • Tool “decide_approval” dropped its output schema functional
    • Tool “delete_accounting_run” dropped its output schema functional
    • Tool “delete_monitor” dropped its output schema functional
    • Tool “delete_saved_view” dropped its output schema functional
    • Tool “delete_workflow_template” dropped its output schema functional
    • Tool “diff_portfolio_snapshots” dropped its output schema functional
    • Tool “draft_outreach_email” dropped its output schema functional
    • Tool “estimate_cost” dropped its output schema functional
    • Tool “execute_saved_view” dropped its output schema functional
    • Tool “get_accounting_run” dropped its output schema functional
    • Tool “get_agent_detail” dropped its output schema functional
    • Tool “get_api_key_info” dropped its output schema functional
    • Tool “get_consulting_engagement” dropped its output schema functional
    • Tool “get_content_asset” dropped its output schema functional
    • Tool “get_content_calendar” dropped its output schema functional
    • Tool “get_deal” dropped its output schema functional
    • Tool “get_deal_health” dropped its output schema functional
    • Tool “get_invoice” dropped its output schema functional
    • Tool “get_invoice_aging” dropped its output schema functional
    • Tool “get_marketing_audience” dropped its output schema functional
    • Tool “get_marketing_brand” dropped its output schema functional
    • Tool “get_marketing_campaign” dropped its output schema functional
    • Tool “get_meta_council_platform_metrics” dropped its output schema functional
    • Tool “get_portfolio_snapshot” dropped its output schema functional
    • Tool “get_sales_analytics” dropped its output schema functional
    • Tool “get_sales_recommendations” dropped its output schema functional
    • Tool “get_saved_view” dropped its output schema functional
    • Tool “get_session” dropped its output schema functional
    • Tool “get_settings” dropped its output schema functional
    • Tool “get_site_analytics” dropped its output schema functional
    • Tool “get_ticket_burndown” dropped its output schema functional
    • Tool “get_ticket_projects” dropped its output schema functional
    • Tool “get_visualization” dropped its output schema functional
    • Tool “get_workflow_session” dropped its output schema functional
    • Tool “get_workspace_metrics” dropped its output schema functional
    • Tool “initialize_consulting_milestones” dropped its output schema functional
    • Tool “list_accounting_runs” dropped its output schema functional
    • Tool “list_agents” dropped its output schema functional
    • Tool “list_approvals” dropped its output schema functional
    • Tool “list_campaign_replies” dropped its output schema functional
    • Tool “list_campaign_triggers” dropped its output schema functional
    • Tool “list_consulting_clients” dropped its output schema functional
    • Tool “list_consulting_engagements” dropped its output schema functional
    • Tool “list_content_assets” dropped its output schema functional
    • Tool “list_deals” dropped its output schema functional
    • Tool “list_integrations” dropped its output schema functional
    • Tool “list_invoices” dropped its output schema functional
    • Tool “list_marketing_audiences” dropped its output schema functional
    • Tool “list_marketing_brands” dropped its output schema functional
    • Tool “list_marketing_campaigns” dropped its output schema functional
    • Tool “list_meta_council_feedback” dropped its output schema functional
    • Tool “list_monitors” dropped its output schema functional
    • Tool “list_outreach_campaigns” dropped its output schema functional
    • Tool “list_panels” dropped its output schema functional
    • Tool “list_portfolio_snapshot_notes” dropped its output schema functional
    • Tool “list_portfolio_snapshots” dropped its output schema functional
    • Tool “list_sales_tasks” dropped its output schema functional
    • Tool “list_saved_views” dropped its output schema functional
    • Tool “list_workflows” dropped its output schema functional
    • Tool “locus_determine_from_scores” dropped its output schema functional
    • Tool “log_deal_activity” dropped its output schema functional
    • Tool “mark_invoice_paid” dropped its output schema functional
    • Tool “mint_child_api_key” dropped its output schema functional
    • Tool “outreach_analytics” dropped its output schema functional
    • Tool “plan_workflow” dropped its output schema functional
    • Tool “preview_accounting_ticket_sync” dropped its output schema functional
    • Tool “recommend_panel” dropped its output schema functional
    • Tool “reject_content_asset” dropped its output schema functional
    • Tool “reopen_consulting_deliverable” dropped its output schema functional
    • Tool “restore_saved_view” dropped its output schema functional
    • Tool “retry_workflow” dropped its output schema functional
    • Tool “rotate_api_key” dropped its output schema functional
    • Tool “run_council” dropped its output schema functional
    • Tool “run_workflow” dropped its output schema functional
    • Tool “score_locus_case” dropped its output schema functional
    • Tool “search_outreach_leads” dropped its output schema functional
    • Tool “send_invoice” dropped its output schema functional
    • Tool “share_saved_view” dropped its output schema functional
    • Tool “submit_consulting_deliverable” dropped its output schema functional
    • Tool “submit_content_asset” dropped its output schema functional
    • Tool “submit_meta_council_feedback” dropped its output schema functional
    • Tool “sync_accounting_tickets” dropped its output schema functional
    • Tool “test_workflow_step” dropped its output schema functional
    • Tool “ticket_archive” dropped its output schema functional
    • Tool “ticket_batch_create” dropped its output schema functional
    • Tool “ticket_claim” dropped its output schema functional
    • Tool “ticket_comment” dropped its output schema functional
    • Tool “ticket_create” dropped its output schema functional
    • Tool “ticket_dependency_add” dropped its output schema functional
    • Tool “ticket_dependency_list” dropped its output schema functional
    • Tool “ticket_dependency_remove” dropped its output schema functional
    • Tool “ticket_get” dropped its output schema functional
    • Tool “ticket_list” dropped its output schema functional
    • Tool “ticket_plan” dropped its output schema functional
    • Tool “ticket_readiness” dropped its output schema functional
    • Tool “ticket_scenario_create” dropped its output schema functional
    • Tool “ticket_scenario_list” dropped its output schema functional
    • Tool “ticket_scenario_revise” dropped its output schema functional
    • Tool “ticket_update” dropped its output schema functional
    • Tool “ticket_validation_finalize” dropped its output schema functional
    • Tool “triage_meta_council_feedback” dropped its output schema functional
    • Tool “unshare_saved_view” dropped its output schema functional
    • Tool “update_consulting_client” dropped its output schema functional
    • Tool “update_consulting_deliverable” dropped its output schema functional
    • Tool “update_consulting_document_revision” dropped its output schema functional
    • Tool “update_consulting_engagement” dropped its output schema functional
    • Tool “update_consulting_milestone” dropped its output schema functional
    • Tool “update_content_asset” dropped its output schema functional
    • Tool “update_deal” dropped its output schema functional
    • Tool “update_invoice” dropped its output schema functional
    • Tool “update_marketing_audience” dropped its output schema functional
    • Tool “update_marketing_brand” dropped its output schema functional
    • Tool “update_marketing_campaign” dropped its output schema functional
    • Tool “update_outreach_lead_status” dropped its output schema functional
    • Tool “update_saved_view” dropped its output schema functional
    • Tool “update_workflow_template” dropped its output schema functional
    • Tool “void_invoice” dropped its output schema functional
    • “advance_workflow” added an optional parameter “expected_execution_seq” cosmetic
    • “advance_workflow” added an optional parameter “expected_step_id” cosmetic
  • 11 Sept 26 0
    • Tool “create_accounting_run” rewrote its description, which is the text the model reads security
    • New tool “get_business_suite_overview” functional
    • “create_accounting_run” added an optional parameter “duplicate_resolutions” cosmetic
    • “plan_workflow” added an optional parameter “step_models” cosmetic
    • “run_workflow” added an optional parameter “step_models” cosmetic
  • 10 Sept 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • Tool “create_accounting_run” rewrote its description, which is the text the model reads security
    • “convert_lead_to_deal” reworded the description of “currency” cosmetic
    • “create_deal” reworded the description of “currency” cosmetic
    • “create_invoice” reworded the description of “currency” cosmetic
  • 26 Aug 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 25 Aug 26 +1

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 24 Aug 26 86

    First indexed and scored.

Diagnostics

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 22 Sept 2026 · Probed https://meta-council.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=meta-council.com CN=YE1,O=Let's Encrypt,C=US 25 Jul 2026 23 Oct 2026 ECDSA 256 ECDSA-SHA384 67d6b0bfd327a02a47bbae22d691b7df572
SANs: *.meta-council.com, meta-council.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of meta-council.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
meta-council.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="meta-council"

Bearer realm="meta-council"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self'; frame-src https://js.stripe.com https://hooks.stripe.com https://challenges.cloudflare.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(), browsing-topics=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=(), midi=(), serial=()

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://meta-council.com/mcp Verified 200
http (plaintext) http://meta-council.com/mcp HTTPS enforced 301 https://meta-council.com/mcp
MCP tools · 179 exposed · ~24,350 tokens

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 →

Tool Tokens
get_content_asset ~39

Get one owned content revision, including its review state and exact content hashes.

NameTypeReqDescription
asset_idstringyesFull UUID from the matching list tool.

No output schema declared.

No examples provided.

get_content_calendar ~43

List scheduled owned content between optional ISO-8601 boundaries. Scheduling is planning metadata, not publishing.

NameTypeReqDescription
endstring
startstring

No output schema declared.

No examples provided.

get_deal ~48

Fetch one of the caller's deals by id with its full activity timeline (notes, calls, meetings, emails, tasks; newest first).

NameTypeReqDescription
deal_idstringyesThe deal id.

No output schema declared.

No examples provided.

get_deal_health ~134

Health scores for the caller's OPEN deals: each scored 0-100 on how likely it is to be slipping (healthy >= 70 / watch / at_risk), worst first, with plain-language reasons — days since last logged contact, whether it is past its own expected close date, and how its age compares to the caller's average won-deal cycle. Includes per-band counts, an average score, and the reference cycle. Read-only and deterministic over the caller's own deals + activities; nothing is executed or sent. Pair with get_sales_recommendations to act on what is slipping. Requires authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_delivery_timeline ~118

Read a delivery group planned/actual timeline and optional frozen-baseline variance, plus explanatory dependency risks. Unknown dates/history are not inferred. Bounded to 10,001 owned tickets (10,000 work tickets plus a root); pages of 1–500, default200. Critical path only for supported complete calendar/duration graphs; no dates move. Requires tickets:read.

NameTypeReqDescription
after_ticket_idstring
baseline_idstring
limitinteger
root_idstringyes

No output schema declared.

No examples provided.

get_feature_delivery_summary ~72

Read one owned feature epic's task completion, estimate coverage, ledger-based weekly flow, lead/cycle evidence, risks and evidence-gated throughput scenario. Current task cohort only; no historical membership or planned timeline. Requires tickets:read.

NameTypeReqDescription
root_idstringyes
weeksinteger

No output schema declared.

No examples provided.

get_invoice ~34

Fetch one of the caller's invoices by id, including its line items.

NameTypeReqDescription
invoice_idstringyesThe invoice id.

No output schema declared.

No examples provided.

get_invoice_aging ~72

Summarize the caller's unpaid invoices by how long they have been past due. This owner-scoped, read-only report is computed live; an invoice is overdue only when its status is sent and its due_date is before today. Balances are separated by currency, with no conversion or combined money total.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_marketing_audience ~37

Get one owned audience definition with pain points and channels.

NameTypeReqDescription
audience_idstringyesFull UUID from the matching list tool.

No output schema declared.

No examples provided.

get_marketing_brand ~40

Get one owned brand identity with its voice, value proposition, and guidelines.

NameTypeReqDescription
brand_idstringyesFull UUID from the matching list tool.

No output schema declared.

No examples provided.

get_marketing_campaign ~41

Get one owned marketing campaign with its brand, audience, channels, and dates.

NameTypeReqDescription
campaign_idstringyesFull UUID from the matching list tool.

No output schema declared.

No examples provided.

get_meta_council_platform_metrics ~196

OPERATOR ONLY: cross-owner analytics for the META COUNCIL PLATFORM itself — every account added together, NOT the caller's workspace (use get_workspace_metrics for that). Requires both the platform:admin scope AND an ADMIN_EMAILS operator account; everyone else gets a permission error. Returns content-free aggregates only: account counts, 30-day active owners, session counts by status and token totals, ticket open/done, deal pipeline and outstanding invoice amounts separated by recorded currency without FX conversion and with missing coverage stated, overdue invoice counts, feedback backlog, per-pillar adoption, the busiest panel slugs, and a per-account activity table (email and counts). It never returns query text, answers, feedback bodies, deal or invoice detail, or any other text a user typed — the aggregate reports how much, never what about. Note that open + done need not equal the ticket total: cancelled tickets are neither.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_portfolio_snapshot ~113

Fetch one portfolio snapshot by id: its label, schema version, the exact stored rollup payload, its content hash, who recorded it and when. The payload is served from storage and is never recomputed from live tickets, so a snapshot read today reports what was true when it was taken. A snapshot you do not own is reported as not found rather than as forbidden. Requires authentication and the tickets:read scope.

NameTypeReqDescription
snapshot_idstringyesThe snapshot's id, from list_portfolio_snapshots.

No output schema declared.

No examples provided.

get_sales_analytics ~73

Sales pipeline analytics for the caller: probability-weighted forecast, per-stage $ rollup, win rate (won / decided, by count and by value), average sales-cycle days over won deals, and open-deal aging with a stale count. Read-only; computed from the caller's own deals. Requires authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_sales_recommendations ~111

The caller's prioritized next-best sales actions: interested leads to convert, open deals gone stale enough to need a follow-up, and overdue tasks — each with a rationale and the exact governed tool to run next (convert_lead_to_deal / log_deal_activity / complete_sales_task) plus its arguments. Read-only; ranks the caller's own CRM data (overdue > convert > follow-up). Nothing is executed or sent — approve an item by calling the named write tool. Requires authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_saved_view ~109

Fetch one saved ticket view's definition by id: its name, filters, columns, grouping, sort and whether it is shared. This returns the view itself, not the tickets it selects -- use execute_saved_view to run it. A view you cannot read is reported as not found rather than as forbidden, so this cannot be used to discover that someone else's view exists. Requires authentication and the tickets:read scope.

NameTypeReqDescription
view_idstringyesThe view's id, from list_saved_views.

No output schema declared.

No examples provided.

get_scope_baseline ~45

Read frozen structural scope, estimates and captured explicit plans for an owned baseline. Older schema1 dates remain unknown. Requires tickets:read.

NameTypeReqDescription
baseline_idstringyes

No output schema declared.

No examples provided.

get_session ~40

Get the full results of a previous Meta Council session, including all agent opinions and the synthesis.

NameTypeReqDescription
session_idstringyesThe session ID to retrieve

No output schema declared.

No examples provided.

get_settings ~64

Get the authenticated user's Meta Council settings — preferred model, plan tier, which credentials are saved (not live-verified), and the registry-backed tools that require, optionally use, or do not use account credentials. Names and booleans only, never secret values. Requires authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_site_analytics ~226

OPERATOR ONLY: visitor traffic for the META COUNCIL PLATFORM's own website — every visitor added together, NOT the caller's workspace (use get_workspace_metrics for that) and NOT the business rollup (use get_meta_council_platform_metrics for that). Requires both the platform:admin scope AND an ADMIN_EMAILS operator account; everyone else gets a permission error naming which of the two requirements failed. Covers a window of whole UTC days ending today, set by days. Returns total views, unique visitors, the authenticated/anonymous split, the busiest public paths, the busiest in-app sections, top referrers and a per-day series, plus the window it covers so the caller need not track what it asked for. Page paths and in-app sections are counted separately and are not comparable to one another. It never returns per-visitor rows, email addresses, IP hashes, user agents, session identifiers or query text — the rollup reports how many, never who.

NameTypeReqDescription
daysintegerWhole UTC days to cover, ending today. Defaults to 7.

No output schema declared.

No examples provided.

get_ticket_attention_policy ~75

Read the owner-private effective attention policy, built-in defaults, applicable statuses and immutable history. Requires tickets:read. limit 1–50 (default 20); exclusive before_revision. Earlier unrecorded history is unknown. No writes or providers.

NameTypeReqDescription
before_revisioninteger
limitinteger

No output schema declared.

No examples provided.

get_ticket_attention_queue ~154

Read the same ranked Needs attention queue as the browser and REST. Returns complete JSON with reasons, UTC clock evidence, effective owner policy thresholds and revision, approximation flags, unmet prerequisites and suggested next actions. Open active owned tickets only; limit 1–500 (default 100), with total_flagged and truncated. Filter reason to find current epic completion blockers or one elapsed-clock reason before the limit. Completion blockers reuse current readiness and have no known age or threshold. Ranked by greatest known days over threshold, then ticket UUID; items with no elapsed clock sort last. No state changes, acknowledgments, notifications or provider calls. Requires tickets:read.

NameTypeReqDescription
limitinteger
reasonstring

No output schema declared.

No examples provided.

get_ticket_attention_review ~108

Read the owner-private current attention assessment, latest review and immutable history. Requires tickets:read. History uses limit 1–50 (default 20) and exclusive before_revision; stays readable after ticket closure/archive/deletion. Evidence-changed and follow-up-due are separate states. Dates become due at start of their recorded IANA calendar day. No writes or providers.

NameTypeReqDescription
before_revisioninteger
limitinteger
ticket_idstringyes

No output schema declared.

No examples provided.

get_ticket_burndown ~215

Daily burndown series replayed from the append-only ticket ledger: per-day scope (existing, non-cancelled), remaining, done levels plus added/completed flows, with a summary. Optionally scope to one epic's current subtree via root_id. Backfill (legacy_snapshot) rows seed state but never count as additions. days clamps to 7-180 (default 30). Optionally pass target_date to overlay a straight-line plan: an ideal series descending from the window-start remaining to zero on that date, for reading actual against plan. Alternatively pass baseline_id for exact frozen-task planned/actual JSON with coverage; this uses the same cohort and excludes epic estimates and later additions.

NameTypeReqDescription
baseline_idstring
daysinteger
root_idstring
target_datestringOptional plan-line end date, YYYY-MM-DD. Must be strictly after the window start. Omitting it leaves the output exactly as it is without a plan line.

No output schema declared.

No examples provided.

get_ticket_delivery_plan ~47

Read the explicit dated plan of an owned ticket, including archived or retained deleted-ticket plans. Absent plans remain unknown. Requires tickets:read.

NameTypeReqDescription
ticket_idstringyes

No output schema declared.

No examples provided.

get_ticket_label_cohort ~99

Report a fixed cohort holding one exact label at the UTC window start, observed daily task completions/reopens, status and point coverage. Today's labels never rewrite history. end_date is exclusive; default today UTC. Bounded cursor pagination; unknown history is disclosed.

NameTypeReqDescription
cursorstring
daysinteger
end_datestring
labelstringyes
limitinteger

No output schema declared.

No examples provided.

get_ticket_label_history ~65

Read immutable owner-private observed label assignments/removals, revision bindings and legacy limits. Retains deleted tickets. Bounded cursor pagination; no provider or ticket changes.

NameTypeReqDescription
cursorstring
limitinteger
ticket_idstringyes

No output schema declared.

No examples provided.

get_ticket_projects ~99

Projects overview of the caller's board: one entry per top-level epic with recursive descendant progress (done %, counts by status, blocked, points, sub-epics, last activity), plus a triage strip of unrouted work (backlog + unassigned root tickets). Read-only, recomputed live. Use this before planning a session to see initiative health at a glance; use ticket_list/ticket_get to drill into any id it returns.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_visualization ~116

Fetch a chart artifact generated by a council session or LOCUS determination. Returns the machine-readable spec (the data behind the chart) plus the stable SVG URL, or the raw SVG itself with include_svg=true. Artifact ids appear in session results as 'visualizations' / 'visualization' reference blocks. Requires authentication and enforces the artifact owner's tenant boundary.

NameTypeReqDescription
artifact_idstringyes32-hex artifact id from a visualization reference
include_svgbooleanAlso return the full SVG markup (default false)

No output schema declared.

No examples provided.

get_workflow_session ~88

Poll a previously started workflow run for its current step-by-step status and output (useful when run_workflow timed out or is awaiting a checkpoint). Also returns that run's definition_sha — the fingerprint of the definition it resolved when it started, comparable against the one plan_workflow reported. Requires authentication.

NameTypeReqDescription
session_idstringyesThe workflow session ID returned by run_workflow.

No output schema declared.

No examples provided.

get_workspace_metrics ~246

One cross-domain rollup of the caller's own workspace: council sessions (total, last 30 days, by status, tokens), feedback ratings, tickets (open/done), deals (count by stage, open pipeline value) and invoices (count by status, outstanding total, overdue count). Read-only, recomputed live, and scoped to the caller — it never aggregates across accounts. Amounts are labelled and grouped by recorded currency, never converted or added across currencies; unavailable currency or amount coverage is stated explicitly. Use it for a single 'how is this workspace doing' answer instead of calling the per-domain analytics tools one by one; use those (get_sales_analytics, get_ticket_projects, list_invoices) to drill into whatever this surfaces. Counts of unrecognised stages or statuses are reported under 'unknown' rather than dropped, so each breakdown sums to its own total. Note that open + done need not equal the ticket total: cancelled tickets are neither. Invoice overdue status is computed at read time by comparing due dates against now, not stored on the record, so it is current as of this call and an invoice due today does not yet count as overdue.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

initialize_consulting_milestones ~46

Idempotently initialize stable engagement milestones. Retries return the same ids and external refs.

NameTypeReqDescription
engagement_idstringyes
milestonesarray

No output schema declared.

No examples provided.

list_accounting_runs ~55

List only the caller's private Accounting-run audit metadata, newest first. Raw source text and analysis results are intentionally omitted.

NameTypeReqDescription
limitinteger
offsetinteger
statusstring

No output schema declared.

No examples provided.

list_agents ~46

List all available expert agents with their roles, domains, and specialties.

NameTypeReqDescription
domainstringFilter agents by domain (e.g., 'finance', 'technology', 'healthcare')

No output schema declared.

No examples provided.

list_approvals ~72

List workflow checkpoints waiting on you, soonest deadline first, with which step is paused and when it runs out. Defaults to the pending ones. Requires authentication and the workflows:read scope.

NameTypeReqDescription
statusstringWhich lifecycle status to list. Defaults to pending -- the ones still waiting for an answer.

No output schema declared.

No examples provided.

list_campaign_replies ~100

List sent / received emails for an outreach campaign, newest first — subject, body preview, and reply classification. Requires authentication.

NameTypeReqDescription
campaign_idstringyesCampaign UUID (from list_outreach_campaigns).
directionstring'inbound' (replies from prospects — the default), 'outbound' (sent), or '' for all.
limitintegerMax rows (default 50, max 200).

No output schema declared.

No examples provided.

list_campaign_triggers ~50

List automation triggers (auto-reply rules, status updates, notifications) configured for an outreach campaign. Requires authentication.

NameTypeReqDescription
campaign_idstringyesCampaign UUID (from list_outreach_campaigns).

No output schema declared.

No examples provided.

list_consulting_clients ~35

List consulting clients owned by the API-key account.

NameTypeReqDescription
limitinteger
statusstring

No output schema declared.

No examples provided.

list_consulting_engagements ~45

List consulting engagements owned by the API-key account.

NameTypeReqDescription
client_idstring
limitinteger
statusstring

No output schema declared.

No examples provided.

list_content_assets ~64

List owned content assets and immutable revisions; content is never published by this tool.

NameTypeReqDescription
approval_statestring
campaign_idstringFull UUID from the matching list tool.
include_archivedboolean
limitinteger

No output schema declared.

No examples provided.

list_deals ~78

List the caller's sales deals (newest first) together with a weighted pipeline forecast (open/weighted/won totals). Optionally filter by stage or lead_id. Deals are private to the API-key owner.

NameTypeReqDescription
lead_idstringOptional: only deals linked to this lead.
stagestringOptional stage filter.

No output schema declared.

No examples provided.

list_integrations ~95

List which outside services the authenticated user has connected — ticket boards, stored connector credentials (name, kind, whether configured, and when last verified) and the connectors available to call them. Returns configured / not configured facts, names and dates ONLY, and never returns a secret value. Read this before planning a workflow that reaches an external service, so a step is not written against a credential the user has not registered. Requires authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_invoices ~50

List the caller's invoices (newest first), optionally filtered by status (draft/sent/paid/void). Each entry includes its computed overdue flag.

NameTypeReqDescription
statusstringOptional status filter.

No output schema declared.

No examples provided.

list_marketing_audiences ~23

List reusable marketing audiences owned by the API-key account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_marketing_brands ~21

List brand identities owned by the API-key account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_marketing_campaigns ~40

List owned marketing campaigns. These are separate from Sales outreach campaigns.

NameTypeReqDescription
include_archivedboolean
statusstring

No output schema declared.

No examples provided.

list_meta_council_feedback ~92

ADMIN ONLY: list platform-feedback reports — feedback about Meta Council itself, never a tenant's own business data — across all users for triage (requires an ADMIN_EMAILS account; everyone else gets a permission error). Filter by status, category, or severity.

NameTypeReqDescription
categorystring
limitinteger
severitystring
statusstring

No output schema declared.

No examples provided.

list_monitors ~45

List the standing watches you have saved, newest first, with what each one watches, what it does, and when it last fired. Requires authentication and the monitors:read scope.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_outreach_campaigns ~29

List the authenticated user's outreach campaigns with live lead / sent / reply counts. Requires authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_panels ~21

List all available expert panels with their descriptions and agent counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Meta Council MCP server?

Meta Council is an MCP server listed in the public MCP registry as com.meta-council/decision-intelligence. Multi-expert decision intelligence with transparent synthesis and auditable workflows. This page covers its hosted endpoint (https://meta-council.com/mcp).

Is the Meta Council MCP server safe to use?

Meta Council scores 81 out of 100 on VerifyMCP. 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 Meta Council MCP server expose?

Meta Council exposes 179 tools: run_council, plan_council, list_panels, list_agents, get_session, and 174 more. Their descriptions and schemas cost roughly 24,350 tokens of context every time the server is loaded.

Does the Meta Council MCP server require authentication?

Yes. Meta Council asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Meta Council MCP server still maintained?

Meta Council is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.