io.github.figranium/figranium-mcp

MCPcommunity
v0.1.0io.github.figraniumUnknownUpdated 1mo agoGitHub

MCP server implementation for Figranium

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.figranium
LicenseUnknown
Version0.1.0
Sourcemcp-registry
GitHubfigranium/figranium-mcp.git
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 surface14 tools · 2 privileged
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 11, 2026

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

Tools

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

create_taskNo description published

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

task_updateNo description published

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

task_deleteprivilegedNo description published

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

task_listNo description published

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

browser_openNo description published

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

inspector_highlightNo description published

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

task_executeNo description published

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

execution_listNo description published

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

schedule_listNo description published

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

schedule_get_all_statusNo description published

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

schedule_get_statusNo description published

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

schedule_setNo description published

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

schedule_deleteprivilegedNo description published

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

schedule_describeNo description published

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

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

MCP server implementation for Figranium

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

14 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.