A second path to the source.

An MCP server built for moments when an agent can find a page but cannot properly read it. Origo will focus on direct link retrieval and site mapping, not search.

Infrastructure preview. The server transport and authentication are scaffolded; retrieval features are still being designed.

Optimized for reading. Not another search engine.

Origo is intended to preserve the strengths of WebCTX's Markdown and GitHub retrieval while giving agents more ways to access pages when a standard browser fetch falls short.

Read the original

Prefer a site's native Markdown, source APIs, and high-quality extraction. Planned for read_link.

Explore a site

Discover relevant URLs without reimplementing web search. Planned for map_site.

Fallback only

Designed to complement native agent browsing and search, not replace either.

Small surface

A stateless Go MCP endpoint on Vercel with API-key authentication. Infrastructure scaffold is ready.

From transport to retrieval.

Start with the infrastructure and follow the design decisions before enabling the two tools.

Origo is a private, early-stage project. The public docs describe the architecture, not a finished retrieval product.