io.github.vanshulgoyal101/ctx
REMOTE · CTX.VANSHUL.COM · SCANNED OCT 4
Turn a GitHub repo or docs site into agent-ready context: pack it or search it, over MCP.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.vanshulgoyal101/ctx MCP server?
io.github.vanshulgoyal101/ctx is a hosted endpoint at https://ctx.vanshul.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ctx.vanshul.com
claude mcp add --transport http vanshulgoyal101-ctx 'https://ctx.vanshul.com/mcp'
{
"mcpServers": {
"vanshulgoyal101-ctx": {
"url": "https://ctx.vanshul.com/mcp"
}
}
} {
"servers": {
"vanshulgoyal101-ctx": {
"type": "http",
"url": "https://ctx.vanshul.com/mcp"
}
}
} [mcp_servers.vanshulgoyal101-ctx] url = "https://ctx.vanshul.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vanshulgoyal101-ctx": {
"type": "remote",
"url": "https://ctx.vanshul.com/mcp",
"enabled": true
}
}
} openclaw mcp add vanshulgoyal101-ctx --url 'https://ctx.vanshul.com/mcp' --transport streamable-http
mcp_servers:
vanshulgoyal101-ctx:
url: "https://ctx.vanshul.com/mcp" {
"McpServers": {
"vanshulgoyal101-ctx": {
"Transport": "http",
"Url": "https://ctx.vanshul.com/mcp"
}
}
} assistant mcp add vanshulgoyal101-ctx -t streamable-http -u 'https://ctx.vanshul.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Sept 26 72
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 6 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 8 Oct 2026 · Probed https://ctx.vanshul.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vanshul.com | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 662fdbcf22a8bc840e21b0f05320d01f |
| SANs: vanshul.com, ctx.vanshul.com, *.ctx.vanshul.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ctx.vanshul.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| vanshul.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ctx.vanshul.com/mcp | Verified | 200 | |
| http (plaintext) | http://ctx.vanshul.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_file ~88
Return the full text of a single file in a repository, by path. Use after list_files or search_context to drill in.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | File path within the repo. |
| ref | string | – | Optional branch, tag or commit SHA (defaults to the default branch). |
| repo | string | yes | A GitHub repo as "owner/repo" or a github.com URL. |
No output schema declared.
No examples provided.
list_files ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A GitHub repo as "owner/repo" or a github.com URL. |
No output schema declared.
No examples provided.
pack_docs ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The absolute http(s) URL to start crawling from (e.g. a docs index). |
No output schema declared.
No examples provided.
pack_repo ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A GitHub repo as "owner/repo" or a github.com URL. |
No output schema declared.
No examples provided.
search_context ~193
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?").
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Space-separated search terms; matching is case-insensitive. |
| ref | string | – | Optional branch, tag or commit SHA (defaults to the default branch). |
| repo | string | yes | A GitHub repo as "owner/repo" or a github.com URL. |
No output schema declared.
No examples provided.
search_docs ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Space-separated search terms; matching is case-insensitive. |
| url | string | yes | The absolute http(s) URL to start crawling from. |
No output schema declared.
No examples provided.
What is the io.github.vanshulgoyal101/ctx MCP server?
io.github.vanshulgoyal101/ctx is an MCP server listed in the public MCP registry as io.github.vanshulgoyal101/ctx. Turn a GitHub repo or docs site into agent-ready context: pack it or search it, over MCP. This page covers its hosted endpoint (https://ctx.vanshul.com/mcp).
Is the io.github.vanshulgoyal101/ctx MCP server safe to use?
io.github.vanshulgoyal101/ctx scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.vanshulgoyal101/ctx MCP server expose?
io.github.vanshulgoyal101/ctx exposes 6 tools: pack_repo, search_context, list_files, get_file, pack_docs, search_docs. Their descriptions and schemas cost roughly 870 tokens of context every time the server is loaded.
Does the io.github.vanshulgoyal101/ctx MCP server require authentication?
No. We connected to io.github.vanshulgoyal101/ctx without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.vanshulgoyal101/ctx MCP server still maintained?
io.github.vanshulgoyal101/ctx is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.