# Figranium MCP (oci · ghcr.io/figranium/figranium-mcp:0.1.0)

MCP server implementation for Figranium

- Trust score: 39/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- oci · `ghcr.io/figranium/figranium-mcp:0.1.0`: 39/100 (this document), [markdown](https://verifymcp.io/servers/figranium-figranium-mcp/ghcr-io-figranium-figranium-mcp-0-1-0.md), [page](https://verifymcp.io/servers/figranium-figranium-mcp/ghcr-io-figranium-figranium-mcp-0-1-0)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/figranium/figranium-mcp:0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-22.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 6/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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

### Claude

```bash
claude mcp add figranium-figranium-mcp -- docker run --rm -i ghcr.io/figranium/figranium-mcp:0.1.0
```

### Codex

```bash
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

```yaml
mcp_servers:
  figranium-figranium-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/figranium/figranium-mcp:0.1.0"]
```

### Other

```json
{
  "mcpServers": {
    "figranium-figranium-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/figranium/figranium-mcp:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-21 (score 39, +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.

### 2026-08-20 (score 38, +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.

### 2026-08-17 (score 37, +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.

### 2026-08-15 (score 36, +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.

### 2026-08-14 (score 35, +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.

### 2026-08-13 (score 34, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-11 (score 31, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 31, 0)

- [functional regression] Security disclosure: fail → unverified

## MCP tools (10)

### `create_task` (~1600 tokens)

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…

Input parameters:

- `actions` (array): Sequential list of browser actions/control flow steps to execute.
- `description` (string): Detailed description of what the task automates. Expected type: string. Example: 'Logs in and extracts weekly leads'
- `disableRecording` (boolean): Disable video/VNC recording of this task to save storage. Expected type: boolean. Example: true
- `extractionFormat` (string): Target export format of any extracted data. Expected type: string enum. Example: 'json'
- `extractionScript` (string): Optional post-execution script to extract data. Expected type: string. Example: 'return Array.from(document.querySelectorAll("a")).map(el => el.href)'
- `humanTyping` (boolean): Vary typing speeds and insert tiny delays to simulate organic human typing. Expected type: boolean. Example: true
- `includeHtml` (boolean): Whether to include the raw page HTML in the execution response. Expected type: boolean. Example: false
- `includeShadowDom` (boolean): Whether to parse and resolve target elements residing in Shadow DOMs. Expected type: boolean. Example: true
- `mode` (string, required): Execution 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'
- `name` (string, required): Descriptive name of the automation task. Expected type: string. Example: 'HackerNews Scraper'
- `rotateProxies` (boolean): Rotate through configured proxy IPs to prevent IP-based rate limiting. Expected type: boolean. Example: false
- `rotateUserAgents` (boolean): Rotate user agents across requests to avoid pattern blocking and fingerprinting. Expected type: boolean. Example: true
- `rotateViewport` (boolean): Vary viewport resolutions randomly to simulate multiple desktop and mobile devices. Expected type: boolean. Example: true
- `schedule` (object): Task automatic execution schedule. Expected type: object.
- `selector` (string): Default CSS selector to wait for on the page load before starting actions. Expected type: string. Example: '.main-content'
- `statelessExecution` (boolean): If set to true, clear browser cookies and session states between runs. Expected type: boolean. Example: false
- `stealth` (object): Configures realistic stealth, anti-bot, and human behavior simulation on the browser instance.
- `url` (string, required): Initial URL to navigate to when the task starts. Expected type: string. Example: 'https://news.ycombinator.com'
- `variables` (object): Task variables to store state and dynamic values. Expected type: record object of variable configurations.
- `wait` (number): Standard delay in seconds to wait after navigation and page loads to let dynamic scripts complete. Expected type: number. Example: 5

### `task_list` (~22 tokens)

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

### `task_execute` (~53 tokens)

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

Input parameters:

- `taskId` (string, required): The unique ID of the task to execute.
- `variables` (object): Key-value pairs representing the execution variables (optional).

### `execution_list` (~17 tokens)

List a summary of all past execution records.

### `schedule_list` (~20 tokens)

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

### `schedule_get_all_status` (~20 tokens)

Get overall scheduler status and metadata for all schedules.

### `schedule_get_status` (~43 tokens)

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

Input parameters:

- `taskId` (string, required): The unique ID of the task to check.

### `schedule_set` (~224 tokens)

Create or update a schedule for a specific task.

Input parameters:

- `cronExpression` (string): Standard 5-field cron expression. Used if scheduleMode is 'cron'.
- `dayOfMonth` (number): Day of the month (1-31) if frequency is 'monthly'.
- `daysOfWeek` (array): Array of days of the week if frequency is 'weekly'.
- `enabled` (boolean, required): Whether the schedule is active.
- `frequency` (string): The frequency mode. Used if scheduleMode is 'frequency'.
- `intervalMinutes` (number): Interval in minutes if frequency is 'interval'.
- `scheduleHour` (number): Hour of execution (0-23) if frequency is 'daily', 'weekly', or 'monthly'.
- `scheduleMinute` (number): Minute of execution (0-59) if frequency is 'daily', 'weekly', or 'monthly'.
- `scheduleMode` (string, required): Whether to define the schedule using 'cron' or structured 'frequency' fields.
- `taskId` (string, required): The unique ID of the task to configure.

### `schedule_delete` (~37 tokens)

Disable and remove the schedule configuration from a specific task.

Input parameters:

- `taskId` (string, required): The unique ID of the task whose schedule to delete.

### `schedule_describe` (~213 tokens)

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

Input parameters:

- `cronExpression` (string): Standard 5-field cron expression. Used if scheduleMode is 'cron'.
- `dayOfMonth` (number): Day of the month (1-31) if frequency is 'monthly'.
- `daysOfWeek` (array): Array of days of the week if frequency is 'weekly'.
- `frequency` (string): The frequency mode. Used if scheduleMode is 'frequency'.
- `intervalMinutes` (number): Interval in minutes if frequency is 'interval'.
- `scheduleHour` (number): Hour of execution (0-23) if frequency is 'daily', 'weekly', or 'monthly'.
- `scheduleMinute` (number): Minute of execution (0-59) if frequency is 'daily', 'weekly', or 'monthly'.
- `scheduleMode` (string, required): Whether to define the schedule using 'cron' or structured 'frequency' fields.
- `taskId` (string, required): The unique ID of the task.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/figranium-figranium-mcp/ghcr-io-figranium-figranium-mcp-0-1-0#diagnostics

## Score history

- 2026-08-22: 39
- 2026-08-21: 39
- 2026-08-20: 38
- 2026-08-19: 37
- 2026-08-18: 37
- 2026-08-17: 37
- 2026-08-16: 36
- 2026-08-15: 36
- 2026-08-14: 35
- 2026-08-13: 34
- 2026-08-12: 31
- 2026-08-11: 31
- 2026-08-10: 31
- 2026-08-09: 31
- 2026-08-08: 31
- 2026-08-07: 31
- 2026-08-06: 31
- 2026-08-05: 1

## Links

- Changelog RSS feed: https://verifymcp.io/servers/figranium-figranium-mcp/ghcr-io-figranium-figranium-mcp-0-1-0.xml
- Changelog JSON feed: https://verifymcp.io/servers/figranium-figranium-mcp/ghcr-io-figranium-figranium-mcp-0-1-0.json
- HTML version of this page: https://verifymcp.io/servers/figranium-figranium-mcp/ghcr-io-figranium-figranium-mcp-0-1-0