Koskamo

COSO Internal Control MCP

An MCP server that enables end-to-end COSO internal-control reviews, including scope definition, risk assessment, control testing, sampling, workpaper generation, and deficiency evaluation based on the COSO ICIF-2013 framework.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

COSO Internal Control MCP logo, by Ascent PartnersVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-10-19Operated by Ascent Partners
MCP endpoint (Streamable HTTP)
https://internal-control.ascent-partners.com/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Failed Endpoint failed the latest live check ·
  • Passed Official MCP Registry namespace is tied to ascent-partners.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Uptime 0% over 90 days

What you can do with it

  • Run a COSO internal-control review end to end
  • Perform deterministic sampling and deficiency math
  • Trace evidence to the framework a reviewer will test

Source and maintenance

Vendor evidenceRegistry 0.1.2MIT
mcp-registry: com.ascent-partners/coso-mcp@0.1.2Source repository
Last repository push
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

0% (0 of 19 checks answered)

  1. 2026-11-02: 0 of 3 checks answered
  2. 2026-11-03: 0 of 4 checks answered
  3. 2026-11-04: 0 of 4 checks answered
  4. 2026-11-05: 0 of 4 checks answered
  5. 2026-11-06: 0 of 4 checks answered

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · repository · passed · updated
  • · repository · passed · metadata changed · unchanged
  • · repository · passed · metadata changed · updated
  • · registry · passed · metadata changed · Source metadata updated
  • · registry · passed · metadata changed · Source metadata updated
  • · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http coso-internal-control-mcp https://internal-control.ascent-partners.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add coso-internal-control-mcp --url https://internal-control.ascent-partners.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable coso-internal-control-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "coso-internal-control-mcp": {
      "url": "https://internal-control.ascent-partners.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "coso-internal-control-mcp": {
      "type": "streamableHttp",
      "url": "https://internal-control.ascent-partners.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start coso-internal-control-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "coso-internal-control-mcp": {
      "type": "http",
      "url": "https://internal-control.ascent-partners.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http coso-internal-control-mcp https://internal-control.ascent-partners.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://internal-control.ascent-partners.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "coso-internal-control-mcp": {
      "serverUrl": "https://internal-control.ascent-partners.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like COSO Internal Control MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,987

Do you run COSO Internal Control MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing