# Figurewell (remote · figurewell-api.cybermaxtools.com)

Point-in-time SEC financials API + MCP: XBRL as first reported, EDGAR times. 100 free/day.

- Trust score: 69/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `figurewell-api.cybermaxtools.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-figurewell-api/figurewell-api-2.md), [page](https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-figurewell-api/figurewell-api-2)

## Channel facts

- Endpoint: `https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-18.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 719 tokens (~239/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 9 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 0 additions.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Figurewell MCP server?

Figurewell is a hosted endpoint at https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-workers-cybermax-tools-cybermax-figurewell-a 'https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-cybermax-tools-cybermax-figurewell-a": {
      "url": "https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-cybermax-tools-cybermax-figurewell-a": {
      "type": "http",
      "url": "https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-cybermax-tools-cybermax-figurewell-a]
url = "https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-cybermax-tools-cybermax-figurewell-a": {
      "type": "remote",
      "url": "https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-cybermax-tools-cybermax-figurewell-a --url 'https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-cybermax-tools-cybermax-figurewell-a:
    url: "https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-cybermax-tools-cybermax-figurewell-a": {
      "Transport": "http",
      "Url": "https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-cybermax-tools-cybermax-figurewell-a -t streamable-http -u 'https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-cybermax-tools-cybermax-figurewell-a": {
      "type": "http",
      "url": "https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-12 (score 69, −1)

- [security regression] Stability: 0.03 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [functional regression] “financials_as_of” made “ticker” required, so existing callers break
- [functional regression] “metric_history” made “ticker” required, so existing callers break
- [functional regression] “snapshot_as_of” made “tickers” required, so existing callers break
- [functional] Schema quality: excellent → good
- [cosmetic] “snapshot_as_of” reworded the description of “tickers”
- [cosmetic] “financials_as_of” reworded the description of “ticker”
- [cosmetic] “metric_history” reworded the description of “ticker”

### 2026-10-10 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-09 (score 70)

First indexed and scored.

## MCP tools (3)

### `financials_as_of` (~327 tokens)

Financials as known on a date

A company's 10-K/10-Q/20-F/40-F filings (newest accepted first, up to 40) with revenue, profit, EPS, cash, debt, cash flow and margins as each filing first reported them, EDGAR acceptance time and filing link. as_of = only filings accepted by then.

Input parameters:

- `amendments` (boolean): Include 10-K/A and 10-Q/A amendments (default false)
- `as_of` (string): Point in time: only filings EDGAR had accepted by then. YYYY-MM-DD (end of day, New York) or ISO time with offset. Empty = now
- `cik` (string): SEC CIK number, for companies without a listed ticker
- `fields` (string): Only these metrics (comma separated): revenue, cost_of_revenue, gross_profit, operating_income, net_income, eps_basic, eps_diluted, diluted_shares, total_assets, current_assets, total_liabilities, cu…
- `form` (string): all, annual (10-K, 20-F, 40-F) or quarterly (10-Q)
- `limit` (integer): Filings, newest accepted first (1-40)
- `offset` (integer): Skip filings (paging)
- `ticker` (string, required): Stock ticker (e.g. AAPL). Or pass "" and use cik

### `snapshot_as_of` (~98 tokens)

Point-in-time snapshot

For up to 10 tickers, the newest filing EDGAR had accepted by as_of, with key metrics as first reported.

Input parameters:

- `as_of` (string): Point in time (YYYY-MM-DD = end of that day, New York). Empty = now
- `form` (string): all, annual or quarterly
- `tickers` (string, required): Up to 10 tickers, comma separated (or pass "" and use cik)

### `metric_history` (~190 tokens)

Metric history and restatements

One metric per period, newest first: value as first reported (and when), latest value known at as_of, restated flag.

Input parameters:

- `as_of` (string): Only what was public by then (YYYY-MM-DD or ISO time)
- `limit` (integer): Periods, newest first (1-80)
- `metric` (string): One of: revenue, cost_of_revenue, gross_profit, operating_income, net_income, eps_basic, eps_diluted, diluted_shares, total_assets, current_assets, total_liabilities, current_liabilities, stockholder…
- `period` (string): quarter, annual, ytd or instant (default: the metric's own kind)
- `ticker` (string, required): Stock ticker (or pass "" and use cik)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-figurewell-api/figurewell-api-2#diagnostics

## Score history

- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 69
- 2026-10-14: 69
- 2026-10-13: 69
- 2026-10-12: 69
- 2026-10-10: 70
- 2026-10-09: 70

## Common questions

### What is the Figurewell MCP server?

Figurewell is an MCP server listed in the public MCP registry as dev.workers.cybermax-tools.cybermax/figurewell-api. Point-in-time SEC financials API + MCP: XBRL as first reported, EDGAR times. 100 free/day. This page covers its hosted endpoint (https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry).

### Is the Figurewell MCP server safe to use?

Figurewell scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Figurewell MCP server expose?

Figurewell exposes 3 tools: financials_as_of, snapshot_as_of, metric_history. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.

### Does the Figurewell MCP server require authentication?

No. We connected to Figurewell without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Figurewell MCP server still maintained?

Figurewell is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://figurewell-api.cybermaxtools.com/mcp?via=mcp-registry
- Repository: https://gitlab.com/CyberMax.tools/agent-tools
- Website: https://cybermaxtools.com/apis/sec-xbrl-api/?s=mcp-registry-figurewell-api
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-figurewell-api/figurewell-api-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-figurewell-api/figurewell-api-2.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-figurewell-api/figurewell-api-2