Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AsOf Demo

REMOTE · DEMO.ASOF.XYZ

No-sign-up demo: recorded historical crypto wallet holdings, prices and CSV exports. Fixed examples.

Available components

68 Trust /100

Last scanned (13 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security74
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 307 tokens (~51/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 65

    First indexed and scored.

Diagnostics

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 18 Oct 2026 · Probed https://demo.asof.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=demo.asof.xyz CN=WR3,O=Google Trust Services,C=US 11 Oct 2026 9 Jan 2027 RSA 2048 SHA256-RSA ddcb67f149792d3c10062d04d644757b
SANs: demo.asof.xyz
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of demo.asof.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
asof.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://demo.asof.xyz/mcp Verified 200
http (plaintext) http://demo.asof.xyz/mcp HTTPS enforced 302 https://demo.asof.xyz/mcp
MCP tools · 6 exposed · ~250 tokens

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 →

Tool Tokens
export_holdings_csv ~43

Export all positions from a fixed sample as safe CSV, including price/verification evidence.

NameTypeReqDescription
as_of_datestringyes–
walletstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_demo_guide ~24

Explain fixed-snapshot scope and how to connect the separate paid service.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

get_historical_price ~51

Read a recorded sample price by symbol or exact contract; no market lookup.

NameTypeReqDescription
as_of_datestringyes–
assetstringyes–
chain–––
wallet–––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_holdings ~56

Read one listed wallet's precomputed report, paginated; never scan or refresh.

NameTypeReqDescription
as_of_datestringyes–
limitinteger––
offsetinteger––
walletstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_demo_wallets ~22

List the fixed public wallets, snapshot dates and recorded coverage.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

retrieve_holdings ~54

Retrieve recorded sample positions with provenance; same fixed data as get_holdings.

NameTypeReqDescription
as_of_datestringyes–
limitinteger––
offsetinteger––
walletstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the AsOf Demo MCP server?

AsOf Demo is a hosted endpoint at https://demo.asof.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 · demo.asof.xyz

# add to Claude Code
claude mcp add --transport http xyz-asof-asof-demo 'https://demo.asof.xyz/mcp'
Common questions

What is the AsOf Demo MCP server?

AsOf Demo is an MCP server listed in the public MCP registry as xyz.asof/asof-demo. No-sign-up demo: recorded historical crypto wallet holdings, prices and CSV exports. Fixed examples. This page covers its hosted endpoint (https://demo.asof.xyz/mcp).

Is the AsOf Demo MCP server safe to use?

AsOf Demo scores 68 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 AsOf Demo MCP server expose?

AsOf Demo exposes 6 tools: list_demo_wallets, get_holdings, retrieve_holdings, get_historical_price, export_holdings_csv, get_demo_guide. Their descriptions and schemas cost roughly 250 tokens of context every time the server is loaded.

Does the AsOf Demo MCP server require authentication?

No. We connected to AsOf Demo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AsOf Demo MCP server still maintained?

AsOf Demo is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.