Put the check
before the context.

Keep the content with you.

Trismag 0.4.11 runs offline with Python 3.10 or newer. The installed engine has no third-party runtime dependencies, telemetry, account or API key. It inspects text, conversations and supplied tool metadata without contacting our servers.

SHA-256 checksum · Full local guide · Release details

Install, then inspect.

Once downloads open and you have the wheel, run these commands in a Python virtual environment from the folder containing it. This installs the downloaded file; it does not require a PyPI release.

python -m pip install ./trismag-0.4.11-py3-none-any.whl
python -m trismag --version
python -m trismag triage --text "The meeting is on Thursday."
python -m trismag triage --file document.txt --untrusted

The trismag command is also installed. Use --file - for UTF-8 stdin, --messages messages.json for a JSON array of up to eight messages, or --tools tools.json for supplied MCP tool metadata. Larger or incomplete inputs are refused rather than silently truncated.

Require the check in Python.

from trismag import inspect_or_raise

# Keep the document outside model context until this returns.
released = inspect_or_raise(document)
# Pass only released to your model. Let exceptions stop this path.

inspect_or_raise returns the unchanged text only after a complete LOW scan with untrusted provenance. Warnings raise ContentHeld; invalid or incomplete inputs raise InspectionError. For your own policy, use triage, triage_messages or triage_tools and inspect the JSON-compatible result.

The wheel includes the same detector source used by the API, but releases can be installed or deployed at different times. Compare engine_version locally with detector_version in the hosted response. A packaged local HTTP server, Docker image, native executable and npm package are not included in this release.

Let us run the service.

Call the hosted API from your server in any language. Content is sent to Trismag for inspection; read the hosted privacy policy before sending it. Anonymous previews show risk; a free key adds findings.

curl https://api.trismag.dev/v1/triage   -H "Content-Type: application/json"   -d '{"text":"The meeting is on Thursday."}'

Get a free hosted key → · Read the API quickstart → · Hosted allowances →

Your application must check the response before releasing content. Stop on errors, timeouts, exhausted quotas and incomplete scans. Local use does not consume hosted scan credits.

Fit inspection into your workflow.

These hosted integrations connect to the API. The n8n starter holds content until its inspection policy releases it. MCP offers scanning tools that an agent can choose to call; connecting it does not automatically intercept other content.

Require inspection with n8n → · Add optional MCP scanning → · HTTP and Make options →

Fetch. Inspect. Release or hold.

The starter fetches a harmless example document, scans its text and releases that same text only after a usable LOW response. Errors stop execution. Warnings and invalid verdicts never reach the release output.

1. Get a free key. Use Trismag’s key form. Current allowance: 500 scans per calendar month, with limited free usage continuing after September 30, 2026.
2. Import the JSON into n8n. In the Trismag HTTP node, create a Header Auth credential. Header name: Authorization. Value: Bearer YOUR_TRISMAG_KEY. Store your key in n8n Credentials, not the workflow file.
3. Run the included document. The ordinary sample should reach RELEASE. Change the fetch URL to the attack sample to exercise HOLD. The known limitation intentionally returns LOW.
4. Connect your content source and model. Prepare untrusted text must output a text string. Connect only RELEASE to the model, and use only that step’s $json.text. Keep HOLD disconnected from the model.
5. Check the failure paths. A missing key, exhausted allowance, timeout, bad JSON or incomplete response must not produce a released item. Never enable Continue On Fail, Always Output Data or Ignore Response Code to get around a failed inspection.

Saved success, error and manual execution data are disabled in this template. n8n still processes content and can display it while debugging; your instance logs, credentials, backups and retention settings are separate from Trismag’s privacy practices.

Updating an older import? Download and review this version, then replace your earlier workflow. Existing imports do not update automatically. The earlier starter checked only the risk label; this one also validates the response and rejects explicit incomplete scans.

Validated with 21 local executions in n8n 2.38.7. Verification scope is published in the n8n execution report. Local CLI execution is not a test of every n8n Cloud version or your downstream model. Make remains an earlier starting blueprint; it has not received this n8n runtime verification.

See where the content goes.

These examples explain the local test outcomes. Selecting one does not call the API or a model. They demonstrate both a useful warning and a known miss.

Ordinary document: LOW, RELEASE.

One endpoint. Optional inspection.

Remote Streamable HTTP endpoint: https://api.trismag.dev/mcp. Tools: check_text, check_conversation and check_tool_descriptions. Use your Trismag key in an Authorization header; Trismag does not provide an OAuth sign-in flow.

Cursor

Set TRISMAG_API_KEY in the environment Cursor inherits, then restart Cursor. The install link contains only an environment-variable reference, never your key. Cursor will ask you to review the configuration.

{
  "mcpServers": {
    "trismag": {
      "url": "https://api.trismag.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TRISMAG_API_KEY}"
      }
    }
  }
}

Based on Cursor’s install-link format and environment interpolation. The Cursor application installation itself has not been tested on this machine.

Claude Code

Set TRISMAG_API_KEY in the environment that launches Claude Code. Merge this entry into the project’s .mcp.json, review the server approval, then check its status with /mcp. Never commit a literal key.

{
  "mcpServers": {
    "trismag": {
      "type": "http",
      "url": "https://api.trismag.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${TRISMAG_API_KEY}"
      }
    }
  }
}

Configuration follows Claude Code’s remote HTTP documentation. The live protocol checks use the official MCP SDK, not a Claude Code session. Claude Desktop and other clients may have different remote-server and authentication support; no universal one-click compatibility is claimed.

Verify the connection

Confirm all three tools appear. Ask for a check_text call on the ordinary sample and inspect the actual tool result. A timeout, authentication failure, quota error, protocol error or isError: true is no verdict. Keep untrusted results out of context if your integration is meant to enforce inspection.

The SDK passed all three tool checks against a local synthetic account. Live discovery and error handling passed; live scan verdicts were unavailable because the test IP exhausted its public allowance.

Start small. Keep the evidence.

Use synthetic content first. Review missed attacks and benign warnings alongside successful detections. Neither this workflow nor an MCP connection guarantees complete protection.