NetNest Design Fundamentals API
REMOTE · API.NETNESTDESIGN.COM
SEC company fundamentals and filing events, each with its source filing. Pay per call with x402.
Available components
Last scanned (11 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- 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. 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 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.
- 3 Nov 26 +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.
- 1 Nov 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.
- 30 Oct 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.
- 28 Oct 26 +1
- Tool “get_events” rewrote its description, which is the text the model reads security
- 26 Oct 26 +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.
- 24 Oct 26 +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.
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 6 Nov 2026 · Probed https://api.netnestdesign.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.netnestdesign.com | CN=YR1,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | 6a63f175d340f585057b4fecc3a48644211 |
| SANs: api.netnestdesign.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.netnestdesign.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| netnestdesign.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.netnestdesign.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.netnestdesign.com/mcp | HTTPS enforced | 308 | https://api.netnestdesign.com/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_company Company profile and latest key metrics ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Stock ticker, for example AAPL or BRK.B |
No output schema declared.
No examples provided.
get_events SEC filing events across companies ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_events_head Latest events cursor and how many are new ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | – | Cursor from an earlier answer (its next field): only events newer than it are returned |
No output schema declared.
No examples provided.
get_fundamentals Latest values of chosen metrics ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Stock ticker, for example AAPL or BRK.B |
No output schema declared.
No examples provided.
get_history One metric over time ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number|string | – | Number of periods, newest first, 1 to 200 (default 20) |
| metric | string | yes | 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 | yes | Stock ticker, for example AAPL or BRK.B |
No output schema declared.
No examples provided.
search_company Find a company ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number|string | – | Number of results, 1 to 25 (default 10) |
| q | string | yes | Company name or ticker, for example apple or AAPL |
No output schema declared.
No examples provided.
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.
remote · api.netnestdesign.com
claude mcp add --transport http com-netnestdesign-fundamentals 'https://api.netnestdesign.com/mcp'
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 6 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.