Securedact MCP
PYPI · SECUREDACT-MCP
Local-first privacy MCP server for sensitive AI workflows
Available components
Last scanned (5 hours ago)
Scores higher than 82% of PyPI servers
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to GigantesHJI/securedact-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 50 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability42
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 223 tokens (~44/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 −14
- Malware scan: pass → unverified ▼ security
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 6 Nov 2026 · Analysed pypi/securedact-mcp@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | GigantesHJI/securedact-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/GigantesHJI/securedact-mcp/.github/workflows/release.yml@refs/tags/v0.2.1 |
| Rekor log index | 2529115515 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:9e63030d1e581ce339ff396a46d0d80705bacdb472c243ffcd1fc04b85366be0 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_text ~43
Lower-level local review tool; raw details require enabled debug mode.
| Name | Type | Req | Description |
|---|---|---|---|
| policy | string | – | – |
| response_mode | string | – | – |
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_safe_copy ~41
Write sanitized content to the configured Safe Copies directory only.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| filename | string | yes | – |
| policy | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
prepare_for_external_ai ~51
Recommended: prepare text locally and return only approved safe output.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| policy | string | – | – |
| response_mode | string | – | – |
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
redact_text ~41
Lower-level compatibility tool; prefer prepare_for_external_ai.
| Name | Type | Req | Description |
|---|---|---|---|
| policy | string | – | – |
| response_mode | string | – | – |
| text | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
restore_text ~47
Restore an opaque session; direct mappings require explicit legacy mode.
| Name | Type | Req | Description |
|---|---|---|---|
| mapping | – | – | – |
| restoration_session | – | – | – |
| text | string | yes | – |
| trusted_local_review | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Securedact MCP server?
Securedact MCP runs locally as a PyPI package, launched with uvx securedact-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · securedact-mcp
claude mcp add giganteshji-securedact-mcp -- uvx securedact-mcp
What is the Securedact MCP server?
Securedact MCP is listed in the public MCP registry as io.github.GigantesHJI/securedact-mcp. Local-first privacy MCP server for sensitive AI workflows. This page covers its PyPI package (securedact-mcp).
Is the Securedact MCP server safe to use?
Securedact MCP scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. Its build provenance is signed and verified. 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 Securedact MCP server expose?
Securedact MCP exposes 5 tools: prepare_for_external_ai, analyze_text, redact_text, restore_text, create_safe_copy. Their descriptions and schemas cost roughly 223 tokens of context every time the server is loaded.
Is the Securedact MCP server still maintained?
Securedact MCP is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Securedact MCP server under?
Securedact MCP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Securedact MCP server?
VerifyMCP ran 16 checks on Securedact MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.