figranium-mcp

MCPattested

v1.2.3io.github.figraniumApache-2.0Updated 5d agonpm GitHub

MCP server for Figranium, wrapping task execution, scheduling, and automation orchestration.

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.

499Downloads/wk

5GitHub stars

5d agoLast update

Package

Authorio.github.figranium

LicenseApache-2.0

Version1.2.3

Sourcenpm+mcp-registry

npmfigranium-mcp

GitHubfigranium/figranium-mcp

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 · 2e9b97c

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface16 tools · 2 privileged

Security scan✓ Cleanv1.2.3 · todayHow well does this scan work?

EvalsNone

IndexedSep 8, 2026

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

Tools

16 tools · 2 privileged

Statically extracted from the published packagev1.2.3 · 3h 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.

Filter toolsPrivileged only

create_taskNo description published

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

task_updateUpdate fields of an existing task on the Figranium server.

Update fields of an existing task on the Figranium server.

No input schema was published for this tool.

task_deleteprivilegedPermanently delete a Figranium task by taskId.

Permanently delete a Figranium task by taskId.

No input schema was published for this tool.

task_listList all task IDs, names, and descriptions from Figranium.

List all task IDs, names, and descriptions from Figranium.

No input schema was published for this tool.

browser_openLaunch or reattach a managed headful/interactive browser session.

Launch or reattach a managed headful/interactive browser session.

No input schema was published for this tool.

inspector_highlightActivate inspect/highlight mode on an active browser session with optional selector hints.

Activate inspect/highlight mode on an active browser session with optional selector hints.

No input schema was published for this tool.

task_executeExecute/run a saved automation task by ID and return its result.

Execute/run a saved automation task by ID and return its result.

No input schema was published for this tool.

execution_listList a summary of all past execution records.

List a summary of all past execution records.

No input schema was published for this tool.

schedule_listList all tasks that have schedules configured (enabled or not).

List all tasks that have schedules configured (enabled or not).

No input schema was published for this tool.

schedule_get_all_statusGet overall scheduler status and metadata for all schedules.

Get overall scheduler status and metadata for all schedules.

No input schema was published for this tool.

schedule_get_statusGet the detailed schedule status, cron configuration, and next run time for a specific task.

Get the detailed schedule status, cron configuration, and next run time for a specific task.

No input schema was published for this tool.

schedule_setCreate or update a schedule for a specific task.

Create or update a schedule for a specific task.

No input schema was published for this tool.

schedule_deleteprivilegedDisable and remove the schedule configuration from a specific task.

Disable and remove the schedule configuration from a specific task.

No input schema was published for this tool.

schedule_describeValidate and preview/describe a schedule configuration without saving it.

Validate and preview/describe a schedule configuration without saving it.

No input schema was published for this tool.

list_cabinetsList all Cabinets (durable download queues) configured on the Figranium server, including their IDs, names, and item counts. Use this to find a cabinetId to reference in a task's 'cabinetId' field or an 'upload' action.

List all Cabinets (durable download queues) configured on the Figranium server, including their IDs, names, and item counts. Use this to find a cabinetId to reference in a task's 'cabinetId' field or an 'upload' action.

No input schema was published for this tool.

create_cabinetCreate a new Cabinet (durable download queue) on the Figranium server.

Create a new Cabinet (durable download queue) on the Figranium server.

No input schema was published for this tool.

15 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

MCP server for Figranium, wrapping task execution, scheduling, and automation orchestration.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

16 tools · 2 privileged · observed 2026-09-11 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.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-11 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
@figranium/sdk0.2.0
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.7
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.2
- cors2.8.6+2 not drawn
- hono4.13.7
- jose6.2.12
- express5.2.1+27 not drawn1 dependency
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 50
below the depth cap: 5

es-define-property ^1.0.1 — required by qs@6.16.0package cap reached
wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.