Skip to content

io.github.vanshulgoyal101/ctx

by vanshulgoyal101 · remote · no sign-in to list tools · v1.0.0 · published by GitHub user vanshulgoyal101

Turn a GitHub repo or docs site into agent-ready context: pack it or search it, over MCP.

Changes · 1
CompareRegistry entry

6 tools: 1 change things and 5 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http ctx https://ctx.vanshul.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 1Claude Code: ask
  • pack_docsCrawl 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.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
Only reads 5Claude Code: allow, ask for 1 outbound
  • get_fileReturn the full text of a single file in a repository, by path.Reads private dataNo findings

    Why it is in this group

    • The name "get_file" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_file" says "get" and "file": it reads files.
    • private-dataThe description's first sentence says "return" and "file": it reads files.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    Return the full text of a single file in a repository, by path. Use after list_files or search_context to drill in.
  • list_filesList the text files ctx would include for a repository (after stripping binaries, lockfiles and build dirs), with their byte sizes.Reads private dataNo findings

    Why it is in this group

    • The name "list_files" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_files" says "list" and "file": it reads files.
    • private-dataThe description's first sentence says "list" and "file": it reads files.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    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.
  • pack_repoFetch 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…Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.

    What it can reach

    • private-dataThe name "pack_repo" says "repo": it reads repositories.
    • private-dataThe description's first sentence says "fetch" and "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    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.
  • search_contextSearch a GitHub repository and return only the passages that match a query — each with its file path, line number and a relevance score.Reads private dataNo findings

    Why it is in this group

    • The name "search_context" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "repository": it reads repositories.
    • private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
    Description, as the server wrote it
    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?").
  • search_docsCrawl a documentation site and return only the passages that match a query — each with its page URL, line and a relevance score.Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The name "search_docs" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_docs" says "search" and "doc": it reads documents.
    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

20 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__ctx__pack_docs",
      "mcp__ctx__search_docs"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http ctx https://ctx.vanshul.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ctx__pack_repo",
      "mcp__ctx__search_context",
      "mcp__ctx__list_files",
      "mcp__ctx__get_file"
    ],
    "ask": [
      "mcp__ctx__pack_docs",
      "mcp__ctx__search_docs"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ctx. Review it before you use it.

Capability tags behind 6 rules
  • mcp__ctx__pack_repo private-data
  • mcp__ctx__search_context private-data
  • mcp__ctx__list_files private-data
  • mcp__ctx__get_file private-data
  • mcp__ctx__pack_docs untrusted-input, outbound
  • mcp__ctx__search_docs private-data, untrusted-input, outbound