SweetValueLab
REMOTE · API.SWEETVALUELAB.COM
Free valuation models for S&P 500 and Nasdaq-100 stocks, Treasury yields and market sentiment.
Available components
Last scanned (8 hours ago)
Scores higher than 85% 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 Security77
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 876 tokens (~175/item across 5 items; 5 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 Management77
- Stability observed for 23 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 5 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 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool “get_stock_valuation” rewrote its description, which is the text the model reads security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +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.
- 25 Oct 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.
- 23 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 474 → 860 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “get_13f_consensus” functional
- New tool “get_investor_holdings” functional
- 22 Oct 26 +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.
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.sweetvaluelab.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sweetvaluelab.com | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 5a61339f0d0200921309ec1da0df5695 |
| SANs: sweetvaluelab.com, api.sweetvaluelab.com, *.api.sweetvaluelab.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.sweetvaluelab.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| sweetvaluelab.com. | DS published | 2371 | 13 | Verified |
| api.sweetvaluelab.com. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sweetvaluelab.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.sweetvaluelab.com/mcp | HTTPS enforced | 301 | https://api.sweetvaluelab.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_13f_consensus What the tracked managers hold in common ~91
Across the investment managers SweetValueLab tracks, from their latest quarter of Form 13F filings: the 10 stocks the most managers hold, the 10 the most managers bought or added to on balance, and the 10 the most reduced or sold on balance, each with the count of managers and the dollars moved. From public SEC filings, updated as managers file. Not investment advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_investor_holdings A manager's 13F holdings ~194
One investment manager SweetValueLab tracks (Berkshire Hathaway, Pershing Square, Bridgewater and about 80 more) from its latest Form 13F filing on SEC EDGAR: the quarter and filing date, the portfolio's size, its 10 largest positions, and its 10 largest moves that quarter in past tense — bought, added, reduced or sold — with the shares before and after. Also when the next 13F is due. A 13F is filed up to 45 days after the quarter ends, so it shows what the manager held then. From public SEC filings, updated as managers file. Not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| manager | string | yes | The manager, firm or person: "Berkshire Hathaway", "Warren Buffett", "buffett", "Pershing Square". When several match, the answer lists them; ask again with one's `manager` value. |
No output schema declared.
No examples provided.
get_market_context Rates and market sentiment ~93
The US Treasury yield curve (yields by tenor, curve shape, spreads, the 10-year real yield and breakeven, the last month's move), the risk-free rate and equity risk premium the valuation models discount with, and SweetValueLab's seven-factor market sentiment gauge. SweetValueLab model output, recomputed nightly from public filings and end-of-day prices. Not real-time quotes, not investment advice.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_stock_valuation Stock valuation vs models ~136
One covered stock's valuation: the current price, the headline model value and how far the price is from it ("overvalued by 5% vs model"), every other model's value with its range, the valuation profile that chose the headline model, the discount rate inputs, and its Quant and Valuation grades (a letter with the model and the date). SweetValueLab model output, recomputed nightly from public filings and end-of-day prices. Not real-time quotes, not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | The stock's ticker, e.g. "NVDA". Use search_stocks first when unsure. |
No output schema declared.
No examples provided.
search_stocks Search covered stocks ~111
Find a US stock SweetValueLab covers (the S&P 500 and Nasdaq-100 constituents) by ticker or company name. Returns up to 10 matches with the ticker to pass to get_stock_valuation and the stock's page. SweetValueLab model output, recomputed nightly from public filings and end-of-day prices. Not real-time quotes, not investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A ticker ("NVDA", "BRK.B") or part of a company name ("nvidia"). |
No output schema declared.
No examples provided.
How do I install the SweetValueLab MCP server?
SweetValueLab is a hosted endpoint at https://api.sweetvaluelab.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.sweetvaluelab.com
claude mcp add --transport http com-sweetvaluelab-valuation 'https://api.sweetvaluelab.com/mcp'
What is the SweetValueLab MCP server?
SweetValueLab is an MCP server listed in the public MCP registry as com.sweetvaluelab/valuation. Free valuation models for S&P 500 and Nasdaq-100 stocks, Treasury yields and market sentiment. This page covers its hosted endpoint (https://api.sweetvaluelab.com/mcp).
Is the SweetValueLab MCP server safe to use?
SweetValueLab scores 82 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 SweetValueLab MCP server expose?
SweetValueLab exposes 5 tools: search_stocks, get_stock_valuation, get_market_context, get_investor_holdings, get_13f_consensus. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.
Does the SweetValueLab MCP server require authentication?
No. We connected to SweetValueLab without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SweetValueLab MCP server still maintained?
SweetValueLab 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 SweetValueLab MCP server?
VerifyMCP ran 13 checks on SweetValueLab, 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.