Meta Council
REMOTE · META-COUNCIL.COM · SCANNED SEP 22
Multi-expert decision intelligence with transparent synthesis and auditable workflows.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
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
claude mcp add --transport http com-meta-council-decision-intelligence 'https://meta-council.com/mcp'
{
"mcpServers": {
"com-meta-council-decision-intelligence": {
"url": "https://meta-council.com/mcp"
}
}
} {
"servers": {
"com-meta-council-decision-intelligence": {
"type": "http",
"url": "https://meta-council.com/mcp"
}
}
} [mcp_servers.com-meta-council-decision-intelligence] url = "https://meta-council.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-meta-council-decision-intelligence": {
"type": "remote",
"url": "https://meta-council.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-meta-council-decision-intelligence --url 'https://meta-council.com/mcp' --transport streamable-http
mcp_servers:
com-meta-council-decision-intelligence:
url: "https://meta-council.com/mcp" {
"McpServers": {
"com-meta-council-decision-intelligence": {
"Transport": "http",
"Url": "https://meta-council.com/mcp"
}
}
} assistant mcp add com-meta-council-decision-intelligence -t streamable-http -u 'https://meta-council.com/mcp'
{
"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.
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.
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 |
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 →
list_portfolio_snapshot_notes List Portfolio Snapshot Notes ~154
Read the decision and comment thread recorded against one of your portfolio snapshots, oldest first. Each note carries the snapshot content hash it was written against plus binding_intact comparing that hash to the snapshot's hash now, so a note can be read as evidence of what was actually on the screen when it was written. Counts are over the notes actually returned, so a truncated page never reports a total it did not show. This reads the thread; it does not approve, reject or block anything. Requires authentication and the tickets:read scope.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many notes to return. Defaults to 100. |
| snapshot_id | string | yes | The snapshot's id, from list_portfolio_snapshots. |
No output schema declared.
No examples provided.
list_portfolio_snapshots List Portfolio Snapshots ~105
List your own portfolio snapshots, newest first: the immutable rollups of how your ticket portfolio stood at the moments you captured them. Each carries its label, schema version, stored payload, content hash, recording actor and creation time. Snapshots are owner-private and never span accounts. Returns the same payload the web app's snapshot list returns. Requires authentication and the tickets:read scope.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many snapshots to return. Defaults to 50. |
No output schema declared.
No examples provided.
list_sales_tasks List Sales Tasks ~53
List the caller's open sales tasks (activities of type 'task' not yet done), bucketed overdue / today / upcoming and ordered most-urgent-first with per-bucket counts. Close one with complete_sales_task.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_saved_views List Saved Views ~208
List saved ticket views you can open: the stored filter, column, grouping and sort combinations saved by you, plus any shared with a team you belong to. Shared views appear under the active and all scopes and never once archived, because an owner's archive is their own working state. Returns the same payload the web app's saved-view list returns. Requires authentication and the tickets:read scope. Pages use immutable creation-time/ID order; follow next_cursor while has_more. Current permissions and archive state are rechecked on every page; this is live metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque next_cursor from the same caller and scope; expires after 24 hours. Omit to refresh. |
| limit | integer | – | How many views per page. Defaults to 50. |
| scope | string | – | Which of YOUR OWN views to include: active (the default, excluding archived), archived (your recovery list), or all. Shared views are unaffected by archived and never appear under it. |
No output schema declared.
No examples provided.
list_scope_baselines List Scope Baselines ~59
List saved baselines for an owned delivery group, newest first. Includes retained baselines after group deletion. Requires tickets:read.
| Name | Type | Req | Description |
|---|---|---|---|
| before_id | string | – | – |
| limit | integer | – | – |
| root_id | string | yes | – |
No output schema declared.
No examples provided.
list_ticket_delivery_plan_history List Ticket Delivery Plan History ~59
Read immutable plan revisions, newest first, including retained deleted-ticket history. Continue with next_before_version. Requires tickets:read.
| Name | Type | Req | Description |
|---|---|---|---|
| before_version | integer | – | – |
| limit | integer | – | – |
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
list_workflows List Workflows ~73
List available multi-step workflow pipelines (composable bundles that chain several steps, each able to run on its own model/provider). Returns each workflow's slug, description, per-step model, and definition_sha — a fingerprint of that definition as loaded right now, comparable against the definition_sha reported by a run you start later.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
locus_determine_from_scores Locus Determine From Scores ~354
Compute a LOCUS Level of Care from dimension ratings you already have. Deterministic — no LLM, instant: composite + Determination Grid + the inviolable override floors (e.g. Risk-of-Harm=4 → minimum Level 5), applied in code. Provide EITHER the seven flat D* ratings (1-5 each; Dimension IV splits into IV-A Stress / IV-B Support) OR a per-reviewer agent_scores map. Sending both is refused (422) rather than scored: agent_scores would win and your flat ratings would be discarded, override floors included. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| D1_RiskOfHarm | integer | – | Risk of Harm (1-5). |
| D2_FunctionalStatus | integer | – | Functional Status (1-5). |
| D3_CoMorbidity | integer | – | Medical/Addictive/Psychiatric Co-Morbidity (1-5). Capital M in CoMorbidity. |
| D4A_Stress | integer | – | Recovery Environment — Stress (1-5). |
| D4B_Support | integer | – | Recovery Environment — Support (1-5). |
| D5_TreatmentHistory | integer | – | Treatment & Recovery History (1-5). |
| D6_Engagement | integer | – | Engagement & Recovery Status (1-5). |
| agent_scores | object | – | Per-reviewer scores keyed by reviewer name, aggregated by median. Shape: {"<reviewer>": {"D1_RiskOfHarm": 4, ...}}. Mutually exclusive with the flat D* fields — sending both is refused (422), not mer… |
No output schema declared.
No examples provided.
log_deal_activity Log Deal Activity ~172
Log an activity on a deal (or lead) — a note/call/meeting/email, or a follow-up task with a due date. Pass deal_id and/or lead_id (each must be owned by the caller). type defaults to 'note'; for a task set type='task' and a due_date (YYYY-MM-DD). Tasks appear in list_sales_tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| deal_id | string | – | Owned deal to attach to. |
| done | boolean | – | Mark a task already done. |
| due_date | string | – | ISO date YYYY-MM-DD (for tasks). |
| lead_id | string | – | Owned lead to attach to. |
| subject | string | – | – |
| type | string | – | note|call|meeting|email|task (default note). |
No output schema declared.
No examples provided.
mark_invoice_paid Mark Invoice Paid ~44
Mark a draft or sent invoice as paid (stamps paid_at). Cannot be applied to a void invoice. invoice_id is required.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | – |
No output schema declared.
No examples provided.
mint_child_api_key Mint Child Api Key ~192
Mint a short-lived child API key for a delegated subtask. The child can never exceed the calling key: requested scopes must be a subset of what the caller holds, its expiry is capped by the caller's, and it may never itself mint keys (delegation is exactly one level deep). A caller whose own scopes were never recorded explicitly cannot delegate at all until it rotates first. The child key is returned exactly once in the response and cannot be retrieved again; revoking the parent immediately revokes the child. Requires the keys:mint scope.
| Name | Type | Req | Description |
|---|---|---|---|
| expires_in_minutes | integer | – | Child lifetime in minutes (default 60, maximum 1440). |
| name | string | – | Label for the child key (default 'delegated key'). |
| scopes | array | yes | Scopes to grant the child. Must be a subset of the calling key's own scopes and may not include keys:mint. |
No output schema declared.
No examples provided.
outreach_analytics Outreach Analytics ~29
Outreach summary for the user — total leads, sent, replied, and reply rate. Requires authentication.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_council Plan Council ~82
Resolve the effective Council models, parameters, tools, and setup reasons for this account without starting a session, calling a provider, or recording usage.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Optional model override for every Council agent |
| panel | string | – | Panel slug; omit to use the default panel |
| query | string | yes | The question used for panel selection |
No output schema declared.
No examples provided.
plan_workflow Plan Workflow ~272
Preview what a workflow WOULD do, without running it. Costs nothing and runs no models: returns the step execution order, each step's role/model/max_tokens and whether it pauses for a human checkpoint, the workflow's declared parameters (validated if you supply values), which required integrations your account already has credentials on file for, an upper-bound cost estimate, and definition_sha — a fingerprint of the definition this plan was built from, which tells you whether the definition changed between planning and running but never hands back the definition itself. Starts no session and records no usage. Use before run_workflow to check a pipeline fits before spending on it. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| parameters | object | – | Optional values for the workflow's declared parameters, as a flat name-to-value object, e.g. {"region": "EU"}. Supply them to have them validated; omit to skip validation. |
| step_models | object | – | Optional per-run model choices, keyed by zero-based step index (for example {"0": "claude-sonnet-4-6"}). Uses the same catalog validation as run_workflow; send the same choices when starting. Does no… |
| workflow | string | yes | The workflow slug (from list_workflows), e.g. 'due_diligence'. |
No output schema declared.
No examples provided.
preview_accounting_ticket_sync Preview Accounting Ticket Sync ~177
Preview, without writing, how one completed owned Accounting run's WRITEOff work plan would map to stable Meta Council tickets. Reports creates, updates, unchanged tickets, human-edited generated fields that will be preserved, and identity conflicts. Requires both accounting:read and tickets:read; tickets:write also satisfies the ticket-read grant. Preview before committing because tickets are not field-encrypted; work-plan text may reproduce source-derived snippets or parser details, and after commit tickets:read can read it without accounting:read. Check the item count before committing. Statement-derived runs currently plan one ticket per unclassified transaction line, so a several-hundred-row statement plans several hundred tickets. When the count is large, report it and confirm with the owner rather than committing a board-flooding sync.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | – |
No output schema declared.
No examples provided.
project_create Project Create ~77
Create an owner-private project with intent and goals. Persist request_id before calling; retry exact input after an uncertain response. Does not start work or create tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| goals | string | – | – |
| name | string | yes | – |
| repository_url | string | – | – |
| request_id | string | yes | – |
| summary | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| text | string | yes | – |
No examples provided.
project_document_create Project Document Create ~95
Save the first immutable project brief, PRD, technical specification or decision revision. Optional ticket_id scopes the document to a linked feature. reviewed is editorial metadata, never execution approval.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| kind | string | yes | – |
| project_id | string | yes | – |
| request_id | string | yes | – |
| status | string | – | – |
| ticket_id | – | – | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| text | string | yes | – |
No examples provided.
project_document_get Project Document Get ~58
Read one exact owned project document revision and its bounded revision history. Omit revision for latest; use explicit revision when recording evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| document_id | string | yes | – |
| project_id | string | yes | – |
| revision | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| text | string | yes | – |
No examples provided.
project_document_revise Project Document Revise ~115
Append an immutable document revision using expected_revision and a caller-retained request_id. Exact retry reconciles even after later edits; changed input or stale base conflicts. No provider execution or external publication.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| document_id | string | yes | – |
| expected_revision | integer | yes | – |
| kind | string | yes | – |
| project_id | string | yes | – |
| request_id | string | yes | – |
| status | string | – | – |
| ticket_id | – | – | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| text | string | yes | – |
No examples provided.
project_get Project Get ~49
Read project intent, current document IDs/revisions and linked feature epics. Read document bodies with project_document_get and follow ticket_get/ticket_list for execution work.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| text | string | yes | – |
No examples provided.
project_link_feature Project Link Feature ~64
Link an existing owned parentless epic to this project. Exact retry reuses the link; linking an epic already belonging to another project conflicts. Does not reparent, claim or execute the ticket.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| ticket_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| text | string | yes | – |
No examples provided.
project_list Project List ~28
List the account's overarching project workspaces, separate from feature epics. Requires tickets:read.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| text | string | yes | – |
No examples provided.
project_unlink_feature Project Unlink Feature ~68
Remove one exact project-feature placement, retaining the ticket. Read binding_id from project_get first; stale bindings or document references conflict. Does not delete tickets or documents.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_binding_id | string | yes | – |
| project_id | string | yes | – |
| ticket_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| text | string | yes | – |
No examples provided.
project_update Project Update ~92
Revision-safely edit project context. Supply expected_revision from project_get and a new request_id. Stale edits conflict instead of overwriting another agent.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_revision | integer | yes | – |
| goals | string | – | – |
| name | string | – | – |
| project_id | string | yes | – |
| repository_url | string | – | – |
| request_id | string | yes | – |
| summary | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| text | string | yes | – |
No examples provided.
recommend_panel Recommend Panel ~77
Recommend the best expert panel for a query (semantic match with keyword fallback). Returns the top panel + confidence and the runner-up options — feed the result into run_council's panel argument. Requires authentication because the query may be sent to the configured embedding provider.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The question or decision to match to a panel. |
No output schema declared.
No examples provided.
reject_content_asset Reject Content Asset ~46
Reject a submitted owned revision with optional reviewer notes. Requires marketing:approve.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Full UUID from the matching list tool. |
| notes | string | – | – |
No output schema declared.
No examples provided.
reopen_consulting_deliverable Reopen Consulting Deliverable ~34
Return an unapproved review deliverable to editable draft status.
| Name | Type | Req | Description |
|---|---|---|---|
| deliverable_id | string | yes | – |
No output schema declared.
No examples provided.
restore_saved_view Restore Saved View ~92
Return one of YOUR OWN archived saved views to the working set with its definition intact. Idempotent -- restoring a view that is already active is a no-op rather than an error. Use list_saved_views with scope=archived to find restorable views. Requires authentication and the tickets:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| view_id | string | yes | The view's id, from list_saved_views with scope=archived. |
No output schema declared.
No examples provided.
retry_workflow Retry Workflow ~148
Continue a stalled or finished workflow run from a chosen step. This starts a NEW run that reuses the outputs the original run already recorded and only executes — and only pays for — the steps from 'from_step' onward. The original run is left untouched and the new one records which run it continues. Omit 'from_step' to resume at the first step that has no recorded output. A step whose output was never recorded is re-run, never skipped. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| from_step | integer | – | Zero-based index of the first step to actually execute. Defaults to the first step with no recorded output. |
| session_id | string | yes | The workflow session id to continue from. |
No output schema declared.
No examples provided.
rotate_api_key Rotate Api Key ~113
Replace the API key making this call with a fresh one carrying the same scopes. WARNING: this IRREVERSIBLY deactivates the current key the moment it succeeds — every other caller using that key stops working immediately, so do not call it on a shared credential. The new key is returned exactly once in the response and cannot be retrieved again. A delegated child key cannot rotate itself. Requires API-key authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| expires_in_days | integer | – | Lifetime of the replacement key in days (default 90). |
No output schema declared.
No examples provided.
run_council Run Council ~186
Submit a question or decision to Meta Council. A panel of specialized AI agents will independently analyze it, then a synthesis step combines their opinions into a unified recommendation with full transparency. Starts asynchronously by default; use get_session with the returned session id.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Model to use (e.g., 'claude-sonnet-4-6', 'gpt-4o', 'deepseek-chat'). Omit to use user's default. |
| panel | string | – | Panel slug to use (e.g., 'default', 'technology', 'healthcare'). Use 'auto' for automatic panel selection. Omit to use default panel. |
| query | string | yes | The question or decision to analyze |
| wait_seconds | integer | – | Optional synchronous wait (0-90 seconds). Default 0 returns the session id immediately, avoiding reverse-proxy timeouts. |
No output schema declared.
No examples provided.
run_workflow Run Workflow ~350
Start a multi-step workflow pipeline and return its session id and definition_sha immediately by default — the fingerprint of the definition this run resolved, comparable against the one plan_workflow reported. Poll get_workflow_session for each step's model/provider and output. synthesis. Steps run on YOUR configured provider keys, so a pipeline can chain models across providers. If a step is a human checkpoint, returns the session id to advance. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Caller-supplied key: sending the same key again returns the run that already exists instead of starting a second, paid run. Use a stable key derived from your own request so an uncertain retry conver… |
| parameters | object | – | Values for the workflow's declared parameters, as a flat name-to-value object, e.g. {"region": "EU"}. Omitted names use their declared defaults. Workflows that declare no parameters take none. |
| query | string | yes | The input to run the pipeline on. Be specific, e.g. 'Analyze NVDA as an investment'. |
| step_models | object | – | Per-run model choices, keyed by zero-based step index, exactly as supplied to plan_workflow. IDs are catalog-validated; existing key, tier and platform fallback rules still apply. These choices must… |
| wait_seconds | integer | – | Optional synchronous wait; default 0 returns immediately. |
| workflow | string | yes | The workflow slug (from list_workflows), e.g. 'live_market_pipeline', 'due_diligence', 'coding_tdd'. |
No output schema declared.
No examples provided.
save_ticket_attention_policy Save Ticket Attention Policy ~142
Save owner-private attention thresholds and status overrides in elapsed UTC days (finite 0–3650). Requires tickets:write. Supply full base thresholds, sparse status overrides, expected_revision (0 first) and caller-stable idempotency_key. Null only in an override disables that rule, never pauses clocks. Each save/restoration creates immutable history and invalidates earlier attention reviews. Exact retry returns original saved_policy receipt, which may no longer be current; read effective policy separately. No ticket status, clock, notification or provider changes.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_revision | integer | yes | – |
| idempotency_key | string | yes | – |
| policy | object | yes | – |
No output schema declared.
No examples provided.
save_ticket_attention_review Save Ticket Attention Review ~194
Record an owner-private review of current attention evidence, with optional note (2000 characters) and follow_up_date plus explicit IANA follow_up_timezone, or null for both. Requires tickets:write. Supply the current evidence digest, current review revision (0 first), and caller-stable idempotency key. Exact retries return the original receipt; changed requests, revision or evidence conflict. Retains immutable history; omitted fields clear note/date. Does not hide/reorder queue items, reset clocks/status, approve consequential actions, notify or call providers. Retained evidence discloses omitted prerequisite detail.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_evidence_digest | string | yes | – |
| expected_review_revision | integer | yes | – |
| follow_up_date | string|null | – | – |
| follow_up_timezone | string|null | – | – |
| idempotency_key | string | yes | – |
| note | string|null | – | – |
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
save_ticket_delivery_plan Save Ticket Delivery Plan ~96
Explicitly replace or clear a ticket plan. Dates and working-day duration are separate from points. Pass current expected_version; reuse exact request_id on retries. Changed saves atomically record immutable revision and plan_changed history. No automatic scheduling/execution. Requires tickets:write.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_version | integer | yes | – |
| plan | object|null | yes | – |
| request_id | string | yes | – |
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
score_locus_case Score Locus Case ~212
Score an anonymized adult mental-health / addiction case against LOCUS. Convenes the LOCUS Assessment Panel (psychiatrist, addiction specialist, clinical social worker, utilization reviewer, peer specialist, safety officer); each reviewer independently rates all six LOCUS dimensions, then a DETERMINISTIC engine aggregates the ratings and applies the Determination Grid and the inviolable override floors IN CODE (safety floors like Risk-of-Harm=4 → Level 5 cannot be reasoned away). Returns the recommended Level of Care with a full audit trail. Adults only (CALOCUS/CASII covers child/adolescent); use ONLY anonymized cases. Starts asynchronously by default; poll get_session. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| case | string | yes | The anonymized clinical case text (presentation, history, substance use, functional status, environment, engagement). |
| model | string | – | Optional model override; omit for the platform default. |
| wait_seconds | integer | – | Optional synchronous wait; default 0 returns immediately. |
No output schema declared.
No examples provided.
search_outreach_leads Search Outreach Leads ~128
Search the user's outreach leads — filter by a text query (company / contact / email), pipeline status, and/or campaign. Returns company, contact, status, pitch, and reply info. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | Filter to a single campaign id. |
| limit | integer | – | Max leads to return (default 20, max 100). |
| search | string | – | Text to match against company / contact name / title / email. |
| status | string | – | Filter by pipeline status (e.g. 'ready', 'sent', 'replied'). |
No output schema declared.
No examples provided.
send_invoice Send Invoice ~47
Mark a draft invoice as sent (stamps issued_at). Re-sending an already-sent invoice is a harmless no-op. invoice_id is required.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | – |
No output schema declared.
No examples provided.
share_saved_view Share Saved View ~172
Share one of YOUR OWN saved views with a single team you belong to. Members may read, list and execute it; only you may revise, re-share or delete it. Executing a shared view runs it against the READER's own tickets, so this shares the question and never the answers. Re-sharing to a different team MOVES the view rather than adding a second grant -- a view is readable by at most one team. Note: team ids are not currently discoverable from this MCP surface, so supply one you already hold. Requires authentication and the tickets:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | string | yes | The id of a team you belong to. Sharing with a team you are not a member of is refused. |
| view_id | string | yes | The view's id, from list_saved_views. |
No output schema declared.
No examples provided.
submit_consulting_deliverable Submit Consulting Deliverable ~35
Submit an owned draft deliverable for internal review without publishing it.
| Name | Type | Req | Description |
|---|---|---|---|
| deliverable_id | string | yes | – |
No output schema declared.
No examples provided.
submit_content_asset Submit Content Asset ~39
Submit an owned draft for review, freezing that exact revision and content hash.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | Full UUID from the matching list tool. |
No output schema declared.
No examples provided.
submit_meta_council_feedback Submit Meta Council Feedback ~210
Report feedback about the META COUNCIL PLATFORM itself — a noticeable performance failure, a lacking/missing capability, a bug, or a UX/docs gap in Meta Council's tools, councils, workflows, or MCP surface. Platform feedback only: do NOT use this for anything about your own business, customers, deals, invoices, or other data Meta Council manages on your behalf — use the relevant business tool for that instead (e.g. create_deal, create_invoice). Use it the moment a tool result, council run, or workflow falls short. Stored per-user and visible only to platform admins — the response returns an id + acknowledgement and submissions cannot be read back. Include machine context (tool name, session id, model) in the context object.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| category | string | – | – |
| context | object | – | Machine context: tool name, session id, model, timings. |
| severity | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
sync_accounting_tickets Sync Accounting Tickets ~158
Commit a previously previewed completed Accounting run's WRITEOff work plan to stable owner-private Meta Council tickets. The expected_plan_hash from the preview is required, retries are idempotent, stable references prevent duplicate tickets across reprocessed runs, and human edits to generated content fields are preserved. Status, assignee, hierarchy, and completion are not reset. Requires both accounting:read and tickets:write. This creates or updates only in-platform planning tickets; they are not field-encrypted and become readable through tickets:read without accounting:read. It never files, pays, sends, or publishes anything.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_plan_hash | string | yes | Exact plan_hash returned by preview_accounting_ticket_sync. |
| run_id | string | yes | – |
No output schema declared.
No examples provided.
test_workflow_step Test Workflow Step ~285
Run exactly ONE step of a workflow and return what it produced, so you can iterate on a single step's wording without running the steps before it. THIS SPENDS CREDITS EXACTLY LIKE A REAL STEP: the step runs on a real model through the same engine a full run uses and is billed identically -- it is not a simulation, a dry run, or a free preview. If you want to check a workflow's shape, parameters, models and cost estimate for free, use plan_workflow instead; that one runs nothing. Starts no session, so there is nothing to poll and nothing to advance. Requires authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| parameters | object | – | Optional values for the workflow's declared parameters, as a flat name-to-value object, e.g. {"region": "EU"}. They are substituted into the step wording the same way a real run substitutes them. |
| query | string | – | The input the step works on, exactly as you would pass it to run_workflow. Optional -- omit for a step whose instruction already carries everything it needs. |
| step_index | integer | yes | Which step to run, counting from 0. A workflow with 4 steps accepts 0 to 3; anything else is refused without spending. |
| workflow | string | yes | The workflow slug (from list_workflows), e.g. 'due_diligence'. |
No output schema declared.
No examples provided.
ticket_archive Ticket Archive ~160
Retire an owned ticket from the working set, or restore one. Archiving is a different axis from status: the ticket keeps whatever status it had, so a done ticket stays done and a blocked one comes back still blocked — never use status 'cancelled' to mean 'archived'. An archived ticket disappears from ticket_list, the stats, the buckets, the attention queue, and outbound JIRA/Linear sync, but keeps its id and URL so citations stay valid, and it refuses edits until restored. Cascades to the active subtree; restore brings back exactly what was archived alongside it. Nothing is destroyed — this is not a delete, and no delete tool is exposed.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
ticket_batch_create Ticket Batch Create ~213
Preview or idempotently commit one atomic owner-private batch of structured tickets and nested subtickets. Preview is non-mutating and returns the normalized commit payload, exact preview_token, and deterministic predicted IDs as JSON. Commit requires that exact token: combine commit_payload with mode=commit, the caller-held idempotency_key, and preview_token. It returns the same IDs plus replay status. A caller-stable visible-ASCII idempotency_key is always required. MCP authorship is stamped by the server; callers cannot spoof it. Nested subtickets are bounded and validated by the ticket handler before any write. This never executes, sends, publishes, deletes, or mutates an external provider.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | Caller-stable visible-ASCII key. Reuse only for the exact same operation and payload. |
| mode | string | yes | – |
| parent_id | string|null | – | – |
| preview_token | string | – | Exact preview_token returned by preview mode. |
| tickets | array | yes | – |
No output schema declared.
No examples provided.
ticket_claim Ticket Claim ~111
Claim a ticket to work on: sets assignee to your agent name and moves it to in_progress in one step (the move is audit-logged). Refuses if another agent already has it in progress unless force=true. Follow up with ticket_comment progress updates and finish via ticket_update status='done'.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | yes | Your agent name, e.g. 'claude_code_local'. |
| force | boolean | – | Take over a ticket another agent holds. |
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
ticket_comment Ticket Comment ~154
Add a comment to an owned ticket's activity trail. Use kind='progress' for work updates while a ticket is in progress. The authenticated API-key UUID is stamped as author; callers cannot supply or spoof it. Open the comment in plain language before any technical detail — these are read during escalations by people who were not part of the work.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Comment text (Markdown ok). Lead with a plain-language summary: what changed as observable behaviour, and what still needs a human decision — or say plainly that nothing does. Keep SHAs, paths and sy… |
| kind | string | – | – |
| ticket_id | string | yes | – |
No output schema declared.
No examples provided.
ticket_comments Ticket Comments ~136
Read complete discussion bodies, authors, kinds and timestamps for one owned ticket, including archived tickets. Returns a JSON page, newest first with legacy null times last. limit is 1–100 (default 50). Continue with next_cursor while has_more; reached_oldest means there are no older rows. Cursors are bound to this account/ticket and expire after 24 hours. Omit cursor for a fresh read of newer activity. This is ordinary discussion, not completion evidence or permission to act. Requires tickets:read.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| ticket_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No examples provided.
ticket_create Ticket Create ~269
Create a ticket on the caller's board — optionally as a subticket via parent_id. Recommend degree of difficulty with effort (trivial|small|medium|large|epic) and the kind of work with action_type (strategy|implementation|research|validation|testing|coordination). The authenticated API-key UUID is stamped by the server as creator provenance; callers cannot supply or spoof it. Session/workflow ids are opaque metadata links only. New epics cannot be created already done.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptance_criteria | string | – | – |
| action_type | string | – | – |
| assignee | string | – | – |
| description | string | – | Open with one plain sentence saying what needs to happen and why it matters, for someone picking this up cold; put specifics and jargon after it. |
| effort | string | – | – |
| effort_points | integer | – | – |
| external_ref | object | – | – |
| labels | array | – | – |
| order_index | integer | – | – |
| parent_id | string | – | Parent ticket UUID. |
| priority | string | – | – |
| session_id | string | – | – |
| status | string | – | New epics cannot be created already done; task statuses use the lifecycle authority. |
| title | string | yes | – |
| workflow_session_id | string | – | – |
No output schema declared.
No examples provided.
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.