Skip to content

Maha Context Review

by mahastrategies.com · remote · no sign-in to list tools · v1.0.2 · published by com.mahastrategies

Reduce supplied context and check caller-declared, source-specific exact evidence retention.

Changes · 1

1 tool: 1 change things.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http context-review https://www.mahastrategies.com/api/mcp/context-review?channel=registry

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "review_context_retention" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "select": a word for a change.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...downstream prompt capture. Do not send credentials, government IDs, payment card data, pro..."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Changes things 1Claude Code: ask
  • review_context_retentionSelect passages from explicitly supplied sanitized documents under an estimated token budget, and check whether user-declared exact evidence excerpts remain in selected passages fr…2 findings

    Why it is in this group

    • The description's first verb is "select": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...downstream prompt capture. Do not send credentials, government IDs, payment card data, pro..."

      What this check looks for
    • Warn

      The server marks "review_context_retention" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "select": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Select passages from explicitly supplied sanitized documents under an estimated token budget, and check whether user-declared exact evidence excerpts remain in selected passages from their specified source. No web access, storage, payments, semantic correctness guarantee, or downstream prompt capture. Do not send credentials, government IDs, payment card data, protected health information, or confidential personal records.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http context-review https://www.mahastrategies.com/api/mcp/context-review?channel=registry

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__context-review__review_context_retention"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as context-review. Review it before you use it.