io.github.treza-labs/treza

MCPcommunitylive
v1.0.2io.github.treza-labsUnknownUpdated 7d agoGitHub

Build, run, schedule, and publish AI video pipelines to YouTube and TikTok from any MCP client.

Endpoint healthlive
checked 6 days ago · 2276ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
7d agoLast update
Package
Authorio.github.treza-labs
LicenseUnknown
Version1.0.2
Sourcemcp-registry
GitHubtreza-labs/treza-plugin
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface16 tools · 1 privileged
Security scan✓ Cleanv0.1.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

16 tools · 1 privileged
Statically extracted from the published packagev0.1.1 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

treza_list_enclavesNo description published

This tool published no description. Forge does not invent one.

treza_get_enclaveNo description published

This tool published no description. Forge does not invent one.

treza_create_enclaveNo description published

This tool published no description. Forge does not invent one.

treza_update_enclaveNo description published

This tool published no description. Forge does not invent one.

treza_delete_enclaveprivilegedNo description published

This tool published no description. Forge does not invent one.

treza_enclave_actionNo description published

This tool published no description. Forge does not invent one.

treza_get_enclave_logsNo description published

This tool published no description. Forge does not invent one.

treza_get_attestationNo description published

This tool published no description. Forge does not invent one.

treza_verify_attestationNo description published

This tool published no description. Forge does not invent one.

treza_get_verification_statusNo description published

This tool published no description. Forge does not invent one.

treza_list_providersNo description published

This tool published no description. Forge does not invent one.

treza_get_providerNo description published

This tool published no description. Forge does not invent one.

treza_list_tasksNo description published

This tool published no description. Forge does not invent one.

treza_create_taskNo description published

This tool published no description. Forge does not invent one.

treza_list_api_keysNo description published

This tool published no description. Forge does not invent one.

treza_create_api_keyNo description published

This tool published no description. Forge does not invent one.

0 of 16 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Build, run, schedule, and publish AI video pipelines to YouTube and TikTok from any MCP client.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

16 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.