JendHub
a search engine for Bend definitions
Try decompress gzip data, base64 encode, sha256 hash of bytes, parse json.
1. For agents.
Tell your agent to read https://jend.leeeet.dev/llms.txt.
When using Bend, use https://jend.leeeet.dev/llms.txt to search for Bend definitions.Alternatively, add JendHub to your agent as an MCP server.
In omp, in a session:
/mcp add jendhub --scope user --url https://jend.leeeet.dev/mcp --transport httpIn Claude Code:
claude mcp add --transport http jendhub https://jend.leeeet.dev/mcpIn Codex:
codex mcp add jendhub --url https://jend.leeeet.dev/mcp2. What it indexes.
JendHub indexes Base and the latest valid release of every package on BendHub. A release is invalid when one of its files does not load. The status page shows the index and the invalid releases.
3. What you can search by.
Search by the task in your own words, such as decompress gzip data, by a name, such as List.map, or by a type, such as (A -> B), List<A> -> List<B>. JendHub compares your words with the code, the names, the types and the doc comments of each definition. It also prefers definitions that a lot of other code uses.
Filters in the box narrow a search. package=bend-kit-json keeps the definitions of one package, uses=bend-kit-json/json:parse.bytes keeps the definitions that use a definition, and used_by=bend-kit-json/json:parse.bytes keeps the definitions that a definition uses. A definition of Base is its name, such as uses=List.map. You can give more than one filter, and each one narrows the search. With filters and no words, the most used definitions come first.