web3ctx
REMOTE · MCP.SCARAI.XYZ
Version-true web3 docs, ABIs and human-validated integration recipes over MCP.
Available components
Last scanned (3 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 515 tokens (~103/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 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
- 16 Sept 26 0
- Tool “web3_fetch” rewrote its description, which is the text the model reads security
- 1 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 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 5 Nov 2026 · Probed https://mcp.scarai.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=scarai.xyz | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | eb204fbed6a6cc6313848203190aff3b |
| SANs: scarai.xyz, mcp.scarai.xyz, *.mcp.scarai.xyz | ||||||
| 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 mcp.scarai.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| scarai.xyz. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.scarai.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.scarai.xyz/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 →
web3_deps Dependency closure ~44
Dependency closure around a selector. Does not follow calls across projects.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | – |
| kinds | array | – | – |
| selector | string | yes | – |
No output schema declared.
No examples provided.
web3_fetch Fetch complete units ~44
Full bodies for selectors you already chose, or the next page of a cursor. Does not discover selectors.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| selectors | array | – | – |
No output schema declared.
No examples provided.
web3_grep Exact identifier match ~52
Exact lexical match on a known identifier. Does not rank semantically.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| pattern | string | yes | – |
| project | string | – | – |
| version | string | – | – |
No output schema declared.
No examples provided.
web3_lookup Look up a typed record ~63
Typed records by id: address, ABI, EIP. Does not search prose or rank.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| id | string | yes | – |
| kind | string | yes | – |
| project | string | – | – |
| version | string | – | – |
No output schema declared.
No examples provided.
web3_search Search code and docs ~59
Ranked selectors for a prose query or unknown identifier. Does not return bodies.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | – | – |
| limit | integer | – | – |
| project | string | – | – |
| query | string | yes | – |
| version | string | – | – |
No output schema declared.
No examples provided.
How do I install the web3ctx MCP server?
web3ctx is a hosted endpoint at https://mcp.scarai.xyz/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 · mcp.scarai.xyz
claude mcp add --transport http farseensh-web3ctx 'https://mcp.scarai.xyz/mcp'
What is the web3ctx MCP server?
web3ctx is an MCP server listed in the public MCP registry as io.github.FarseenSh/web3ctx. Version-true web3 docs, ABIs and human-validated integration recipes over MCP. This page covers its hosted endpoint (https://mcp.scarai.xyz/mcp).
Is the web3ctx MCP server safe to use?
web3ctx scores 77 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 web3ctx MCP server expose?
web3ctx exposes 5 tools: web3_lookup, web3_grep, web3_search, web3_deps, web3_fetch. Their descriptions and schemas cost roughly 262 tokens of context every time the server is loaded.
Does the web3ctx MCP server require authentication?
No. We connected to web3ctx without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the web3ctx MCP server still maintained?
web3ctx is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.