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.

Moltline Agent Governance

REMOTE · MCP.MOLTLINESTUDIO.COM

Audit MCP configs and skill files for over-broad scope and injection risk. 6 of 8 free.

0 this week 87 Trust /100

Last scanned (1 hour ago)

Scores higher than 94% of remote servers

Reachable. Last reached 5 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 Security83
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2027 tokens (~253/item across 8 items; 8 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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.

  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Tool “audit_skill_file” rewrote its description, which is the text the model reads security
    • “audit_mcp_config” reworded the description of “config” cosmetic
    • “inventory_report” reworded the description of “items” cosmetic
    • “scope_check” reworded the description of “tools” cosmetic
  • 25 Oct 26 0
    • Tool “agent_readiness_scan” rewrote its description, which is the text the model reads security
    • Tool “audit_mcp_config” rewrote its description, which is the text the model reads security
    • Tool “audit_skill_file” rewrote its description, which is the text the model reads security
    • Tool “get_auditor_persona” rewrote its description, which is the text the model reads security
    • Tool “governance_policy” rewrote its description, which is the text the model reads security
    • Tool “injection_scan” rewrote its description, which is the text the model reads security
    • Tool “inventory_report” rewrote its description, which is the text the model reads security
    • Tool “scope_check” rewrote its description, which is the text the model reads security
  • 4 Oct 26 +19
    • Authorization: unverified → partial ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
  • 3 Oct 26 −19
    • Authorization: partial → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
  • 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
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 5 Nov 2026 · Probed https://mcp.moltlinestudio.com/govern

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=moltlinestudio.com CN=WE1,O=Google Trust Services,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA256 5fcf21014c71aedb0ee8aa375beac0b4
SANs: moltlinestudio.com, *.moltlinestudio.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.moltlinestudio.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
moltlinestudio.com. present 2371 13 Verified
mcp.moltlinestudio.com. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=15576000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'nonce-d5365ac5-a31d-4c8d-848d-25c914b63c62'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.moltlinestudio.com https://mcp.moltlinestudio.com; form-action 'self'; frame-ancestors 'none'; base-uri '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 camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.moltlinestudio.com/govern Verified 200
http (plaintext) http://mcp.moltlinestudio.com/govern HTTPS enforced 301 https://mcp.moltlinestudio.com/govern
MCP tools · 8 exposed · ~1,911 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
agent_readiness_scan ~292

Score a public domain against 21 agent-readiness checks. FREE. Use when you need to know whether an autonomous agent can discover, read, use or pay a website - your own, or a vendor you are evaluating before recommending it. Typical input {"domain": "example.com"} returns {"score": 8, "total": 21, "grade": "F", "passed": [...], "failed": [{"title": "...", "detail": "...", "fix": "..."}], "report_url": "..."} where report_url is a permanent shareable page for the same result. Not for auditing an MCP client configuration (audit_mcp_config) and not for scanning text for injection (injection_scan) - this one reaches out over the network and fetches public URLs on a live domain. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "The readiness scanner is not reachable right now."}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
domainstringyesA public hostname such as example.com. A full URL is accepted and reduced to its host. Hostnames that resolve to private or internal addresses are refused.

Structured output declared, but exposes no named fields.

No examples provided.

audit_mcp_config ~274

Audit an MCP server config for risk-ranked posture findings. FREE. Flags exposed machine credentials in the config, required inputs that aren't gated/optional, unpinned versions, over-broad env access, and dangerous auto-run flags. It never echoes any matched secret value back. Typical input {"config": "<mcpize.yaml, mcp.json, or a Claude/Cursor servers block>"} returns {"posture_score": 0-100, "verdict": "...", "findings": [{"line": N, "severity": 1-5, "issue": "...", "fix": "..."}], "note": "..."}. Use on a server configuration document. Not for a skill or instruction file (audit_skill_file) and not for untrusted content an agent is about to read (injection_scan). Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
configstringyesThe MCP config to audit, pasted as text or JSON (mcpize.yaml, mcp.json, or a Claude/Cursor servers block).

Structured output declared, but exposes no named fields.

No examples provided.

audit_skill_file ~238

Audit an agent skill or instruction file before you trust it. FREE. Checks for governance smells: prompt-injection and guardrail-bypass phrasing, concealment instructions ('don't tell the user'), exfiltration language, and exposed credential material. Typical input {"content": "<SKILL.md, system prompt, or tool description text>"} returns {"verdict": "reject: do not install" | "no governance red flags on a pattern pass", "findings": [{"severity": 1-5, "issue": "..."}], "note": "..."}. Use before trusting a skill or instruction file that came from outside your own repository. Not for arbitrary untrusted input at run time (injection_scan). Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
contentstringyesFull text of the skill file, system prompt, or tool description to audit.

Structured output declared, but exposes no named fields.

No examples provided.

get_auditor_persona ~161

Load the Governance Auditor persona for consistent fleet audits. PREMIUM (license). The persona is methodical, evidence-driven, and allergic to 'it's probably fine'. Takes no arguments. Returns {"persona": ..., "identity": ..., "rules": ["...", ...], "opening_move": "..."} ready to adopt as a system prompt. Use to keep repeated audits consistent in voice and rigor. Not for running an audit - the audit tools do that. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

governance_policy ~222

Generate an audit-ready agent-governance policy for a fleet. PREMIUM (license). Covers inventory cadence, ownership rules, least-privilege approval gates, injection defense, logging/retention, and decommissioning triggers. Typical input {"fleet_context": "20 agents, 3 with shell access, one finance bot"} returns {"policy": ..., "sections": {...}, "context_note": ..., "audit_checklist": ["...", ...]}. Use when a fleet needs a written policy document. Not for assessing what the fleet currently does (inventory_report, audit_mcp_config). Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
fleet_contextstring–Optional plain-language description of the fleet (size, capabilities, sensitive systems) used to tailor the policy; empty returns the generic baseline.

Structured output declared, but exposes no named fields.

No examples provided.

injection_scan ~220

Scan untrusted text for prompt-injection patterns before ingestion. FREE. Use on any web page, email, or document an agent is about to ingest to catch prompt-injection and data-exfiltration patterns before they reach the agent's context. Typical input {"text": "<untrusted content>"} returns {"injection_suspected": bool, "count": N, "hits": [{"line": N, "pattern": "...", "text": "<flagged line>"}], "note": "..."}. Not for reviewing a skill file you control (audit_skill_file), and a clean result is not a guarantee of safety - it reports pattern matches only. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
textstringyesThe untrusted content to scan, pasted as a single string.

Structured output declared, but exposes no named fields.

No examples provided.

inventory_report ~256

Build a governance inventory with risk tiers from a raw agent list. FREE. Turns a list of agents / MCP servers / skills into an audit-ready summary with critical/elevated/standard tiers and unowned-agent flags. Typical input {"items": "[{\"name\": \"deploy-bot\", \"owner\": \"ana\"}]"} returns {"total": N, "tiers": {"critical": N, ...}, "unowned_agents": [...], "inventory": [{"name": ..., "owner": ..., "tier": ..., "orphaned": bool}], "reading": "...", "note": "..."}. Use to turn a raw agent list into risk tiers. Not for auditing any single agent in depth (audit_mcp_config, scope_check). Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
itemsstringyesThe fleet as a string (a JSON array of {name, owner?, capabilities?, last_seen?} objects, or plain newline-separated agent names).

Structured output declared, but exposes no named fields.

No examples provided.

scope_check ~248

Score the blast radius of every tool in a permission manifest. FREE. Ranks each tool by capability risk (command exec > money/delete > file-write/messaging > read > network) and flags the over-privileged ones that need approval gates. Typical input {"tools": "[\"run_shell\", \"read_docs\"]"} returns {"tools_scored": N, "high_risk_tools": N, "ranking": [{"tool": ..., "blast_radius": 0-5, "capabilities": [...]}], "recommendation": ["..."], "note": "..."}. Use on a permission manifest to rank tools by blast radius. Not for the configuration that mounts them (audit_mcp_config). Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

NameTypeReqDescription
toolsstringyesThe manifest as a string (a JSON array of tool names or {name, description} objects, a JSON object of name->description, or plain newline-separated names).

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Moltline Agent Governance MCP server?

Moltline Agent Governance is a hosted endpoint at https://mcp.moltlinestudio.com/govern, 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 · mcp.moltlinestudio.com

# add to Claude Code
claude mcp add --transport http com-moltlinestudio-govern 'https://mcp.moltlinestudio.com/govern'
Common questions

What is the Moltline Agent Governance MCP server?

Moltline Agent Governance is an MCP server listed in the public MCP registry as com.moltlinestudio/govern. Audit MCP configs and skill files for over-broad scope and injection risk. 6 of 8 free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/govern).

Is the Moltline Agent Governance MCP server safe to use?

Moltline Agent Governance scores 87 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 Moltline Agent Governance MCP server expose?

Moltline Agent Governance exposes 8 tools: audit_mcp_config, scope_check, audit_skill_file, injection_scan, inventory_report, and 3 more. Their descriptions and schemas cost roughly 1,911 tokens of context every time the server is loaded.

Does the Moltline Agent Governance MCP server require authentication?

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

Is the Moltline Agent Governance MCP server still maintained?

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