Is the Ascent Partners Coso MCP server down?

mcp-registry/com.ascent-partners/coso-mcp · v0.1.1

As of 2026-10-24 19:23 UTC, the Ascent Partners Coso MCP server is unknown with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.3% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 2 minutes.

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

Point your MCP client at this streamable-http endpoint: https://internal-control.ascent-partners.com/mcp

Agent-readiness: D (64/100)

What to fix (5)

Auto-fix: 26 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 33 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.ascent-partners%2Fcoso-mcp/fixes

{
  "name": "add_review_note",
  "description": "Add a reviewer note to a workpaper.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "engagementId",
      "workpaperId",
      "text"
    ],
    "properties": {
      "text": {
        "type": "string",
        "minLength": 1
      },
      "author": {
        "type": "string",
        "minLength": 1
      },
      "workpaperId": {
        "type": "string",
        "pattern": "^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$"
      },
      "engagementId": {
        "type": "string",
        "pattern": "^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add a review note"
}

{
  "name": "add_scope_item",
  "description": "Add a significant account/process to the review scope, with its objective category and assertions.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "engagementId",
      "area",
      "objectiveCategory"
    ],
    "properties": {
      "area": {
        "type": "string",
        "minLength": 1,
        "description": "Significant account or process."
      },
      "inScope": {
        "type": "boolean",
        "default": true
      },
      "rationale": {
        "type": "string"
      },
      "assertions": {
        "type": "array",
        "items": {
          "enum": [
            "completeness",
            "existence-occurrence",
            "accuracy",
            "valuation",
            "obligations-rights",
            "presentation-disclosure"
          ],
          "type": "string"
        },
        "default": []
      },
      "engagementId": {
        "type": "string",
        "pattern": "^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$"
      },
      "objectiveCategory": {
        "enum": [
          "operations",
          "reporting",
          "compliance"
        ],
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Add a scope item"
}

{
  "name": "create_engagement",
  "description": "Create a new internal-control review engagement. Returns the engagement id used by all later tools.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "title",
      "entity"
    ],
    "properties": {
      "id": {
        "type": "string",
        "pattern": "^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$",
        "description": "Optional explicit engagement id."
      },
      "title": {
        "type": "string",
        "minLength": 1,
        "description": "Engagement title."
      },
      "entity": {
        "type": "string",
        "minLength": 1,
        "description": "Entity or business unit under review."
      },
      "period": {
        "type": "string",
        "minLength": 1,
        "description": "Review period, e.g. 2025 or 2025-H2."
      },
      "materiality": {
        "type": "object",
        "properties": {
          "basis": {
            "type": "string"
          },
          "amount": {
            "type": "number"
          },
          "currency": {
            "type": "string"
          }
        }
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Create an engagement"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.ascent-partners/coso-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.ascent-partners/coso-mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~5,463 tokens).
• Tool names are unique and portable across clients.
• No breaking contract changes in 30 days.

Largest tool definitions

• classify_deficiency ~355 tokens
• record_test_result ~325 tokens
• register_control ~318 tokens
• register_risk ~264 tokens
• select_sample ~262 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ascent-partners%2Fcoso-mcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.ascent-partners%2Fcoso-mcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.ascent-partners%2Fcoso-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ascent-partners%2Fcoso-mcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.ascent-partners%2Fcoso-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.ascent-partners%2Fcoso-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:605a0222bea6de0c…, first seen 2026-10-17, included at leaf 5296 of 76,739. Version history · verify what your client received.

Tools (39)

• add_review_note
• add_scope_item
• aggregate_deficiencies
• assemble_workpaper
• assess_component
• assess_principle
• classify_deficiency
• compute_sample_size
• create_engagement
• create_population
• framework_integration_check
• generate_report
• get_activity_log
• get_audit_log
• get_component
• get_engagement
• get_principle
• get_server_info
• get_workpaper
• list_assertions
• list_components
• list_controls
• list_deficiencies
• list_engagements
• list_exceptions
• list_objective_categories
• list_populations
• list_principles
• list_risks
• list_scope_items
• list_test_results
• list_workpapers
• note_exception
• record_test_result
• register_control
• register_risk
• resolve_review_note
• select_sample
• sign_off

Compare: most reliable communication servers · most reliable other servers · most reliable data servers · most reliable productivity servers · most reliable retrieval servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Ascent Partners Coso MCP server down right now?

As of 2026-10-24 19:23 UTC, the Ascent Partners Coso MCP server is unknown with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.3% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Ascent Partners Coso MCP server provide?

Ascent Partners Coso MCP server advertises 39 tools, including add_review_note, add_scope_item, aggregate_deficiencies, assemble_workpaper, assess_component.

How do I install Ascent Partners Coso MCP server?

Point your MCP client at this streamable-http endpoint: https://internal-control.ascent-partners.com/mcp

Is the Ascent Partners Coso MCP server safe to connect to an AI agent?

Glimind scanned all 39 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Ascent Partners Coso MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.