mcp server
ctx
Turn a GitHub repo or docs site into agent-ready context: pack it or search it, over MCP.
Description as published by the maintainer. Source
- version 1.0.0
- active
- retrieval
active — Registry entry last updated 2026-08-06. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_file(ref, path, repo)- Return the full text of a single file in a repository, by path. Use after list_files or search_context to drill in. Required: repo, path.
list_files(ref, repo, exclude, include)- List the text files ctx would include for a repository (after stripping binaries, lockfiles and build dirs), with their byte sizes. Cheap way for an agent to see the layout before packing. Required: repo.
pack_docs(url, depth, max_pages, max_tokens)- Crawl a documentation site from a start URL and return it as one agent-ready context blob: each page extracted to clean Markdown, concatenated with its URL. Stays within the same site section; bounded by depth and page count. Use max_tokens to fit a budget. Required: url.
pack_repo(ref, repo, exclude, include, max_tokens)- Fetch a GitHub repository and return it as one agent-ready context blob: text files concatenated with clear "==== path ====" headers, binaries/lockfiles/build dirs stripped, with a token estimate. Use include/exclude globs to focus, and max_tokens to fit a budget. Required: repo.
search_context(ref, repo, query, exclude, include, max_matches, context_chars)- Search a GitHub repository and return only the passages that match a query — each with its file path, line number and a relevance score. Far more token-efficient than pack_repo when you need a specific detail (e.g. "where is auth handled?"). Required: repo, query.
search_docs(url, depth, query, max_pages, max_matches, context_chars)- Crawl a documentation site and return only the passages that match a query — each with its page URL, line and a relevance score. Token-efficient way to answer a question from docs without packing the whole site. Required: url, query.
Last successful function declaration observed on . Source: https://ctx.vanshul.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://ctx.vanshul.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-06 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-06 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | ctx.vanshul.com | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | ctx.vanshul.com |
Where to get it
Also from vanshulgoyal101
-
io.github.vanshulgoyal101/mcp
Read any web page as clean Markdown for AI agents: fetch, search, metadata, links. SSRF-safe.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json