# Toplyne: MCP server status, API access gate and what it does > unknown in current form - per the seed list and general market classification, Toplyne provided... No MCP found, Gate not applicable. Checked 2026-08-24. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* --- [Directory](../index.md) / [Inbound & PLG Chat](../categories/inbound-plg-chat.md) / Toplyne # Toplyne [No MCP found](../mcp/none-found.md) [Gate not applicable](../gates/n-a.md) [Inbound & PLG Chat](../categories/inbound-plg-chat.md) RESEARCHED Checked 2026-08-24 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0. Vendor: [toplyne.io (returns HTTP 404 as of this research)](https://toplyne.io (returns HTTP 404 as of this research)) · entry id 14-toplyne · source 14-inbound-plg-chat.md line 160 **What it does** unknown in current form - per the seed list and general market classification, Toplyne provided product-qualified-lead (PQL) scoring for PLG companies; this description could not be re-verified against a live company source in this research pass (see notes). **AI features, separated from automation with an AI label on it** unknown - no current product surface exists to evaluate. **RevOps role** n/a today - historically occupied the same PQL-scoring niche as Correlated. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a - **Parsed URLs**: 0 found in the mcp_url field No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: none **Access gate** - **Gate bucket**: Gate not applicable - **Can a solo operator reach it**: Not established api_gate, verbatim from the file: n/a **API documentation** No documentation URL recorded. 263 of 293 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **Jobs it can do** No job tag on this entry. Reason recorded by the tagging pass: dead. Entry records the current form as unknown. 22 of 293 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag. **Sources** - [https://toplyne.io](https://toplyne.io) - [http://archive.org/wayback/available?url=toplyne.io×tamp=20250101](http://archive.org/wayback/available?url=toplyne.io×tamp=20250101) - [http://archive.org/wayback/available?url=toplyne.io×tamp=20260801](http://archive.org/wayback/available?url=toplyne.io×tamp=20260801) 3 source URLs. Raw sources field, verbatim: https://toplyne.io, http://archive.org/wayback/available?url=toplyne.io×tamp=20250101, http://archive.org/wayback/available?url=toplyne.io×tamp=20260801 **Notes, verbatim from the file** STATUS FLAG - LIKELY DEAD, not fully confirmed. toplyne.io returns a direct HTTP 404 (not a DNS failure or parked-domain page) as of 2026-08-24. The Wayback Machine confirms a live, HTTP-200 snapshot as recently as November 24, 2024, but no snapshot close to August 2026 exists, and no acquisition announcement, press release, or successor URL could be located in this pass. A generic web search for "Toplyne" also collides with an unrelated Brazilian mining company of the same name on LinkedIn - do not conflate the two. Recommend a direct re-check (correct-entity LinkedIn page, Crunchbase) before the next directory pass. **Provenance** - **Entry id**: 14-toplyne - **Source file**: 14-inbound-plg-chat.md - **Source line**: 160 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).