securedact-mcp

Purpose: Running sensitive AI workflows without sending private data to external services.

Inferred · not functionally tested

Audience: developers building privacy-sensitive AI workflows

Inferred · not functionally tested

Functions: agents, data_extraction

Inferred · not functionally tested

Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Apache-2.0 · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

securedact-mcp is an AI & LLM security project. Inferred · not functionally tested: It focuses on running sensitive AI workflows without sending private data to external services. Inferred · not functionally tested: It is built as an open-source project for developers building privacy-sensitive AI workflows. Basis unknown · not verified: securedact-mcp is open source under the Apache-2.0 license. Basis unknown · not verified: It ships for the command line, and it can be self-hosted.

It is developed by GigantesHJI, and it first shipped in 2026. Development happens publicly on GitHub with 48 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include local processing, MCP server, and privacy controls. Basis unknown · not verified: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.