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.

Catalyst Governance

REMOTE · CATALYST.STRATOGENIC.AI · 2 COMPONENTS

Governance middleware for AI agents: permission gates, approvals, compliance scanning, audit ledger.

0 this week 84 Trust /100

Last scanned (21 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3304 tokens (~106/item across 31 items; 31 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 32 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • Endpoint address

    Registry says
    https://catalyst.stratogenic.ai/mcp
    Package shows
    https://catalyst.stratogenic.ai/mcp/

    The registry's URL redirects here, so the authorisation and transport results describe this address rather than the one listed. See the evidence →

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.

  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Endpoint reachability: unreachable → reachable ▲ functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Sept 26 0
    • Server version: 1.29.1 → 1.30.0 functional
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 21 Nov 2026 · Probed https://catalyst.stratogenic.ai/mcp/ · Declared URL https://catalyst.stratogenic.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=catalyst.stratogenic.ai CN=YR2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 RSA 2048 SHA256-RSA 55d22cdc041b2bf997f932c5a802738d2be
SANs: catalyst.stratogenic.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of catalyst.stratogenic.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
stratogenic.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 3 probes
Transport URL Outcome Status Location
streamable-http https://catalyst.stratogenic.ai/mcp Redirected 307 https://catalyst.stratogenic.ai/mcp/
streamable-http · followed https://catalyst.stratogenic.ai/mcp/ Verified 200
http (plaintext) http://catalyst.stratogenic.ai/mcp HTTPS enforced 301 https://catalyst.stratogenic.ai/mcp
MCP tools · 31 exposed · ~2,991 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
catalyst_accept_proposals ~116

Accept one or more proposals, committing them to the flow cycle. ids: list of proposal `idempotency_key` values from catalyst_list_proposals. Do not pass `task_id` or `id` — the backend looks up proposals by `idempotency_key` and will silently match nothing if the wrong field is used. Acceptance is the governance commit step: items move from review state into live execution state and are recorded in the immutable ledger.

NameTypeReqDescription
idsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_activate_compliance_framework ~104

Activate a pre-built compliance framework pack for this organisation. framework: one of gdpr, soc2, iso27001, hipaa, pci_dss, eu_ai_act, bribery_act, aml_kyc. Once activated, the pack's DENY/REQUIRE/ADVISE rules are merged into every subsequent compliance scan — no document upload required. Requires can_scan entitlement.

NameTypeReqDescription
frameworkstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_await_approval ~129

Check approval status for a specific proposal. Returns approved: true/false and clear guidance on whether to proceed. Call this after catalyst_check_action returns 'proposal_required'. Do NOT proceed with the gated action until approved: true is returned. POLLING vs EVENT-DRIVEN: For interactive sessions, poll this tool. For autonomous long-running workflows, prefer registering a webhook via catalyst_register_approval_webhook(callback_url) so your orchestrator is notified the moment a human acts — no polling loop required.

NameTypeReqDescription
proposal_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_bulk_update_tasks ~81

Bulk update all tasks matching a filter. Growth/Enterprise plans only. filter keys: domain, priority, stage, owner, tag, group_id. updates keys: owner, priority, domain, stage, tags_add, tags_remove. Returns matched and updated counts.

NameTypeReqDescription
filterobjectyes–
updatesobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_check_action ~151

Check if a capability/action is permitted by your governance policy. Returns decision: 'allow' | 'proposal_required' | 'deny' with guidance. Call BEFORE any consequential action (API call, data write, send, deploy). If title is provided and decision is 'proposal_required', the intent is logged automatically and proposal_id is returned — no second call needed. If 'proposal_required' without a title, call catalyst_log_task separately. capability examples: 'send_email', 'write_file', 'deploy_code', 'update_record', 'delete_record', 'external_api_call'.

NameTypeReqDescription
capabilitystringyes–
context–––
title–––

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_create_tasks_from_findings ~68

Materialise compliance findings as actionable flow tasks. classes: list of finding classes to convert, e.g. ['MISSING_CONTROL', 'PROHIBITED_ACTION']. Defaults to both. Created tasks enter the governance pipeline like any other ingest.

NameTypeReqDescription
classes–––

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_decline_proposals ~109

Decline one or more proposals without committing them. ids: list of proposal `idempotency_key` values from catalyst_list_proposals. Do not pass `task_id` or `id` — the backend looks up proposals by `idempotency_key` and will silently match nothing if the wrong field is used. Declined proposals are recorded for audit and learning but are not added to the live flow cycle.

NameTypeReqDescription
idsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_evaluate_agent_action ~86

Evaluate whether an agent action is permitted by the governance gate. Returns decision: 'allow' | 'proposal_required' | 'deny'. High-risk actors with allow decisions are escalated to proposal_required. The actor must be registered and active for this tenant.

NameTypeReqDescription
actor_idstringyes–
capabilitystringyes–
context–––

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_export_ledger ~85

Export the immutable SHA-256 chained audit ledger. since: ISO timestamp to filter entries (inclusive). format: 'json' returns full entries; 'csv' sets entries to null (use REST API for CSV). The ledger is tamper-evident — any modification breaks the hash chain.

NameTypeReqDescription
formatstring––
since–––

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_export_workflow_audit ~86

Export audit events for an AI workflow as JSON. since: ISO timestamp filter (inclusive). ai_standards_only: limit to events from workflows opted into Built to AI Standards. Suitable for regulatory submissions and investor due diligence.

NameTypeReqDescription
ai_standards_onlyboolean––
since–––
workflow_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_get_compliance_findings ~67

Get the latest compliance findings from the most recent scan. Returns findings flattened by category: conflicts, gaps, ok. Each finding includes category, severity, status, and task linkage. Does not trigger a new scan — use catalyst_run_compliance_scan first.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_get_dashboard ~53

Get the governance dashboard snapshot including all views. Returns tenant metadata, execution metrics, and all 5 governance views (execution_flow, ownership_map, compliance_web, risk_heatmap, client_influence).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_get_graph_views ~66

Get all 7 governance graph views for the tenant. Views: org_snapshot, execution_flow, ownership_map, compliance_web, risk_heatmap, client_influence, catalyst_metrics. Read-only, derived from flow_cycle on demand. Requires governance_dashboard entitlement.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_get_org_summary ~94

Get an AI-generated narrative summary of the org's execution state. time_window: 'last_7_days' or 'last_30_days'. extra_query: optional focus bias (e.g. 'compliance', 'delivery risk'). Returns a MASC-L3 compliant narrative — no individual evaluations. Requires governance_dashboard entitlement.

NameTypeReqDescription
extra_query–––
time_windowstring––

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_get_workflow_trust ~101

Get the four-component trust score for a registered AI workflow. Score = 0.25×ai_declared + 0.25×risk_eval + 0.25×override + 0.25×(1−failure). Range 0.0–1.0. window_days controls the lookback period (1–365).

NameTypeReqDescription
window_daysinteger––
workflow_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_ingest_task ~84

Ingest one or more tasks into Catalyst governance pipeline. Items should include at minimum a 'title'. Optional fields: details, owner, priority (Low/Medium/High/Critical), stage, domain, due_at, tags, group_id. Returns ingested count and proposal IDs created.

NameTypeReqDescription
domain–––
itemsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_list_compliance_frameworks ~92

List all available pre-built compliance framework packs. Returns each pack (GDPR, SOC 2, ISO 27001, HIPAA, PCI-DSS, EU AI Act, Bribery Act, AML/KYC) with its name, description, rule count, and whether it is currently active for this organisation. Activate a pack with catalyst_activate_compliance_framework.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_list_compliance_rules ~104

List all compliance rules currently in effect for the organisation. Returns rules from three sources combined and deduplicated: - Rules extracted from uploaded policy documents - Custom org-level rules (PATCH /compliance/rules) - Rules from any activated framework packs Each rule includes: id, type (DENY/REQUIRE/ADVISE), trigger sentence, severity, scope, remediation guidance, confidence score, and authority citation.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_list_proposals ~117

List all pending governance proposals awaiting acceptance or decline. Proposals are work items that have been ingested but not yet committed to the live flow cycle. They require human (or agent) review. Each proposal contains an `idempotency_key` field — this is the canonical proposal identifier. Always use `idempotency_key` (not `task_id` or `id`) when passing proposal IDs to catalyst_accept_proposals, catalyst_decline_proposals, or catalyst_review_proposal.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_log_task ~103

Log a task or action into the Catalyst governance pipeline. Records work, decisions, and actions for audit and governance. priority: Low | Medium | High | Critical. domain: security | product | operations | compliance | finance | legal | other. Returns ingested count and any proposal_ids created (if a governance hold applies).

NameTypeReqDescription
details–––
domain–––
prioritystring––
titlestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_my_governance ~124

Show your governance profile, actor registration, and plan capabilities. Returns governance_mode (observe/advisory/proposal/strict), risk_class, declared capabilities, and actor_id. Auto-registers you in observe mode on first connection — the lightest governance touch. Also returns plan_capabilities showing which features are active and which require an upgrade — relay any upgrade_required fields to the user so they can unlock compliance scanning or AI workflow governance. Call this first to understand what you are and are not permitted to do.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_pending_approvals ~67

List proposals currently awaiting governance approval. Shows proposals with status pending or in review. Use this to check whether an action you submitted is still waiting for human sign-off before you proceed. Returns count and full proposal objects with IDs for catalyst_await_approval.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_register_approval_webhook ~166

Register a callback URL to receive proposal approval notifications. Subscribes callback_url to proposal.accepted and proposal.declined events. When a human approves or declines any proposal, Catalyst POSTs the event to your URL with the resolved proposal IDs in data.ids. Use this instead of polling catalyst_await_approval for autonomous workflows: register once, let your orchestrator (Temporal, job queue, webhook relay) wake the agent when the relevant proposal_id arrives. Then call catalyst_await_approval once to confirm and proceed. Returns subscription IDs, the expected payload shape, and usage guidance. Returns upgrade_required: true if outbound webhooks are not on your plan.

NameTypeReqDescription
callback_urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_register_machine_actor ~141

Register a machine actor (agent, automation) with Catalyst governance. runtime_type: zapier_zap | n8n_workflow | openai_assistant | make_scenario | claude_agent | custom_agent | internal_worker. governance_mode: observe | advisory | proposal | strict. risk_class: low | standard | high. Requires can_configure_ai_workflows entitlement (Enterprise+).

NameTypeReqDescription
capabilities–––
display_namestringyes–
governance_modestring––
notes–––
risk_classstring––
runtime_typestringyes–
scopes–––

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_register_workflow ~121

Register an AI workflow for EU AI Act compliance governance. risk_level: unacceptable (rejected) | high | limited | minimal. mode: observe | advisory | proposal. High-risk workflows are forced to proposal. Sets ai_standards=True to opt into the Built to AI Standards evidence trail. Requires can_configure_ai_workflows (Enterprise+).

NameTypeReqDescription
ai_standardsboolean––
mode–––
notes–––
risk_levelstring––
workflow_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_review_proposal ~131

Approve or reject a review-required proposal (AI governance hold). proposal_id: the `idempotency_key` field from catalyst_list_proposals. Do not pass `task_id` or `id` — the backend looks up by `idempotency_key`. decision must be 'approve' or 'reject'. Approved proposals can then be accepted via catalyst_accept_proposals. Rejected proposals are marked review-rejected in the ledger.

NameTypeReqDescription
decisionstringyes–
proposal_idstringyes–
reason–––
reviewer_id–––

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_run_compliance_scan ~53

Run a compliance scan against all loaded compliance documents. Detects compliance gaps, conflicts, and policy violations across the current flow cycle. Requires can_scan entitlement. Returns findings grouped by severity.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_search_tasks ~80

Search normalised tasks in the tenant flow cycle. Performs case-insensitive substring match on title/details. Filter by canonical domain (e.g. security, product, operations) or priority.

NameTypeReqDescription
domain–––
limitinteger––
offsetinteger––
priority–––
qstring––

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_send_lite_event ~92

Send a lifecycle event for a registered AI workflow. event_type examples: run.started, action.executed, approval.requested, run.completed, run.failed. Idempotent via request_id (UUID recommended). Payload is scrubbed of credentials before storage.

NameTypeReqDescription
event_typestringyes–
payload–––
request_id–––
workflow_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_update_task ~71

Update a single task in the governance flow. Ledger-recorded. Patch may include: title, details, owner, priority, stage, domain, due_at, status, tags, done. Normalisation is applied automatically.

NameTypeReqDescription
patchobjectyes–
task_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

catalyst_weekly_summary ~49

Get a 7-day activity rollup: ingested, accepted, declined proposals, domain breakdown, priority breakdown, and average risk score. Fully deterministic — no LLM calls.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Catalyst Governance MCP server?

Catalyst Governance is a hosted endpoint at https://catalyst.stratogenic.ai/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 · catalyst.stratogenic.ai

# add to Claude Code
claude mcp add --transport http stratogenic-ai-catalyst 'https://catalyst.stratogenic.ai/mcp'
Common questions

What is the Catalyst Governance MCP server?

Catalyst Governance is an MCP server listed in the public MCP registry as io.github.Stratogenic-AI/catalyst. Governance middleware for AI agents: permission gates, approvals, compliance scanning, audit ledger. This page covers its hosted endpoint (https://catalyst.stratogenic.ai/mcp).

Is the Catalyst Governance MCP server safe to use?

Catalyst Governance scores 84 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 Catalyst Governance MCP server expose?

Catalyst Governance exposes 31 tools: catalyst_ingest_task, catalyst_search_tasks, catalyst_update_task, catalyst_bulk_update_tasks, catalyst_list_proposals, and 26 more. Their descriptions and schemas cost roughly 2,991 tokens of context every time the server is loaded.

Does the Catalyst Governance MCP server require authentication?

No. We connected to Catalyst Governance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Catalyst Governance MCP server still maintained?

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

What did VerifyMCP test on the Catalyst Governance MCP server?

VerifyMCP ran 13 checks on Catalyst Governance, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.