# io.github.vanshulgoyal101/ctx (remote · ctx.vanshul.com)

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

- Trust score: 63/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `ctx.vanshul.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/vanshulgoyal101-ctx/ctx.md), [page](https://verifymcp.io/servers/vanshulgoyal101-ctx/ctx)

## Channel facts

- Endpoint: `https://ctx.vanshul.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 900 tokens (~150/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.vanshulgoyal101-ctx]
url = "https://ctx.vanshul.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vanshulgoyal101-ctx": {
      "type": "remote",
      "url": "https://ctx.vanshul.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vanshulgoyal101-ctx --url https://ctx.vanshul.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vanshulgoyal101-ctx:
    url: "https://ctx.vanshul.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "vanshulgoyal101-ctx": {
      "type": "http",
      "url": "https://ctx.vanshul.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-20 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-18 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-16 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-12 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-11 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-09 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-07 (score 57, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `pack_repo` (~158 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.

Input parameters:

- `exclude` (array): Optional glob patterns (support **, *, ?).
- `include` (array): Optional glob patterns (support **, *, ?).
- `max_tokens` (number): Stop adding files once the estimate exceeds this many tokens.
- `ref` (string): Optional branch, tag or commit SHA (defaults to the default branch).
- `repo` (string, required): A GitHub repo as "owner/repo" or a github.com URL.

### `search_context` (~193 tokens)

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?").

Input parameters:

- `context_chars` (number): Per-passage character budget (80–4000, default 500).
- `exclude` (array): Optional glob patterns (support **, *, ?).
- `include` (array): Optional glob patterns (support **, *, ?).
- `max_matches` (number): Max passages to return (1–50, default 5).
- `query` (string, required): Space-separated search terms; matching is case-insensitive.
- `ref` (string): Optional branch, tag or commit SHA (defaults to the default branch).
- `repo` (string, required): A GitHub repo as "owner/repo" or a github.com URL.

### `list_files` (~120 tokens)

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.

Input parameters:

- `exclude` (array): Optional glob patterns (support **, *, ?).
- `include` (array): Optional glob patterns (support **, *, ?).
- `ref` (string): Optional branch, tag or commit SHA (defaults to the default branch).
- `repo` (string, required): A GitHub repo as "owner/repo" or a github.com URL.

### `get_file` (~88 tokens)

Return the full text of a single file in a repository, by path. Use after list_files or search_context to drill in.

Input parameters:

- `path` (string, required): File path within the repo.
- `ref` (string): Optional branch, tag or commit SHA (defaults to the default branch).
- `repo` (string, required): A GitHub repo as "owner/repo" or a github.com URL.

### `pack_docs` (~145 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.

Input parameters:

- `depth` (number): How many link hops to follow (0–3, default 1).
- `max_pages` (number): Max pages to fetch (1–30, default 10).
- `max_tokens` (number): Stop adding pages once the estimate exceeds this many tokens.
- `url` (string, required): The absolute http(s) URL to start crawling from (e.g. a docs index).

### `search_docs` (~166 tokens)

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.

Input parameters:

- `context_chars` (number): Per-passage character budget (80–4000, default 500).
- `depth` (number): How many link hops to follow (0–3, default 1).
- `max_matches` (number): Max passages to return (1–50, default 5).
- `max_pages` (number): Max pages to fetch (1–30, default 10).
- `query` (string, required): Space-separated search terms; matching is case-insensitive.
- `url` (string, required): The absolute http(s) URL to start crawling from.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vanshulgoyal101-ctx/ctx#diagnostics

## Score history

- 2026-08-20: 63
- 2026-08-19: 62
- 2026-08-18: 62
- 2026-08-17: 61
- 2026-08-16: 61
- 2026-08-15: 60
- 2026-08-14: 60
- 2026-08-13: 59
- 2026-08-12: 59
- 2026-08-11: 58
- 2026-08-10: 58
- 2026-08-09: 58
- 2026-08-08: 57
- 2026-08-07: 57
- 2026-08-06: 56

## Links

- Remote endpoint: https://ctx.vanshul.com/mcp
- Repository: https://github.com/vanshulgoyal101/ctx
- Website: https://ctx.vanshul.com/
- Changelog RSS feed: https://verifymcp.io/servers/vanshulgoyal101-ctx/ctx.xml
- Changelog JSON feed: https://verifymcp.io/servers/vanshulgoyal101-ctx/ctx.json
- HTML version of this page: https://verifymcp.io/servers/vanshulgoyal101-ctx/ctx
