@zyno-io/zynohosting

MCPattested
v0.4.5io.github.zyno-ioUnknownUpdated 2mo agonpmGitHub

Manage ZynoHosting sites and create, discover, embed, and configure ZynoForms through local stdio.

Works in
ClaudeCursorCopilotGemini

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

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
2mo agoLast update
Package
Authorio.github.zyno-io
LicenseUnknown
Version0.4.5
Sourcenpm+mcp-registry
npm@zyno-io/zynohosting
GitHubzyno-io/zynohosting-cli
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—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)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · f165e02
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface18 tools · 1 privileged
Security scan✓ Cleanv0.4.5 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 18, 2026

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

Tools

18 tools · 1 privileged
Statically extracted from the published packagev0.4.5 · 1mo 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.

list_formsNo description published

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

get_form_integrationNo description published

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

create_basic_formNo description published

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

describe_formNo description published

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

update_formNo description published

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

update_form_bot_protectionNo description published

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

update_form_originsNo description published

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

loginNo description published

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

list_sitesNo description published

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

get_siteNo description published

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

list_filesNo description published

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

get_fileNo description published

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

put_fileNo description published

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

delete_fileprivilegedNo description published

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

plan_deployNo description published

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

apply_deployNo description published

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

plan_downloadNo description published

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

apply_downloadNo description published

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

0 of 18 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

Manage ZynoHosting sites and create, discover, embed, and configure ZynoForms through local stdio.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

18 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 package was last scanned before Forge began storing the resolved tree. The next scan will record it.