Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Figranium MCP

OCI · GHCR.IO/FIGRANIUM/FIGRANIUM-MCP:0.1.0 · SCANNED AUG 22

MCP server implementation for Figranium

+3 this week 39 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency6
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2282 tokens (~207/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/figranium/figranium-mcp:0.1.0

# add to Claude Code
claude mcp add figranium-figranium-mcp -- docker run --rm -i ghcr.io/figranium/figranium-mcp:0.1.0
# add to Codex CLI
codex mcp add figranium-figranium-mcp -- docker run --rm -i ghcr.io/figranium/figranium-mcp:0.1.0
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "figranium-figranium-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/figranium/figranium-mcp:0.1.0"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  figranium-figranium-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/figranium/figranium-mcp:0.1.0"]
// mcp.json
{
  "mcpServers": {
    "figranium-figranium-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/figranium/figranium-mcp:0.1.0"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Aug 26 +3
    • Stability: unverified → 0.23 functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 0
    • Security disclosure: fail → unverified functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Aug 2026 · Analysed oci/ghcr.io/figranium/figranium-mcp:0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published
MCP tools · 10 exposed · ~2,249 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
create_task ~1,600

Create a complete, fully-configured Figranium automation task including sequential action steps, state variables, anti-bot stealth mechanisms, and optional scheduling. ### 1. Purpose Use this tool when you need to automate any recurring or complex web-based workflows, including data extraction (scraping), automated form-filling, dashboard testing, or dynamic visual monitoring. Tasks are stored permanently in Figranium and can be executed ad-hoc, triggered via API, or scheduled. ### 2. Execution Model Figranium tasks run as a linear sequence of steps defined in the 'actions' array. Actions are processed in order from top to bottom. Control flow steps (such as 'if', 'while', 'repeat') allow loops and branching, while 'on_error' steps define fallback behaviors. Variables represent the state and can be updated dynamically during execution. ### 3. Comprehensive Step Types - 'navigate': Redirect browser to a new URL specified in the 'value' field. - 'wait': Pause execution for N seconds specified in the 'value' field. - 'wait_selector': Pause until the DOM element matching 'selector' is rendered. - 'click': Simulate a realistic click on the element matching 'selector'. - 'type': Type the 'value' into the 'selector' input element. Use 'typeMode' to clear/replace or append. - 'hover': Move mouse pointer to the element matching 'selector'. - 'press': Press a specific keyboard key (e.g., 'Enter') specified in the 'key' field. - 'scroll': Scroll the page or target element to a specific coordinate or direction. - 'javascript': Execute custom JavaScript on the page. Stored in 'value', outputs can be saved to 'varName'. - 'screenshot': Capture and save a screenshot. - 'http_request': Perform direct API requests. - 'if', 'else', 'end': Conditional blocks based on variables. - 'while', 'repeat', 'foreach': Looping blocks. - 'stop': Halt task execution. - 'set': Set or update a task variable. ### 4. Selector Strategy & Fallbacks When targeting elements, follow this hierarchy o…

NameTypeReqDescription
actionsarraySequential list of browser actions/control flow steps to execute.
descriptionstringDetailed description of what the task automates. Expected type: string. Example: 'Logs in and extracts weekly leads'
disableRecordingbooleanDisable video/VNC recording of this task to save storage. Expected type: boolean. Example: true
extractionFormatstringTarget export format of any extracted data. Expected type: string enum. Example: 'json'
extractionScriptstringOptional post-execution script to extract data. Expected type: string. Example: 'return Array.from(document.querySelectorAll("a")).map(el => el.href)'
humanTypingbooleanVary typing speeds and insert tiny delays to simulate organic human typing. Expected type: boolean. Example: true
includeHtmlbooleanWhether to include the raw page HTML in the execution response. Expected type: boolean. Example: false
includeShadowDombooleanWhether to parse and resolve target elements residing in Shadow DOMs. Expected type: boolean. Example: true
modestringyesExecution mode. 'scrape' is fast and headless; 'agent' uses automated browser interaction; 'headful' runs in a visible browser window with human oversight. Expected type: string enum. Example: 'agent'
namestringyesDescriptive name of the automation task. Expected type: string. Example: 'HackerNews Scraper'
rotateProxiesbooleanRotate through configured proxy IPs to prevent IP-based rate limiting. Expected type: boolean. Example: false
rotateUserAgentsbooleanRotate user agents across requests to avoid pattern blocking and fingerprinting. Expected type: boolean. Example: true
rotateViewportbooleanVary viewport resolutions randomly to simulate multiple desktop and mobile devices. Expected type: boolean. Example: true
scheduleobjectTask automatic execution schedule. Expected type: object.
selectorstringDefault CSS selector to wait for on the page load before starting actions. Expected type: string. Example: '.main-content'
statelessExecutionbooleanIf set to true, clear browser cookies and session states between runs. Expected type: boolean. Example: false
stealthobjectConfigures realistic stealth, anti-bot, and human behavior simulation on the browser instance.
urlstringyesInitial URL to navigate to when the task starts. Expected type: string. Example: 'https://news.ycombinator.com'
variablesobjectTask variables to store state and dynamic values. Expected type: record object of variable configurations.
waitnumberStandard delay in seconds to wait after navigation and page loads to let dynamic scripts complete. Expected type: number. Example: 5

No output schema declared.

No examples provided.

execution_list ~17

List a summary of all past execution records.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

schedule_delete ~37

Disable and remove the schedule configuration from a specific task.

NameTypeReqDescription
taskIdstringyesThe unique ID of the task whose schedule to delete.

No output schema declared.

No examples provided.

schedule_describe ~213

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

NameTypeReqDescription
cronExpressionstringStandard 5-field cron expression. Used if scheduleMode is 'cron'.
dayOfMonthnumberDay of the month (1-31) if frequency is 'monthly'.
daysOfWeekarrayArray of days of the week if frequency is 'weekly'.
frequencystringThe frequency mode. Used if scheduleMode is 'frequency'.
intervalMinutesnumberInterval in minutes if frequency is 'interval'.
scheduleHournumberHour of execution (0-23) if frequency is 'daily', 'weekly', or 'monthly'.
scheduleMinutenumberMinute of execution (0-59) if frequency is 'daily', 'weekly', or 'monthly'.
scheduleModestringyesWhether to define the schedule using 'cron' or structured 'frequency' fields.
taskIdstringyesThe unique ID of the task.

No output schema declared.

No examples provided.

schedule_get_all_status ~20

Get overall scheduler status and metadata for all schedules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

schedule_get_status ~43

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

NameTypeReqDescription
taskIdstringyesThe unique ID of the task to check.

No output schema declared.

No examples provided.

schedule_list ~20

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

schedule_set ~224

Create or update a schedule for a specific task.

NameTypeReqDescription
cronExpressionstringStandard 5-field cron expression. Used if scheduleMode is 'cron'.
dayOfMonthnumberDay of the month (1-31) if frequency is 'monthly'.
daysOfWeekarrayArray of days of the week if frequency is 'weekly'.
enabledbooleanyesWhether the schedule is active.
frequencystringThe frequency mode. Used if scheduleMode is 'frequency'.
intervalMinutesnumberInterval in minutes if frequency is 'interval'.
scheduleHournumberHour of execution (0-23) if frequency is 'daily', 'weekly', or 'monthly'.
scheduleMinutenumberMinute of execution (0-59) if frequency is 'daily', 'weekly', or 'monthly'.
scheduleModestringyesWhether to define the schedule using 'cron' or structured 'frequency' fields.
taskIdstringyesThe unique ID of the task to configure.

No output schema declared.

No examples provided.

task_execute ~53

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

NameTypeReqDescription
taskIdstringyesThe unique ID of the task to execute.
variablesobjectKey-value pairs representing the execution variables (optional).

No output schema declared.

No examples provided.

task_list ~22

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.