io.github.iamdlm/saras-list
REMOTE · THESARASLIST.COM
Read-only tools over Sara's List: growth-stage companies, open roles and equity forecasts.
Available components
Last scanned (21 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Oct 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- Authorization: partial → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 30 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Sept 26 0
First indexed and scored.
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 21 Nov 2026 · Probed https://thesaraslist.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thesaraslist.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1405f31573dd19bf13a6265a61d87fd3 |
| SANs: thesaraslist.com, *.thesaraslist.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 insecure
Validation of thesaraslist.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| thesaraslist.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://thesaraslist.com/mcp | Auth required | 401 | |
| http (plaintext) | http://thesaraslist.com/mcp | HTTPS enforced | 301 | https://thesaraslist.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 Read one company ~93
Read one company by slug, with its description, its industries, its headquarters and its valuation history. Credit the data to Sara's List (https://thesaraslist.com); a new role stays Pro-only for its first 24 hours, so a free key and a call with no key read it only after that window.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug of the company, as search_companies states it. |
No output schema declared.
No examples provided.
get_job Read one role ~94
Read one role by slug, with its description, its benefits, its apply URL and its Millionaire Forecast. Credit the data to Sara's List (https://thesaraslist.com); a new role stays Pro-only for its first 24 hours, so a free key and a call with no key read it only after that window.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug of the role, as search_jobs states it. |
No output schema declared.
No examples provided.
millionaire_forecast Forecast the equity of one role ~176
Run the Millionaire Forecast over one role. It answers the grant value, the exit multiple and the year the equity reaches one million USD, or names the one input the model does not hold. Credit the data to Sara's List (https://thesaraslist.com); a new role stays Pro-only for its first 24 hours, so a free key and a call with no key read it only after that window.
| Name | Type | Req | Description |
|---|---|---|---|
| experience | string|null | – | Your experience level: Entry, Mid, Senior, Lead or Executive. It replaces the level of the posting. |
| jobSlug | string | yes | The slug of the role, as search_jobs states it. |
| salaryUsd | integer|null | – | Your own base salary in USD, from 10000 to 2000000. It replaces the salary anchor of the posting. |
No output schema declared.
No examples provided.
search_companies Search companies ~236
Search the growth-stage companies that Sara's List tracks, highest valuation first. Credit the data to Sara's List (https://thesaraslist.com); a new role stays Pro-only for its first 24 hours, so a free key and a call with no key read it only after that window.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string|null | – | An ISO 3166-1 alpha-2 country code of the headquarters, for example "US". |
| cursor | string|null | – | The nextCursor of the previous answer. Leave it out for the first page. |
| industry | string|null | – | An industry slug, for example "fintech". |
| limit | integer|null | – | The page size, from 1 to 50. The default is 20. |
| maxValuationUsd | number|null | – | The highest valuation the company may hold, in USD. |
| minValuationUsd | number|null | – | The lowest valuation the company must hold, in USD. |
| query | string|null | – | Free text over the company name. |
| stage | string|null | – | The newest funding stage, for example "SeriesB". |
No output schema declared.
No examples provided.
search_jobs Search open roles ~283
Search the open roles of Sara's List at growth-stage companies. Returns a page of roles and a nextCursor to read the following page. Credit the data to Sara's List (https://thesaraslist.com); a new role stays Pro-only for its first 24 hours, so a free key and a call with no key read it only after that window.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string|null | – | The slug of one employer, for example "acme". |
| cursor | string|null | – | The nextCursor of the previous answer. Leave it out for the first page. |
| equityOnly | boolean | – | True reads only roles that state stock options. |
| experience | string|null | – | The experience level, for example "Senior". |
| limit | integer|null | – | The page size, from 1 to 50. The default is 20. |
| location | string|null | – | The name of a city or a country, for example "Berlin". |
| minSalaryUsd | integer|null | – | The lowest salary the role must state, in USD. |
| query | string|null | – | Free text over the role title. Leave it out to read every role. |
| role | string|null | – | The role slug of the board, for example "backend-engineer". |
| workplace | string|null | – | Where the role sits: Remote, Hybrid or OnSite. |
No output schema declared.
No examples provided.
sweet_spot_index Read the Sweet Spot Index ~116
Read a page of the Sweet Spot Index: the tracked companies, highest valuation first, plus the newest entries and exits and the totals behind them. Credit the data to Sara's List (https://thesaraslist.com); a new role stays Pro-only for its first 24 hours, so a free key and a call with no key read it only after that window.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer|null | – | How many companies and how many feed events to return, from 1 to 200. The default is 50. |
No output schema declared.
No examples provided.
whoami Read the plan of the key ~78
Read the plan this key reads with, and the allowance of that plan. A call with no key reads "free". Credit the data to Sara's List (https://thesaraslist.com); a new role stays Pro-only for its first 24 hours, so a free key and a call with no key read it only after that window.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.iamdlm/saras-list MCP server?
io.github.iamdlm/saras-list is a hosted endpoint at https://thesaraslist.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 · thesaraslist.com
claude mcp add --transport http iamdlm-saras-list 'https://thesaraslist.com/mcp'
What is the io.github.iamdlm/saras-list MCP server?
io.github.iamdlm/saras-list is an MCP server listed in the public MCP registry as io.github.iamdlm/saras-list. Read-only tools over Sara's List: growth-stage companies, open roles and equity forecasts. This page covers its hosted endpoint (https://thesaraslist.com/mcp).
Is the io.github.iamdlm/saras-list MCP server safe to use?
io.github.iamdlm/saras-list scores 36 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 io.github.iamdlm/saras-list MCP server expose?
io.github.iamdlm/saras-list exposes 7 tools: get_company, sweet_spot_index, get_job, whoami, search_companies, and 2 more. Their descriptions and schemas cost roughly 1,076 tokens of context every time the server is loaded.
Does the io.github.iamdlm/saras-list MCP server require authentication?
Yes. io.github.iamdlm/saras-list asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.iamdlm/saras-list MCP server still maintained?
io.github.iamdlm/saras-list is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.iamdlm/saras-list MCP server?
VerifyMCP ran 5 checks on io.github.iamdlm/saras-list, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about io.github.iamdlm/saras-list: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.