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.

com.ascent-partners/coso-mcp

REMOTE · INTERNAL-CONTROL.ASCENT-PARTNERS.COM · 2 COMPONENTS

Open COSO internal-control review MCP: scope, risk, controls, sampling, testing, workpapers.

65 Trust /100

Last scanned (4 hours ago)

Scores higher than 47% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Finance and Payments

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 Security63
Transport & Reachability100
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1978 tokens (~49/item across 40 items; 39 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 8% of tool parameters carry a description.Partial
  • 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 39 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 40 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.

  • 15 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 14 Oct 26 64

    First indexed and scored.

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 17 Oct 2026 · Probed https://internal-control.ascent-partners.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ascent-partners.com CN=YE2,O=Let's Encrypt,C=US 13 Oct 2026 11 Jan 2027 ECDSA 256 ECDSA-SHA384 5022c93727c48b52a7127597de7a37383be
SANs: *.ascent-partners.com, ascent-partners.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of internal-control.ascent-partners.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
ascent-partners.com. absent 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://internal-control.ascent-partners.com/mcp Verified 200
http (plaintext) http://internal-control.ascent-partners.com/mcp HTTPS enforced 308 https://internal-control.ascent-partners.com/mcp
MCP tools · 39 exposed · ~1,948 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
add_review_note ~49

Add a reviewer note to a workpaper.

NameTypeReqDescription
authorstring––
engagementIdstringyes–
textstringyes–
workpaperIdstringyes–
NameTypeReqDescription
note–yes–
workpaper–yes–

No examples provided.

add_scope_item ~75

Add a significant account/process to the review scope, with its objective category and assertions.

NameTypeReqDescription
areastringyesSignificant account or process.
assertionsarray––
engagementIdstringyes–
inScopeboolean––
objectiveCategorystringyes–
rationalestring––
NameTypeReqDescription
scopeItem–yes–

No examples provided.

aggregate_deficiencies ~43

Group related deficiencies by control, flag combinations that may aggregate, and report the overall severity.

NameTypeReqDescription
deficiencyIdsarray––
engagementIdstringyes–
NameTypeReqDescription
aggregation–yes–

No examples provided.

assemble_workpaper ~71

Assemble a Markdown control-testing workpaper from the control, its risks, population, sample, test results and exceptions.

NameTypeReqDescription
controlIdstringyes–
engagementIdstringyes–
testResultIdstring–Restrict to a single test result.
titlestring––
NameTypeReqDescription
workpaper–yes–

No examples provided.

assess_component ~37

Report coverage indicators for one COSO component, aggregating its principles.

NameTypeReqDescription
engagementIdstringyes–
idstringyes–
NameTypeReqDescription
assessment–yes–
foundbooleanyes–

No examples provided.

assess_principle ~45

Report data-driven coverage indicators for one COSO principle (controls, risks and deficiencies mapped to it).

NameTypeReqDescription
engagementIdstringyes–
numberintegeryes–
NameTypeReqDescription
assessment–yes–
foundbooleanyes–

No examples provided.

classify_deficiency ~119

Classify a control deficiency as deficiency / significant deficiency / material weakness from likelihood × magnitude (escalates for a pervasive control).

NameTypeReqDescription
compensatingControlstring––
controlIdstring––
descriptionstringyes–
engagementIdstringyes–
exceptionIdsarray––
likelihoodstringyes–
magnitudestringyes–
pervasiveboolean––
remediationobject––
testResultIdstring––
titlestringyes–
NameTypeReqDescription
deficiency–yes–

No examples provided.

compute_sample_size ~70

Recommend a sample size for a control from its frequency, risk and population size, with a documented rationale.

NameTypeReqDescription
externalRelianceboolean––
frequencystringyes–
populationSizeinteger––
priorDeficiencyboolean––
riskstring––
NameTypeReqDescription
cappedbooleanyes–
effectiveRiskstringyes–
frequencystringyes–
populationSizenumber––
rationalestringyes–
recommendednumberyes–
requestedRiskstringyes–

No examples provided.

create_engagement ~90

Create a new internal-control review engagement. Returns the engagement id used by all later tools.

NameTypeReqDescription
entitystringyesEntity or business unit under review.
idstring–Optional explicit engagement id.
materialityobject––
periodstring–Review period, e.g. 2025 or 2025-H2.
titlestringyesEngagement title.
NameTypeReqDescription
engagementobjectyes–

No examples provided.

create_population ~85

Register the population for a control — either an explicit item list or a declared size. Bounded to 10000 items.

NameTypeReqDescription
controlIdstring––
currencystring––
declaredSizeinteger––
descriptionstringyes–
engagementIdstringyes–
itemsarray––
periodstring––
NameTypeReqDescription
population–yes–

No examples provided.

framework_integration_check ~35

Check that all five COSO components have some recorded coverage and that principles are addressed.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
componentsarrayyes–
integration–yes–

No examples provided.

generate_report ~41

Generate a Markdown internal-control review report: scope, risks, controls, testing, workpapers, deficiencies and COSO coverage.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
counts–yes–
markdownstringyes–

No examples provided.

get_activity_log ~32

Return the append-only activity log for an engagement, plus a Markdown rendering.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
countnumberyes–
eventsarrayyes–
markdownstringyes–

No examples provided.

get_audit_log ~29

Return the append-only audit events recorded for an engagement.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
countnumberyes–
eventsarrayyes–

No examples provided.

get_component ~28

Return a single COSO component by id, with its principles.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
component–yes–
foundbooleanyes–

No examples provided.

get_engagement ~22

Return an engagement by id.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
engagement–yes–
foundbooleanyes–

No examples provided.

get_principle ~45

Return a single COSO principle by framework number or slug, including its paraphrased points of focus.

NameTypeReqDescription
idstring––
numberinteger––
NameTypeReqDescription
foundbooleanyes–
principle–yes–

No examples provided.

get_server_info ~26

Return the server identity, the COSO framework it covers, and the mandatory disclaimer.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstringyes–
disclaimerstringyes–
frameworkstringyes–
namestringyes–
titlestringyes–
versionstringyes–

No examples provided.

get_workpaper ~35

Return a workpaper including its rendered Markdown.

NameTypeReqDescription
engagementIdstringyes–
workpaperIdstringyes–
NameTypeReqDescription
foundbooleanyes–
workpaper–yes–

No examples provided.

list_assertions ~37

List the assertions used to frame control objectives: completeness, existence/occurrence, accuracy, valuation, obligations/rights, presentation/disclosure.

Input schema present but exposes no named parameters.

NameTypeReqDescription
assertionsarrayyes–
countnumberyes–

No examples provided.

list_components ~28

List the five components of the COSO Internal Control—Integrated Framework (ICIF-2013).

Input schema present but exposes no named parameters.

NameTypeReqDescription
componentsarrayyes–
countnumberyes–
frameworkstringyes–

No examples provided.

list_controls ~24

List the controls registered for an engagement.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
controlsarrayyes–
countnumberyes–

No examples provided.

list_deficiencies ~25

List the deficiencies recorded for an engagement.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
countnumberyes–
deficienciesarrayyes–

No examples provided.

list_engagements ~17

List all engagement ids and titles.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumberyes–
engagementsarrayyes–

No examples provided.

list_exceptions ~25

List the exceptions recorded for an engagement.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
countnumberyes–
exceptionsarrayyes–

No examples provided.

list_objective_categories ~24

List the three COSO objective categories (operations, reporting, compliance).

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumberyes–
objectiveCategoriesarrayyes–

No examples provided.

list_populations ~25

List the populations registered for an engagement.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
countnumberyes–
populationsarrayyes–

No examples provided.

list_principles ~46

List the 17 principles of the COSO ICIF-2013, optionally filtered to a single component.

NameTypeReqDescription
componentstring–Restrict to a single component id.
NameTypeReqDescription
countnumberyes–
frameworkstringyes–
principlesarrayyes–

No examples provided.

list_risks ~26

List the risks registered for an engagement.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
countnumberyes–
risksarrayyes–

No examples provided.

list_scope_items ~25

List the scope items for an engagement.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
countnumberyes–
scopeItemsarrayyes–

No examples provided.

list_test_results ~26

List the test results recorded for an engagement.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
countnumberyes–
testResultsarrayyes–

No examples provided.

list_workpapers ~26

List the workpapers assembled for an engagement.

NameTypeReqDescription
engagementIdstringyes–
NameTypeReqDescription
countnumberyes–
workpapersarrayyes–

No examples provided.

note_exception ~89

Record an exception identified during testing, with root cause, impact and any compensating control.

NameTypeReqDescription
compensatingControlstring––
descriptionstringyes–
engagementIdstringyes–
impactstring––
referencestringyesThe sample item reference the exception relates to.
rootCausestring––
testResultIdstringyes–
NameTypeReqDescription
exception–yes–

No examples provided.

record_test_result ~104

Record attribute-level outcomes (pass/fail/na) for a tested sample, with an optional conclusion.

NameTypeReqDescription
attributestringyesThe control attribute/objective tested.
conclusionstring––
controlIdstringyes–
engagementIdstringyes–
populationIdstring––
preparedBystring––
procedurestring––
resultsarrayyes–
sampleIdstringyes–
NameTypeReqDescription
testResult–yes–

No examples provided.

register_control ~101

Register a key control with its type, frequency, linked risks, assertions and COSO principles.

NameTypeReqDescription
assertionsarray––
descriptionstringyes–
engagementIdstringyes–
frequencystringyes–
keyboolean––
ownerstring––
principlesarray––
riskIdsarray––
scopeItemIdstring––
typestringyes–
NameTypeReqDescription
control–yes–

No examples provided.

register_risk ~95

Register a risk to objectives, with likelihood, assertions, related COSO principles and a fraud flag.

NameTypeReqDescription
assertionsarray––
causestring––
descriptionstringyes–
engagementIdstringyes–
fraudboolean––
impactstring––
likelihoodstring––
principlesarray––
scopeItemIdstring––
NameTypeReqDescription
risk–yes–

No examples provided.

resolve_review_note ~52

Mark a review note resolved on a workpaper.

NameTypeReqDescription
engagementIdstringyes–
noteIdstringyes–
resolvedBystring––
workpaperIdstringyes–
NameTypeReqDescription
note–yes–
workpaper–yes–

No examples provided.

select_sample ~106

Select a reproducible sample from a population. Seeded (deterministic) for random/systematic/haphazard; targeted takes explicit references. Records the method, seed and references.

NameTypeReqDescription
controlIdstring––
engagementIdstringyes–
methodstringyes–
populationIdstringyes–
rationalestring––
sampleSizeinteger––
seedinteger––
targetedReferencesarray––
NameTypeReqDescription
sample–yes–

No examples provided.

sign_off ~70

Record a preparer or reviewer sign-off. Warns (does not block) if the same person prepared and reviewed.

NameTypeReqDescription
actorstring––
commentstring––
engagementIdstringyes–
rolestringyes–
workpaperIdstringyes–
NameTypeReqDescription
warningstring––
workpaper–yes–

No examples provided.

Install

How do I install the com.ascent-partners/coso-mcp server?

com.ascent-partners/coso-mcp is a hosted endpoint at https://internal-control.ascent-partners.com/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 · internal-control.ascent-partners.com

# add to Claude Code
claude mcp add --transport http com-ascent-partners-coso-mcp 'https://internal-control.ascent-partners.com/mcp'
Common questions

What is the com.ascent-partners/coso-mcp server?

com.ascent-partners/coso-mcp is listed in the public MCP registry as com.ascent-partners/coso-mcp. Open COSO internal-control review MCP: scope, risk, controls, sampling, testing, workpapers. This page covers its hosted endpoint (https://internal-control.ascent-partners.com/mcp).

Is the com.ascent-partners/coso-mcp server safe to use?

com.ascent-partners/coso-mcp scores 65 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 com.ascent-partners/coso-mcp server expose?

com.ascent-partners/coso-mcp exposes 39 tools: get_server_info, list_components, list_principles, get_principle, get_component, and 34 more. Their descriptions and schemas cost roughly 1,948 tokens of context every time the server is loaded.

Does the com.ascent-partners/coso-mcp server require authentication?

No. We connected to com.ascent-partners/coso-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.ascent-partners/coso-mcp server still maintained?

com.ascent-partners/coso-mcp is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.