io.github.kuyazee/artifacts

MCPcommunity
v1.0.0io.github.kuyazeeUnknownUpdated 3mo agoGitHub

Self-hosted artifact publishing: POST HTML/JSX/Markdown/zip, get an unguessable URL on your domain

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.kuyazee
LicenseUnknown
Version1.0.0
Sourcemcp-registry
GitHubkuyazee/artifacts
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface12 tools · 2 privileged
Security scan✓ CleanvHEAD · 2mo agoHow well does this scan work?
EvalsNone
IndexedJul 9, 2026

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

Tools

12 tools · 2 privileged
Statically extracted from the published packagevHEAD · 2mo 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.

publish_artifactNo description published

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

update_artifactNo description published

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

rename_artifactprivilegedNo description published

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

set_artifact_expiryNo description published

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

set_artifact_tagsNo description published

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

set_artifact_projectNo description published

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

set_artifact_visibilityNo description published

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

disable_artifactNo description published

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

enable_artifactNo description published

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

set_artifact_frameNo description published

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

list_artifactsNo description published

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

delete_artifactprivilegedNo description published

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

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

Self-hosted artifact publishing: POST HTML/JSX/Markdown/zip, get an unguessable URL on your domain

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

12 tools · 2 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.