_ registry / mcp streamable-http · checked 7h ago

vanshul-ctx

https://ctx.vanshul.com

Registry code: 4e6646c1107cf5a9

api record

Tools to turn a GitHub repo into agent-ready context. Pass a repo as "owner/repo" or a github.com URL.

endpoint
https://ctx.vanshul.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is vanshul-ctx live?
Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
Is vanshul-ctx free to use?
Yes — the hub reached it with no key and no payment.
What tools does vanshul-ctx have?
6 tools: pack_repo, search_context, list_files, pack_docs, get_file, search_docs.
Is vanshul-ctx safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.1%

90 days 98.8%· all time 98.8%

latency
167ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 340 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
developer tools code & repositories
used for
  • pack a github repo into llm context
  • search a repo for matching passages
  • read a file from a repo
  • pack a documentation site into context
takes → gives
text, web pages → code, text
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • pack_repo reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "repo"
  ],
  "properties": {
    "ref": {
      "type": "string",
      "description": "Optional branch, tag or commit SHA (defaults to the default branch)."
    },
    "repo": {
      "type": "string",
      "description": "A GitHub repo as \"owner/repo\" or a github.com URL."
    },
    "exclude": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "max_tokens": {
      "type": "number",
      "description": "Stop adding files once the estimate exceeds this many tokens."
    }
  }
}
    arguments 34 lines
  • search_context reads unknown 27h ago

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "repo",
    "query"
  ],
  "properties": {
    "ref": {
      "type": "string",
      "description": "Optional branch, tag or commit SHA (defaults to the default branch)."
    },
    "repo": {
      "type": "string",
      "description": "A GitHub repo as \"owner/repo\" or a github.com URL."
    },
    "query": {
      "type": "string",
      "description": "Space-separated search terms; matching is case-insensitive."
    },
    "exclude": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "max_matches": {
      "type": "number",
      "description": "Max passages to return (1–50, default 5)."
    },
    "context_chars": {
      "type": "number",
      "description": "Per-passage character budget (80–4000, default 500)."
    }
  }
}
    arguments 43 lines
  • list_files reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "repo"
  ],
  "properties": {
    "ref": {
      "type": "string",
      "description": "Optional branch, tag or commit SHA (defaults to the default branch)."
    },
    "repo": {
      "type": "string",
      "description": "A GitHub repo as \"owner/repo\" or a github.com URL."
    },
    "exclude": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    },
    "include": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional glob patterns (support **, *, ?)."
    }
  }
}
    arguments 30 lines
  • pack_docs reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The absolute http(s) URL to start crawling from (e.g. a docs index)."
    },
    "depth": {
      "type": "number",
      "description": "How many link hops to follow (0–3, default 1)."
    },
    "max_pages": {
      "type": "number",
      "description": "Max pages to fetch (1–30, default 10)."
    },
    "max_tokens": {
      "type": "number",
      "description": "Stop adding pages once the estimate exceeds this many tokens."
    }
  }
}
    arguments 24 lines
  • get_file reads unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "repo",
    "path"
  ],
  "properties": {
    "ref": {
      "type": "string",
      "description": "Optional branch, tag or commit SHA (defaults to the default branch)."
    },
    "path": {
      "type": "string",
      "description": "File path within the repo."
    },
    "repo": {
      "type": "string",
      "description": "A GitHub repo as \"owner/repo\" or a github.com URL."
    }
  }
}
    arguments 21 lines
  • search_docs reads unknown 27h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url",
    "query"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The absolute http(s) URL to start crawling from."
    },
    "depth": {
      "type": "number",
      "description": "How many link hops to follow (0–3, default 1)."
    },
    "query": {
      "type": "string",
      "description": "Space-separated search terms; matching is case-insensitive."
    },
    "max_pages": {
      "type": "number",
      "description": "Max pages to fetch (1–30, default 10)."
    },
    "max_matches": {
      "type": "number",
      "description": "Max passages to return (1–50, default 5)."
    },
    "context_chars": {
      "type": "number",
      "description": "Per-passage character budget (80–4000, default 500)."
    }
  }
}
    arguments 33 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4e6646c1107cf5a9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4e6646c1107cf5a9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4e6646c1107cf5a9/badge.svg)](https://brick.blue/agent/4e6646c1107cf5a9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on vanshul.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.