Is apexcharts-mcp live?

Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.

Is apexcharts-mcp free to use?

Yes — the hub reached it with no key and no payment.

What tools does apexcharts-mcp have?

23 tools: apextree_generate_config, apexstock_generate_config, apexmaps_generate_config, apexcharts_generate_config, apexcharts_validate_config, apexgantt_generate_config, apexgantt_validate_config, apexgantt_get_reference, ….

Is apexcharts-mcp safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp streamable-http · checked 57m ago

apexcharts-mcp

https://mcp.apexcharts.com

Registry code: 0f908302bc44bd98

api record

Generates and validates configs for ApexCharts charts, grid, gantt, tree, sankey, stock and maps.

from a public catalogue that lists it, not from the operator

endpoint: https://mcp.apexcharts.com/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is apexcharts-mcp live?: Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is apexcharts-mcp free to use?: Yes — the hub reached it with no key and no payment.
What tools does apexcharts-mcp have?: 23 tools: apextree_generate_config, apexstock_generate_config, apexmaps_generate_config, apexcharts_generate_config, apexcharts_validate_config, apexgantt_generate_config, apexgantt_validate_config, apexgantt_get_reference, ….
Is apexcharts-mcp safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

306ms

last good check

priced tools

of 23 tools

_ answered our checks, 90 days 1 checks · signed record

2026-10-07 07:04 unknown → live

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 23 tools

3 open 20 never probed 3 of 23 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

apexcharts_get_reference open 57m ago
Read authoritative ApexCharts documentation from the bundled apexcharts-skill knowledge base. Call with no arguments to list all available files (SKILL.md plus per-family reference docs). Call with `file` to return that file as markdown. Use this when you need to look up an option, formatter signature, plotOptions detail, or a fully worked example for a specific chart family.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "file": { "type": "string", "description": "Filename to read (e.g. \"SKILL.md\", \"circular-charts.md\"). Omit to list available files." } }, "additionalProperties": false }
arguments 11 lines
apexcharts_list_products open 57m ago
Return every product (charts, gantt, tree, sankey, grid, stock, maps) currently exposed by this MCP server, with a "when to pick this" hint and the tool names it registers. Use this once at the start of a session to decide which product matches the user's task; then call that product's tools directly. Each product also reports `compatibility`: the bundled skill version and the upstream library version its guidance was verified against — use it to tell the user which library version this server targets. Results respect the APEXCHARTS_MCP_PRODUCTS env-var gating.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

apexcharts_list_types open 57m ago

Return every ApexCharts chart type this server supports, with name, description, family (cartesian/bar/financial/circular/grid/radar/unit), series format (axis vs non-axis), expected data shape, and the reference doc filename for deeper detail. Optionally filter by family.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "family": {
      "enum": [
        "cartesian",
        "bar",
        "financial",
        "circular",
        "grid",
        "radar",
        "unit"
      ],
      "type": "string",
      "description": "Optional family filter. Omit to return all supported types."
    }
  },
  "additionalProperties": false
}

arguments 20 lines

apextree_generate_config unknown never probed

Build a minimal valid ApexTree config split into `options` (constructor) and `data` (the root NestedNode passed to `tree.render(data)`). Generates a small 3-level org chart placeholder when `data` is omitted. Every node in the output has `children: []` even for leaves (ApexTree requires it).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "data": {
      "type": "object",
      "description": "Root NestedNode: `{ id, name, children: [...] }`. Recursive. Leaves must have `children: []`.",
      "additionalProperties": {}
    },
    "theme": {
      "type": "string",
      "description": "Built-in \"light\"/\"dark\"/\"custom\", or (apextree 2.1+) the name of a theme registered on the shared family registry."
    },
    "width": {
      "type": [
        "number",
        "string"
      ],
      "description": "Canvas width. Default \"100%\"."
    },
    "height": {
      "type": [
        "number",
        "string"
      ],
      "description": "Canvas height. Default \"auto\"."
    },
    "direction": {
      "enum": [
        "top",
        "bottom",
        "left",
        "right",
        "radial"
      ],
      "type": "string",
      "description": "Where the root sits and which way the tree grows. Default \"top\". \"radial\" (apextree 2.0+) puts the root at the centre with one ring per depth."
    },
    "edgeStyle": {
      "enum": [
        "orthogonal",
        "curved",
        "straight"
      ],
      "type": "string"
    },
    "nodeWidth": {
      "type": "number"
    },
    "contentKey": {
      "type": "string",
      "description": "Key on each node used as the label. Default \"name\". Set to \"data\" to activate the built-in org-card template."
    },
    "nodeHeight": {
      "type": "number"
    },
    "enableToolbar": {
      "type": "boolean"
    },
    "siblingSpacing": {
      "type": "number",
      "description": "Horizontal spacing between siblings (px)."
    },
    "childrenSpacing": {
      "type": "number",
      "description": "Vertical spacing between a node and its children (px)."
    },
    "enableSelection": {
      "enum": [
        "single",
        "multi",
        false
      ],
      "type": [
        "string",
        "boolean"
      ],
      "description": "Selection mode. Note: enableSelection: true is INVALID — use \"single\" or \"multi\"."
    }
  },
  "additionalProperties": false
}

arguments 82 lines

apexstock_generate_config unknown never probed

Build a minimal valid ApexStock options object for a financial / stock chart. Generates a placeholder OHLCV candle series when `data` is omitted, so the result renders as-is. Note: at runtime ApexStock also requires `window.ApexCharts` to be set (it does not import ApexCharts) — that is a host-page concern, not part of this options object.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "data": {
      "type": "array",
      "items": {},
      "description": "OHLC candles for series[0].data. Each point: { x, y: [open, high, low, close], v? }. Omit for a placeholder series."
    },
    "name": {
      "type": "string",
      "description": "Series name (default \"Price\")."
    },
    "theme": {
      "enum": [
        "light",
        "dark"
      ],
      "type": "string",
      "description": "Theme mode (default \"light\")."
    },
    "title": {
      "type": "string",
      "description": "Optional chart title."
    },
    "height": {
      "type": "integer",
      "description": "Chart height in px (default 600).",
      "exclusiveMinimum": 0
    },
    "indicators": {
      "anyOf": [
        {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        {
          "type": "object",
          "additionalProperties": {}
        }
      ],
      "description": "Indicators to enable: a list of keys (e.g. [\"moving average\", \"rsi\"]) or a keyed config map (e.g. { \"bollinger bands\": { period: 20, stdDev: 2 } }). Overlays and oscillators both stack; each oscillator gets its own pane."
    }
  },
  "additionalProperties": false
}

arguments 48 lines

apexmaps_generate_config unknown never probed

Build a minimal valid ApexMaps options object for a geographic visualization. Supports the six series types: choropleth (default), bubble, marker, arc, line, hexbin. Geometry comes from the built-in registry (e.g. "world/countries", "us", "eu/nuts2"), so no GeoJSON is needed. Generates a small placeholder dataset when data is omitted. Use the result with `new ApexMaps(el, options)` then `await map.render()`.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "map": {
      "type": "string",
      "description": "Geometry registry pack id or alias: \"world/countries\", \"us\", \"us/counties\", \"eu/nuts2\", \"jp/prefectures\", ... Default \"world/countries\"."
    },
    "data": {
      "type": "array",
      "items": {},
      "description": "Data array in the datum shape of `type`: choropleth rows `{ <key>, value }`, bubble/marker `{ lon, lat, ... }`, arc `{ from, to }`, line `{ path: [[lon,lat],...] }`, hexbin `{ lon, lat, value? }`. Omit for a placeholder dataset."
    },
    "type": {
      "enum": [
        "choropleth",
        "bubble",
        "marker",
        "arc",
        "line",
        "hexbin"
      ],
      "type": "string",
      "description": "Series type. Default \"choropleth\". \"hexbin\" bins points into a hex lattice (density); it takes points, never region-keyed rows."
    },
    "joinBy": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "array",
          "items": [
            {
              "type": "string"
            },
            {
              "type": "string"
            }
          ],
          "maxItems": 2,
          "minItems": 2
        },
        {
          "type": "object",
          "additionalProperties": {
            "type": "string"
          }
        }
      ],
      "description": "Join spec: \"field\", [\"geoField\", \"dataField\"], or { geo, data }. Omit to use key auto-detection (the placeholder emits [\"iso_a3\", \"code\"])."
    },
    "palette": {
      "type": "string",
      "description": "Palette name for the value scale (e.g. \"blues\", \"viridis\", \"okabeIto\")."
    },
    "themeMode": {
      "enum": [
        "light",
        "dark",
        "auto"
      ],
      "type": "string",
      "description": "Theme mode."
    },
    "projection": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "object",
          "additionalProperties": {}
        }
      ],
      "description": "Projection name or spec object. Omit to use the pack default (recommended: packs like \"us\" already pick albersUsa)."
    },
    "seriesName": {
      "type": "string",
      "description": "Series display name (legend / tooltip)."
    }
  },
  "additionalProperties": false
}

arguments 84 lines

apexcharts_generate_config unknown never probed

Build a minimal valid ApexCharts options object for a given chart type. Picks the correct series data format (axis vs non-axis) and supplies placeholder data when none is given. Use this as the starting point for a chart.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "type"
  ],
  "properties": {
    "type": {
      "enum": [
        "line",
        "area",
        "bar",
        "scatter",
        "bubble",
        "rangeArea",
        "rangeBar",
        "funnel",
        "pyramid",
        "waterfall",
        "dumbbell",
        "streamgraph",
        "raincloud",
        "histogram",
        "candlestick",
        "boxPlot",
        "violin",
        "heatmap",
        "treemap",
        "icicle",
        "radar",
        "pie",
        "donut",
        "polarArea",
        "radialBar",
        "gauge",
        "sunburst",
        "unit",
        "waffle"
      ],
      "type": "string",
      "description": "ApexCharts chart.type value (e.g. \"line\", \"bar\", \"pie\")."
    },
    "title": {
      "type": "string",
      "description": "Optional chart title."
    },
    "height": {
      "type": "integer",
      "description": "Chart height in px (default 350).",
      "exclusiveMinimum": 0
    },
    "series": {
      "type": "array",
      "items": {},
      "description": "Optional series data in the format required by the chart type."
    },
    "stacked": {
      "type": "boolean",
      "description": "Stack series. Honored only for bar and area chart types."
    },
    "categories": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "xaxis categories (axis charts) or labels (pie/donut/etc)."
    },
    "horizontal": {
      "type": "boolean",
      "description": "Render bars horizontally. Honored only for bar chart type."
    }
  },
  "additionalProperties": false
}

arguments 74 lines

apexcharts_validate_config unknown never probed
Check an ApexCharts options object against the data-format rules and known pitfalls (wrong series shape for chart type, radialBar values out of 0–100 range, undefined data points, conflicting tooltip flags, hex colors missing #, etc.). Returns structured issues so the caller can fix them. Returns ok: true when there are no errors (warnings still allowed).

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "config" ], "properties": { "config": { "type": "object", "description": "The ApexCharts options object to validate.", "additionalProperties": {} } }, "additionalProperties": false }
arguments 15 lines

apexgantt_generate_config unknown never probed

Build a minimal valid ApexGantt options object. Generates a placeholder schedule (phases, dependencies, a milestone) when `tasks` is omitted, so the result can be rendered as-is. The placeholder dates are emitted in whatever `inputDateFormat` is chosen, so they parse without further work.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "tasks": {
      "type": "array",
      "items": {},
      "description": "Task array (`series`). Each task: { id, name, startTime, endTime?, progress?, type?, parentId?, dependency? }."
    },
    "title": {
      "type": "string",
      "description": "Optional chart title."
    },
    "height": {
      "type": "integer",
      "description": "Chart height in px (default 600).",
      "exclusiveMinimum": 0
    },
    "baseline": {
      "anyOf": [
        {
          "type": "boolean"
        },
        {
          "type": "object",
          "properties": {
            "color": {
              "type": "string"
            }
          },
          "additionalProperties": true
        }
      ],
      "description": "Enable planned-vs-actual baseline track. Tasks must supply a per-task `baseline: { start, end }`."
    },
    "enableSelection": {
      "type": "boolean",
      "description": "Enable `getSelectedTasks()` / `setSelectedTasks()` / `selectionChange` event."
    },
    "inputDateFormat": {
      "type": "string",
      "description": "dayjs format for parsing date strings. Default is ApexGantt's own default \"MM-DD-YYYY\". Common alternatives: \"YYYY-MM-DD\", \"DD/MM/YYYY\"."
    },
    "enableCriticalPath": {
      "type": "boolean",
      "description": "Highlight the longest dependency chain on render."
    }
  },
  "additionalProperties": false
}

arguments 50 lines

apexgantt_validate_config unknown never probed
Check an ApexGantt options object against the rules in apexgantt-skill (missing id/name/startTime, duplicate ids, orphan parentId, milestone with endTime, progress out of 0–100, ISO dates with default MM-DD-YYYY format, dependency object using `id` instead of `taskId`, unknown dependency target, self-dependency, invalid dependency type, cycles, baseline missing start/end). Returns structured issues with stable rule ids.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "config" ], "properties": { "config": { "type": "object", "description": "The ApexGantt options object to validate.", "additionalProperties": {} } }, "additionalProperties": false }
arguments 15 lines
apexgantt_get_reference unknown never probed
Read authoritative ApexGantt documentation from the bundled apexgantt-skill knowledge base. Call with no arguments to list all available files. Call with `file` to return that file as markdown. Use this to look up task data format, dependency types, view modes, the update lifecycle, or framework integration.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "file": { "type": "string", "description": "Filename to read (e.g. \"SKILL.md\", \"data-format.md\"). Omit to list available files." } }, "additionalProperties": false }
arguments 11 lines
apextree_validate_config unknown never probed
Check an ApexTree config against apextree-skill rules: root is a NestedNode, every node has id/name/children (children must be `[]` for leaves), ids unique across the whole tree, valid direction/edgeStyle/edgeColorMode/theme values, enableSelection is "single"|"multi"|false (NOT boolean true), and a warning when contentKey is "data" but a node has no `data` payload. Accepts both the wrapped `{ options, data }` shape and a bare root node.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "config" ], "properties": { "config": { "type": "object", "description": "The ApexTree config to validate.", "additionalProperties": {} } }, "additionalProperties": false }
arguments 15 lines
apextree_get_reference unknown never probed
Read authoritative ApexTree documentation from the bundled apextree-skill knowledge base. Call with no arguments to list available files; call with `file` to fetch markdown. Use this for the NestedNode data shape, grow directions, nodeTemplate, the graph API, or framework integration.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "file": { "type": "string", "description": "Filename to read (e.g. \"SKILL.md\", \"data-format.md\"). Omit to list available files." } }, "additionalProperties": false }
arguments 11 lines

apexsankey_generate_config unknown never probed

Build a minimal valid ApexSankey config split into `options` (constructor) and `data` (render payload). Generates a 5-node placeholder flow when nodes/edges are omitted so the result renders something visible. Use the result by calling `new ApexSankey(el, options)` then `sankey.render(data)`.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "edges": {
      "type": "array",
      "items": {},
      "description": "Array of edge objects: `{ source, target, value, type }`. source/target reference node ids; value > 0."
    },
    "nodes": {
      "type": "array",
      "items": {},
      "description": "Array of node objects: `{ id, title, color? }`. ids must be unique."
    },
    "width": {
      "type": [
        "number",
        "string"
      ],
      "description": "Canvas width (px number or any CSS width). Default \"100%\"."
    },
    "height": {
      "type": [
        "number",
        "string"
      ],
      "description": "Canvas height (px number or \"auto\"). Default \"auto\" ≈ 1.6:1 from width."
    },
    "spacing": {
      "type": "number",
      "description": "Horizontal gap between node columns (px). Default 20."
    },
    "animation": {
      "type": "boolean",
      "description": "Enable entrance animation. Default true."
    },
    "nodeWidth": {
      "type": "number",
      "description": "Node rectangle width (px). Default 20."
    },
    "tooltipTheme": {
      "enum": [
        "light",
        "dark"
      ],
      "type": "string",
      "description": "Tooltip preset."
    }
  },
  "additionalProperties": false
}

arguments 51 lines

apexsankey_validate_config unknown never probed
Check an ApexSankey config against apexsankey-skill rules (unique node ids, edges reference real nodes, edge.value > 0, no self-loops, cycles flagged as warnings since apexsankey 1.11 renders them as dashed back-edges, edge.type provided for grouping). Accepts either the wrapped `{ options, data }` shape from generate_config or the raw render payload `{ nodes, edges }`.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "config" ], "properties": { "config": { "type": "object", "description": "The ApexSankey config object to validate.", "additionalProperties": {} } }, "additionalProperties": false }
arguments 15 lines
apexsankey_get_reference unknown never probed
Read authoritative ApexSankey documentation from the bundled apexsankey-skill knowledge base. Call with no arguments to list available files; call with `file` to fetch markdown. Use this for the { nodes, edges, options } data shape, layer ordering, styling, or framework integration.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "file": { "type": "string", "description": "Filename to read (e.g. \"SKILL.md\", \"data-format.md\"). Omit to list available files." } }, "additionalProperties": false }
arguments 11 lines

apexgrid_generate_config unknown never probed

Build a minimal valid `<apex-grid>` config: `{ columns, data }`. When both are omitted, a small users table is generated. When only `columns` is omitted, they are inferred from the keys of the first data row with `type` inferred per column. Pass `enableSortAndFilter: true` to opt every generated column in.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "data": {
      "type": "array",
      "items": {},
      "description": "Array of row objects. Keys referenced by `column.key` must exist on each row."
    },
    "columns": {
      "type": "array",
      "items": {},
      "description": "Array of ColumnConfiguration. Each column needs `{ key, type? }` where key is a real key of each data row."
    },
    "resizable": {
      "type": "boolean",
      "description": "Convenience: add `resizable: true` to every generated column."
    },
    "enableSortAndFilter": {
      "type": "boolean",
      "description": "Convenience: add `sort: true` and `filter: true` to every generated column."
    }
  },
  "additionalProperties": false
}

arguments 25 lines

apexgrid_validate_config unknown never probed
Check an apex-grid `{ columns, data }` config against apexgrid-skill rules: columns/data required and array-shaped, every column.key must be a real key of the data rows, column.key unique, type is one of apex-grid's column types (string, number, boolean, date, currency, select and the other presentation types), sort/filter is boolean or config object. Returns structured issues with stable rule ids.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "config" ], "properties": { "config": { "type": "object", "description": "The apex-grid config `{ columns, data }` to validate.", "additionalProperties": {} } }, "additionalProperties": false }
arguments 15 lines
apexgrid_get_reference unknown never probed
Read authoritative apex-grid documentation from the bundled apexgrid-skill knowledge base. Call with no arguments to list available files; call with `file` to fetch markdown. Use this for ColumnConfiguration, Lit cellTemplate, sort/filter, data pipeline, or framework integration.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "file": { "type": "string", "description": "Filename to read (e.g. \"SKILL.md\", \"columns-and-templates.md\"). Omit to list available files." } }, "additionalProperties": false }
arguments 11 lines
apexstock_validate_config unknown never probed
Check an ApexStock options object against the rules in apexstock-skill (missing series/data, flat o/h/l/c keys instead of a y:[o,h,l,c] array, malformed or inconsistent OHLC tuples, missing/invalid x, non-ascending data, invalid theme.mode, and unknown indicator keys). Returns structured issues with stable rule ids.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "config" ], "properties": { "config": { "type": "object", "description": "The ApexStock options object to validate.", "additionalProperties": {} } }, "additionalProperties": false }
arguments 15 lines
apexstock_get_reference unknown never probed
Read authoritative ApexStock documentation from the bundled apexstock-skill knowledge base. Call with no arguments to list all available files. Call with `file` to return that file as markdown. Use this to look up the OHLC data format, indicators, streaming/appendData, trading overlays, theming, or framework integration.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "file": { "type": "string", "description": "Filename to read (e.g. \"SKILL.md\", \"indicators.md\"). Omit to list available files." } }, "additionalProperties": false }
arguments 11 lines
apexmaps_validate_config unknown never probed
Check an ApexMaps options object against apexmaps-skill rules: geo.map present, known series types, arc from/to endpoints, line paths, bubble/marker coordinates or joinBy, hexbin point positions and aggregates (a hexbin has no joinBy), [lon, lat] ordering, joinBy shape, null (not undefined) for missing values, and known scale / projection / palette names. Returns structured issues with stable rule ids, severity, path, and a fix when there is a one-shot remedy.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "config" ], "properties": { "config": { "type": "object", "description": "The ApexMaps options object to validate.", "additionalProperties": {} } }, "additionalProperties": false }
arguments 15 lines
apexmaps_get_reference unknown never probed
Read authoritative ApexMaps documentation from the bundled apexmaps-skill knowledge base. Call with no arguments to list available files; call with `file` to fetch markdown. Use this for series datum shapes, joins, the geometry registry, projections, scales, drilldown, theming, or framework integration.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "file": { "type": "string", "description": "Filename to read (e.g. \"SKILL.md\", \"data-format.md\"). Omit to list available files." } }, "additionalProperties": false }
arguments 11 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0f908302bc44bd98.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0f908302bc44bd98/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/0f908302bc44bd98/badge.svg)](https://brick.blue/agent/0f908302bc44bd98?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.