coso-mcp
Related Servers
Alternatives to coso-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables DORA ICT governance and compliance workflows through 10 MCP tools for managing audit findings, generating board reports, reviewing frameworks, tracking controls, exceptions, remediation actions, KPIs, and annual compliance evidence.-
- FlicenseNot gradedqualityDmaintenanceEnables DORA Article 8 change management through MCP tools for registering and tracking changes, assessing risk, validating approvals, rollback plans, and test evidence, checking patch compliance and segregation of duties, and viewing change statistics and server health.-
- FlicenseNot gradedqualityDmaintenanceEnables DORA-compliant ICT contract management through 10 MCP tools, including mandatory clause checking, critical/important function analysis, subcontracting chain assessment, exit readiness evaluation, and risk scoring.-
- AlicenseAqualityBmaintenanceEnables AI agents to screen journal entries against 11 rules, prioritize them by risk score, and run balance checks, duplicate detection, and Benford analysis via MCP.573 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to check code changes against architecture and business rules, assess dependency impact before edits, verify violations after edits, and record tamper-evident audit evidence through MCP tools.4Apache 2.0
- AlicenseAqualityBmaintenanceEnables institutional bond valuation, FINRA TRACE spread analysis, portfolio VaR/CVaR stress testing, OFAC SDN screening and safe-harbor certificates, plus SEC XBRL forensic and whistleblower workpapers through MCP tools.111MIT
TDQS
Scored across 39 tools
Most tools map to a clearly distinct resource+action in the audit lifecycle (engagement, scope, risk, control, population, sample, test result, exception, workpaper, deficiency, report). The main overlap is get_audit_log vs get_activity_log, both described as append-only per-engagement logs, and the classify/aggregate/list_deficiencies trio requires reading descriptions to separate. Overall boundaries are clear enough that an agent can select correctly.
Nearly all tools follow a consistent snake_case verb_noun pattern (create_engagement, register_risk, select_sample, list_exceptions). Deviations are minor: sign_off is verb-only, framework_integration_check puts the verb last, and assessment tools use assess_/classify_/aggregate_ prefixes that still read consistently.
39 tools is heavy for a single MCP server, and the surface is inflated by many near-duplicate list_* tools (list_risks, list_controls, list_scope_items, list_populations, list_test_results, list_exceptions, list_workpapers, list_deficiencies) that could be one parameterized list endpoint. Each tool is individually defensible for a full audit lifecycle, but the set is larger than the workflow strictly requires.
The surface covers the whole engagement lifecycle end-to-end: setup, scoping, risk/control registration, sampling, testing, exceptions, workpapers, review notes, sign-off, deficiency classification, COSO coverage assessment, and reporting. Gaps are minor: there are no update/delete operations for engagements, risks, controls, or scope items, so corrections must be appended rather than amended.