COSO Internal Control MCP

MCP server

Run a COSO internal-control review end to end — scope, risks, controls, sampling, testing, workpapers, sign-off and deficiency evaluation.

An internal control is only as good as the evidence behind it. This is that evidence trail, run to the framework a reviewer will test.

tools: 39
COSO principles: 17
components: 5
open source: MIT

What it does

39 tools over Streamable HTTP
Scope → risk → controls → sampling → testing → workpapers → sign-off
Deficiency classification and COSO component coverage

Standards it cites

COSO ICIF-2013
SOX 404
PCAOB AS 2201

Connect

Add the endpoint as a remote MCP server — no API key. Works with any MCP client, including ChatGPT and n8n.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "coso-mcp": {
      "type": "remote",
      "url": "https://internal-control.ascent-partners.com/mcp"
    }
  }
}

Facts

Endpoint: https://internal-control.ascent-partners.com/mcp
Transport: Streamable HTTP
Auth: Open — no API key
Licence: MIT
Registry: io.github.simonmak-ascent/coso-mcp

Where it comes from

Built by Simon Mak, Founder & Chief Executive Officer, and published under github.com/simonmak-ascent as part of the firm's open tooling.

Technology Advisory Talk to us

Documentation Source

Back to Open Tooling