io.github.mcpware/logoloom

MCPcommunity
v1.0.1io.github.mcpwareUnknownUpdated 6mo agoGitHub

AI logo design → SVG → full brand kit. Text-to-path, optimize, export PNG/ICO/WebP.

One command. Full brand kit. Zero cost. Stop juggling 5 tools for your logo. Getting a logo for your side project shouldn't cost $96 (Looka) or require juggling Canva + favicon generator + OG image maker + manual PNG exports. Logo is the #1 shipping blocker for indie devs — not because it's hard, but because the tooling sucks. AI designs your logo as clean SVG code (not messy auto-traced paths),…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
36GitHub stars
5Forks
6mo agoLast update
Package
Authorio.github.mcpware
LicenseUnknown
Version1.0.1
Sourcemcp-registry
GitHubmcpware/logoloom
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 surface4 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

4 tools · none privileged
Statically extracted from the published packagevHEAD · 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.

text_to_pathNo description published

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

optimize_svgNo description published

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

export_brand_kitNo description published

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

image_to_svgNo description published

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

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

One command. Full brand kit. Zero cost. Stop juggling 5 tools for your logo. Getting a logo for your side project shouldn't cost $96 (Looka) or require juggling Canva + favicon generator + OG image maker + manual PNG exports. Logo is the #1 shipping blocker for indie devs — not because it's hard, but because the tooling sucks. AI designs your logo as clean SVG code (not messy auto-traced paths), then post-processes into a complete brand kit — 31 files, one command: SVG — full logo, icon only,…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

4 tools · none 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.