# NetNest Design Fundamentals API (remote · api.netnestdesign.com)

SEC company fundamentals and filing events, each with its source filing. Pay per call with x402.

- Trust score: 88/100 (high trust)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-07

## Components

- remote · `api.netnestdesign.com`: 88/100 (this document), [markdown](https://verifymcp.io/servers/com-netnestdesign-fundamentals/api.md), [page](https://verifymcp.io/servers/com-netnestdesign-fundamentals/api)

## Channel facts

- Endpoint: `https://api.netnestdesign.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## 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-11-07.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 792 tokens (~132/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 NetNest Design Fundamentals API MCP server?

NetNest Design Fundamentals API is a hosted endpoint at https://api.netnestdesign.com/mcp, 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 com-netnestdesign-fundamentals 'https://api.netnestdesign.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-netnestdesign-fundamentals": {
      "url": "https://api.netnestdesign.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-netnestdesign-fundamentals": {
      "type": "http",
      "url": "https://api.netnestdesign.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-netnestdesign-fundamentals]
url = "https://api.netnestdesign.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-netnestdesign-fundamentals": {
      "type": "remote",
      "url": "https://api.netnestdesign.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-netnestdesign-fundamentals --url 'https://api.netnestdesign.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-netnestdesign-fundamentals:
    url: "https://api.netnestdesign.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-netnestdesign-fundamentals": {
      "Transport": "http",
      "Url": "https://api.netnestdesign.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-netnestdesign-fundamentals -t streamable-http -u 'https://api.netnestdesign.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-netnestdesign-fundamentals": {
      "type": "http",
      "url": "https://api.netnestdesign.com/mcp"
    }
  }
}
```

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-11-06 (score 88, +7)

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

### 2026-11-05 (score 81, +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-11-03 (score 80, +1)

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

### 2026-11-01 (score 79, +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-10-30 (score 78, +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-10-28 (score 77, +1)

- [security] Tool “get_events” rewrote its description, which is the text the model reads

### 2026-10-26 (score 76, +1)

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

### 2026-10-24 (score 75, +1)

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

## MCP tools (6)

### `search_company` (~78 tokens)

Find a company

Free ticker and company name lookup: find the ticker for a company name, or the company for a ticker. Data from SEC filings. Not investment advice.

Input parameters:

- `limit` (number|string): Number of results, 1 to 25 (default 10)
- `q` (string, required): Company name or ticker, for example apple or AAPL

### `get_company` (~103 tokens)

Company profile and latest key metrics

Latest company financials from SEC filings for one ticker: revenue, net income, diluted EPS, operating income, total assets, cash, free cash flow and shares outstanding, for the latest fiscal year, latest quarter and trailing twelve months. Every number includes its period dates, the 10-K or 10-Q it came from, the filing date and a link to the SEC filing.

Input parameters:

- `ticker` (string, required): Stock ticker, for example AAPL or BRK.B

### `get_fundamentals` (~175 tokens)

Latest values of chosen metrics

Latest company revenue, net income, EPS, operating income, assets, liabilities, equity, cash, operating cash flow, capex, free cash flow or shares outstanding from SEC filings. Choose metrics and period (annual, quarterly or ttm). Latest values follow the fiscal year of each company, with the source filing, filing date and accession number for every number.

Input parameters:

- `metrics` (string): Comma separated: revenue, net_income, eps_basic, eps_diluted, operating_income, total_assets, total_liabilities, equity, cash, operating_cash_flow, capex, free_cash_flow, shares_outstanding, revenue_…
- `period` (string): annual, quarterly or ttm (trailing twelve months)
- `ticker` (string, required): Stock ticker, for example AAPL or BRK.B

### `get_history` (~184 tokens)

One metric over time

Financial history of one metric from SEC filings, newest first: revenue history, net income history, EPS history, cash flow history and more, by year, quarter or trailing twelve months. Up to 200 periods, each with its 10-K or 10-Q, filing date and SEC link.

Input parameters:

- `limit` (number|string): Number of periods, newest first, 1 to 200 (default 20)
- `metric` (string, required): The metric to return: revenue, net_income, eps_basic, eps_diluted, operating_income, total_assets, total_liabilities, equity, cash, operating_cash_flow, capex, free_cash_flow, shares_outstanding, rev…
- `period` (string): annual, quarterly or ttm (trailing twelve months)
- `ticker` (string, required): Stock ticker, for example AAPL or BRK.B

### `get_events` (~174 tokens)

SEC filing events across companies

SEC filing events across companies, newest first: 8-K items by plain name, Form 4 insider transactions and Schedule 13D and 13G stakes, each with its form, filing date, acceptance time, accession number, SEC link, CIK and ticker.

Input parameters:

- `before` (string): Cursor from an earlier answer (its continue field): the next page of older events
- `limit` (number|string): Number of events, 1 to 100 (default 100)
- `since` (string): Cursor from an earlier answer (its next field): only events newer than it are returned
- `tickers` (array): Tickers to include, for example AAPL or BRK.B
- `types` (array): Event types to include, for example 8k_results or form4_transaction

### `get_events_head` (~78 tokens)

Latest events cursor and how many are new

Free: the newest cursor of the SEC events feed and, given a cursor, how many events are newer than it, so a poller pays only when there is something new. Data from SEC filings. Not investment advice.

Input parameters:

- `since` (string): Cursor from an earlier answer (its next field): only events newer than it are returned

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-netnestdesign-fundamentals/api#diagnostics

## Score history

- 2026-11-07: 88
- 2026-11-06: 88
- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 67

## Common questions

### What is the NetNest Design Fundamentals API MCP server?

NetNest Design Fundamentals API is an MCP server listed in the public MCP registry as com.netnestdesign/fundamentals. SEC company fundamentals and filing events, each with its source filing. Pay per call with x402. This page covers its hosted endpoint (https://api.netnestdesign.com/mcp).

### Is the NetNest Design Fundamentals API MCP server safe to use?

NetNest Design Fundamentals API scores 88 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 NetNest Design Fundamentals API MCP server expose?

NetNest Design Fundamentals API exposes 6 tools: search_company, get_company, get_fundamentals, get_history, get_events, get_events_head. Their descriptions and schemas cost roughly 792 tokens of context every time the server is loaded.

### Does the NetNest Design Fundamentals API MCP server require authentication?

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

### Is the NetNest Design Fundamentals API MCP server still maintained?

NetNest Design Fundamentals API is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the NetNest Design Fundamentals API MCP server?

VerifyMCP ran 13 checks on NetNest Design Fundamentals API, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.netnestdesign.com/mcp
- Website: https://api.netnestdesign.com/docs
- Changelog RSS feed: https://verifymcp.io/servers/com-netnestdesign-fundamentals/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-netnestdesign-fundamentals/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-netnestdesign-fundamentals/api.json
- HTML version of this page: https://verifymcp.io/servers/com-netnestdesign-fundamentals/api