
Ask262
io.github.bendtherulesPublished by GitHub account bendtherulesv0.0.13Updated Oct 24, 2026
MCP server for understanding Javascript internals from ECMAScript specification.
Overview
Ask262 lets an assistant search the ECMAScript specification, read spec sections, and run JavaScript in engine262 to see which spec parts execute.
- What you can do
- Search the ECMAScript specification by semantic query and retrieve the full content of matching sections. Execute JavaScript in engine262 and capture the spec sections that run, with marking of important code parts. Use a knowledge graph that maps spec sections to implementation functions. Code execution is capped by a one-second timeout.
- When to use it
- Useful when you need to understand JavaScript language internals, trace behavior back to ECMAScript spec text, or check how a snippet behaves in a spec-faithful engine.
- Requirements
- A remote endpoint is available with no local setup; the README also documents a local install needing Bun 1.0.0 or higher and Ollama with the qwen3-embedding:8b model, or a Fireworks cloud embedding option configured through FIREWORKS_API_KEY.
Installation
In SourceWeft
- Open Ask262 in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.bendtherules%2Fask262/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"ask262": {
"type": "http",
"url": "https://ask262.mcp.bendtherules.io/mcp"
}
}
}README
Ask262
MCP server for exploring the ECMAScript specification and its implementation in engine262.
🎮 Try it now
The fastest way to tinker with JavaScript internals:
- Ask262 Chat — Ask questions in natural language (register new account)
- MCP Inspector — Direct access to all mcp tools, no signup needed
npx add-mcp "https://ask262.bendtherules.in/mcp"
Features
- Vector search ECMAScript specification sections using semantic queries
- Execute JavaScript in engine262 and capture spec sections, with
ask262Debug.startImportant()to mark the key parts of your code - Knowledge graph mapping spec sections to implementation functions
- 1-second timeout on code execution for safety
Available Tools
Quick Start (Hosted Instance)
Use the hosted MCP server without any local setup:
Preferred Method: npx add-mcp
Install ask262 MCP server to your client with one command:
Manual Configuration
If you prefer to configure manually:
Claude Desktop (claude_desktop_config.json):
OpenCode (~/.config/opencode/opencode.json):
Local Installation
Prerequisites
- Bun: Version 1.0.0 or higher (install)
- Ollama: Installed with
qwen3-embedding:8b
(ollama pull qwen3-embedding:8b)
Setup
Environment Configuration
Copy .env.example and configure:
Key variables:
ASK262_EMBEDDING_PROVIDER: Chooseollama(local) orfireworks(cloud). Default:ollamaOLLAMA_HOST: Ollama server URL. Default:http://localhost:11434FIREWORKS_API_KEY: Required if using Fireworks. Get from https://app.fireworks.aiASK262_PORT: HTTP server port. Default:8081
Example .env:
Local MCP Configuration
Claude Desktop (claude_desktop_config.json):
stdio (no server needed)
http (requires server)
⬇️ Required for HTTP config above:
OpenCode (~/.config/opencode/opencode.json):
stdio (no server needed)
http (requires server)
⬇️ Required for HTTP config above:
HTTP Server Endpoints:
Note: /mcp is defined before the inspector's catch-all / route to ensure proper request handling.
Testing
Development
For development or using a custom ECMAScript specification:
-
Clone and setup:
-
Ensure spec is present:
./spec-built/multipage/- Built ECMAScript spec HTML files
Steps -
git clone https://github.com/tc39/ecma262npm i && npm run build- copy
out/from ecma262 tospec-built/in this repo
-
Build vectors (lancedb)
-
Release to npm (maintainers only):
This will:
- Check for uncommitted git changes
- Bump patch version (e.g., 0.0.1 → 0.0.2)
- Fix any hard links in
storage/ - Run checks and release
Other options:
bun run release -- --minor,bun run release -- --major, orbun run release -- --no-bump
License
ISC
Source: Readme.md at commit 1715462
Tools
0Version history
1- v0.0.13LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.