Developer Tools

scarai.xyz

Provides web3 lookup, search, dependency, and fetch tools for Ethereum selectors and ABIs.

1 endpoint5 known toolsFirst detected September 1, 2026Last detected September 1, 2026

ENDPOINT 1

https://mcp.scarai.xyz/mcp

No auth detected

MCP server metadata

Name: web3-context
Version: 0.1.0

Capabilities

tools.listChangedprompts.listChangedresources.listChanged

Server instructions

Version-true Web3 context: code, docs, EIPs, ABIs and deployment addresses, scoped to an exact project version. Escalation ladder — start at the cheapest primitive that can answer: lookup → grep → search → deps → fetch - lookup: a typed record (address, ABI, EIP). Mis-routing away from lookup is the worst failure on this surface. - grep: an exact identifier you already know. - search: prose, or an identifier you do not know. Returns selectors, not bodies. - deps: once you hold a selector and the surrounding surface matters. - fetch: last. The only step that spends tokens on bodies. Max 5 selectors. Version contract: pass `version` when you know it. Every response labels `version_defaulted` when you did not, and carries `project@version`, `last_validated` and `as_of` on every unit. Two versions of one interface are never returned without labelling both. Scoping: if your client sends a lockfile or package manifest, the server scopes to the projects it names — the most reliable path. Otherwise scoping falls back to identifiers in the query, which abstains rather than guess when the evidence is thin.

Known tools 5

web3_lookup

Typed records by id: address, ABI, EIP.

Inferred read-only

web3_grep

Exact lexical match on a known identifier.

Inferred read-only

web3_search

Ranked selectors for a prose query or unknown identifier.

Inferred read-only

web3_deps

Dependency closure around a selector.

Inferred read-only

web3_fetch

Full bodies for selectors you already chose.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.web3-context]
url = "https://mcp.scarai.xyz/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "web3-context": {
      "type": "http",
      "url": "https://mcp.scarai.xyz/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: web3-context
Remote MCP URL: https://mcp.scarai.xyz/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "web3-context": {
      "url": "https://mcp.scarai.xyz/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "web3-context": {
      "type": "http",
      "url": "https://mcp.scarai.xyz/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "web3-context",
  "transport": "streamable-http",
  "url": "https://mcp.scarai.xyz/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.