# 10 recent agent products with public-documentation entry barriers Checked on 5 September 2026 using anonymous HTTP GET requests, following normal redirects without running JavaScript. Launch window: 7 June–5 September 2026. Each finding concerns the exact entry path stated, not the availability of an entire product. Conventional-path checks are explicitly distinguished from broken published links. Error responses below are intentional test targets; supporting links lead to source material. ## 1. Libretto Browser Tools SDK - **Name + homepage:** [Libretto Browser Tools SDK](https://libretto.sh/browser-tools), an agent browser harness with an MCP adapter. Its [founder launch record](https://hacker-news.firebaseio.com/v0/item/48998262.json) is dated **21 July 2026**. [YC identifies the two-person team and its cofounders](https://www.ycombinator.com/companies/libretto). - **Verified blocker:** The [public agent index](https://libretto.sh/docs/llms.txt) links the [Markdown quickstart](https://libretto-docs.vercel.app/docs/browser-tools/quickstart.md). That guide contains `[MCP](/browser-tools/adapters/mcp)`. Following this published relative link produces `GET https://libretto-docs.vercel.app/browser-tools/adapters/mcp` → **404**, exact body: `Not Found`. A cold agent following this onboarding link misses the MCP adapter instructions, although the correctly addressed document exists. - **Public founder contact:** Tanishq Kancharla: `tanishqkancharla3@gmail.com`, published on [his own website](https://www.tanishqkancharla.dev/), which identifies his Libretto founder role. - **Suggested fix:** Correct the Markdown export's base path and suffix so the link targets the existing [MCP adapter Markdown](https://libretto-docs.vercel.app/docs/browser-tools/adapters/mcp.md), verified **200** with setup instructions. ## 2. Routebase - **Name + homepage:** [Routebase](https://routebase.dev/), an API-development tool with native MCP. The [official changelog](https://routebase.dev/changelog/) dates version 1.0.0 to **21 July 2026**. [Denny Riedl's public profile](https://hacker-news.firebaseio.com/v0/user/driedl.json) identifies him as founder; the [legal notice](https://routebase.dev/imprint/) identifies his company role. - **Verified blocker:** The [CLI overview](https://docs.routebase.dev/cli-overview/index.html) links its CI/CD guide to `https://docs.routebase.dev/cli-ci-cd/`. `GET https://docs.routebase.dev/cli-ci-cd/` → **404**, XML error `BlobNotFound`; exact response text: `The specified blob does not exist.` An agent following the overview's CI/CD link cannot read the promised pipeline instructions at that destination. This is a specific broken link; other documentation works. - **Public founder contact:** `hello@routebase.dev`, the company's published contact in its [legal notice](https://routebase.dev/imprint/). This is the business contact route, not a claim that only Denny reads it. - **Suggested fix:** Replace the stale overview link with the existing [CLI in CI/CD guide](https://docs.routebase.dev/cli-in-cicd/), verified **200** with actual pipeline instructions. ## 3. FetchSandbox MCP - **Name + homepage:** [FetchSandbox MCP](https://fetchsandbox.com/), a founder-led API integration-testing product. The [official launch record](https://www.producthunt.com/products/fetchsandbox/launches/fetchsandbox-mcp) dates its MCP launch to **23 August 2026**. [Raj Nagulapalle's first-person account](https://www.producthunt.com/products/aws/reviews?filter=founder&founderReview=19009&page=1) identifies him as the founder building FetchSandbox. - **Verified blocker:** The [installation guide](https://fetchsandbox.com/install) links a provider-specific Stripe validation prompt to `/docs/stripe`. `GET https://fetchsandbox.com/docs/stripe` → **200**, but `
` contains loading placeholders, not the promised guide or prompt. Exact response excerpt: `
`. Repeated requests gave the same empty documentation area. The installation overview itself is readable; the linked detailed provider example is the blocked step. - **Public founder contact:** [@fetchsandbox on X](https://x.com/fetchsandbox), the product contact explicitly offered for setup help by its [installation guide](https://fetchsandbox.com/install). This is Raj's product's support route, not an assertion of a private founder inbox. - **Suggested fix:** Pre-render the Stripe documentation and validation prompt into the initial `/docs/stripe` HTML. Keep JavaScript for interactive controls, not for access to the instructions. ## 4. Spread by ButterUp - **Name + homepage:** [Spread by ButterUp](https://spread.butterup.app/), a small grocery-data API with MCP. The [creator's launch record](https://hacker-news.firebaseio.com/v0/item/49317344.json) is dated **16 August 2026** and describes separating the existing comparison app's data layer into this API product. - **Verified blocker:** The readable [MCP overview](https://spread.butterup.app/mcp/) links **Setup documentation** to `/docs#mcp`. `GET https://spread.butterup.app/docs` → **200**, but the exact documentation container is `
`. The returned page is an application shell; setup/reference content is generated by JavaScript. A plain-HTTP reader reaches an empty documentation area. The overview's endpoint and authentication summary do work; the finding concerns the linked detailed guide. - **Public founder contact:** `hello@butterup.app`, published on the [MCP page](https://spread.butterup.app/mcp/). [ButterUp](https://butterup.app/) identifies its creator as Gagandeep (Gee); this is his product's public contact route. - **Suggested fix:** Pre-render `/docs`, including its MCP section, as readable HTML or Markdown while preserving the existing `/docs#mcp` link. ## 5. DocuQueue - **Name + homepage:** [DocuQueue](https://docuqueue.com/), a document-generation API whose [MCP launch record](https://hacker-news.firebaseio.com/v0/item/49066700.json) is dated **27 July 2026**. The [company's own guide](https://docuqueue.com/guides/best-pdf-generation-apis-2026) identifies Arun as its founder. - **Verified blocker:** The public [PDF API page](https://docuqueue.com/pdf-filling-api), reached through the homepage's API-docs link, advertises its full reference at `/api-docs`. `GET https://docuqueue.com/api-docs` → **404**, exact response title: `Page Not Found — DocuQueue`. A cold agent following the advertised full-reference link cannot obtain the complete request/response contract there. The product's overview examples remain readable. - **Public founder contact:** `arun@docuqueue.com`, explicitly published in [DocuQueue's terms](https://docuqueue.com/terms). - **Suggested fix:** Restore the complete public reference at `/api-docs`, or redirect that path and its published link to the current reference and schema. ## 6. TaskShell 2.0 - **Name + homepage:** [TaskShell 2.0](https://www.taskshell.app/), an agent-first task platform with MCP. Its [Product Hunt record](https://www.producthunt.com/products/taskshell) dates the 2.0 launch to **26 August 2026**; the [creator's next-day announcement](https://hacker-news.firebaseio.com/v0/item/49461578.json) confirms that he had just launched it. - **Verified blocker:** **Conventional-path discovery gap, not an advertised broken link.** `GET https://www.taskshell.app/docs` → **404**, exact HTML text: `This page doesn't exist or has been moved.` The homepage has no public setup-guide anchor, and its displayed configuration is literally truncated after `https://www.taskshell.app/api/mcp...`. A cold agent cannot recover a complete connection configuration from this tested homepage/docs route. This does not establish that account-only instructions are absent. - **Public founder contact:** `fred@taskshell.app`, published in the [official terms](https://www.taskshell.app/terms). The launch identifies the builder as Fred/Frederick. - **Suggested fix:** Publish and link a static `/docs` quickstart with the complete MCP URL, authentication steps and valid copyable client configuration; replace the truncated homepage example with that working example. ## 7. DevAlly MCP - **Name + homepage:** [DevAlly MCP](https://devally.com/), an accessibility workflow tool for AI editors. Its [official launch article](https://devally.com/blog/devally-mcp-live) is dated **14 July 2026**. The [official Darren Britton biography](https://devally.com/blog/meet-the-devallies-darren) identifies its CTO and cofounder and describes the early-stage team. - **Verified blocker:** **Conventional-path discovery gap, not an advertised broken link.** `GET https://devally.com/docs` → **404**, exact response text: `Page not found`. Neither the homepage nor the readable MCP launch article links a public developer manual. The launch article describes the feature and registration, but supplies no server URL or copyable connector configuration. Thus this obvious documentation entry path cannot provide setup instructions; account-only or unindexed documentation may still exist. - **Public founder contact:** [Darren Britton on GitHub](https://github.com/darrenbritton), linked directly from his [official founder biography](https://devally.com/blog/meet-the-devallies-darren). - **Suggested fix:** Publish a server-rendered MCP quickstart at `/docs`, with the server URL, supported authentication choices and copyable client configuration; link it from the launch article while keeping credentials private. ## 8. Ardent - **Name + homepage:** [Ardent](https://ardent.ai/), a code-first work agent with native MCP support. Its [founder's public-beta launch](https://hacker-news.firebaseio.com/v0/item/49550931.json) is dated **3 September 2026**. The [company page](https://ardent.ai/company) identifies a small team and founder Nate Kohari. - **Verified blocker:** **Conventional-path discovery gap, not an advertised broken link.** `GET https://ardent.ai/docs` → **404**, exact response title: `Page not found — Ardent AI`. The homepage and company navigation offer product information and a Mac download, but no public documentation link. An agent starting with the obvious docs path cannot retrieve the MCP/setup reference there. This is not a claim that the downloadable application or its integrations are broken. - **Public founder contact:** [Nate Kohari on GitHub](https://github.com/nkohari), linked by name from the [company page](https://ardent.ai/company). - **Suggested fix:** Serve a public static `/docs` entry page with MCP connection/setup guidance and link it from the main navigation, so discovery does not require first downloading the application. ## 9. Compilr Studio - **Name + homepage:** [Compilr Studio](https://studio.compilr.dev/welcome/), an MCP-connected project knowledge graph. The [creator's launch](https://hacker-news.firebaseio.com/v0/item/49528310.json) is dated **1 September 2026**; his [same-day follow-up](https://hacker-news.firebaseio.com/v0/item/49528343.json) confirms that the Studio app had just launched with controlled registrations. - **Verified blocker:** **Intentional invitation wall, not a software defect.** `GET https://studio.compilr.dev/welcome/` → **200**, with the exact public instruction: `Accounts are invite-only while we work with the first teams.` The page advertises MCP connectivity but provides neither a public setup reference nor a server URL; its onboarding route is an access-request form. A cold agent cannot proceed from the public introduction to connection instructions without registration approval. - **Public founder contact:** Creator Carmelo Scozzola: `scozzola@gmail.com`, publicly listed for maintainer `scozzola` in [Compilr's package metadata](https://registry.npmjs.org/@compilr-dev%2Flogger), matching the launch author's handle. - **Suggested fix:** Keep beta accounts invite-only, but publish a read-only setup guide showing prerequisites, the connector configuration and how access approval fits into onboarding. This lets agents evaluate the integration without requesting an account. ## 10. G3M - **Name + homepage:** [G3M](https://g3m.co/), an MCP service for physical outbound gifts. Its [creator's launch record](https://hacker-news.firebaseio.com/v0/item/49539359.json) is dated **2 September 2026** and identifies its MCP purpose; the [launch discussion record](https://hn.algolia.com/api/v1/items/49539359) includes the creator's explanation of the project. - **Verified blocker:** `GET https://g3m.co/` → **200**, but the entire body is `
`, with no static setup text or documentation anchor. The MCP setup panel is in the JavaScript bundle rather than the initial page. A plain-HTTP reader of this published entry point cannot read the connection instructions. [Public integration metadata](https://api.g3m.co/api/v1/public/integrations/mcp) does exist and responds **200**; the defect is missing static discovery, not a nonexistent MCP endpoint. - **Public founder contact:** Creator [Davis Martens on GitHub](https://github.com/davismartens). Attribution is cross-source: the same HN account that launched G3M previously [posted its matching GitHub project](https://hacker-news.firebaseio.com/v0/item/46057838.json). This is his public creator profile, not a G3M-site contact link. - **Suggested fix:** Pre-render the existing MCP setup panel and link the public integration metadata from the initial HTML, so agents can discover the server and connection steps without running the application bundle.