WhiteMagic hosted recall

https://mcp.whitemagic.dev/mcp

Shares a payout wallet with 1 other endpoint — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Read-only hosted recall of the WhiteMagic public corpus over MCP: memory search, session continuity, and continuity-receipt verification. OAuth 2.1 with 50 free recalls/day per grant; x402 machine payments for leases. Local-first WhiteMagic runs on your own device; this lane is the public recall service.

60
reliability

Reliability & health

Uptime and response time from our own unpaid probes, plus the reliability score built from them.

Uptime

100.0% avg
0% 50% 100% Sun 5 PMTue 10 PMFri 7 AMSun 3 PM

Response time

p50 92ms · p95 169ms
0ms 100ms 200ms Sun 5 PMTue 10 PMFri 7 AMSun 3 PM
Data table
Reliability history per time bucket over the last 7 days (hourly).
Bucket Uptime Probes Response time
9/27/2026, 5:00:00 PM 100% 1 132ms
9/27/2026, 7:00:00 PM 100% 1 115ms
9/27/2026, 10:00:00 PM 100% 1 89ms
9/28/2026, 12:00:00 AM 100% 1 110ms
9/28/2026, 2:00:00 AM 100% 1 79ms
9/28/2026, 3:00:00 AM 100% 1 101ms
9/28/2026, 5:00:00 AM 100% 1 139ms
9/28/2026, 7:00:00 AM 100% 1 169ms
9/28/2026, 9:00:00 AM 100% 1 16ms
9/28/2026, 11:00:00 AM 100% 1 89ms
9/28/2026, 1:00:00 PM 100% 1 87ms
9/28/2026, 3:00:00 PM 100% 1 87ms
9/28/2026, 5:00:00 PM 100% 1 86ms
9/28/2026, 6:00:00 PM 100% 1 83ms
9/28/2026, 8:00:00 PM 100% 1 90ms
9/28/2026, 10:00:00 PM 100% 1 90ms
9/29/2026, 12:00:00 AM 100% 1 133ms
9/29/2026, 2:00:00 AM 100% 1 82ms
9/29/2026, 4:00:00 AM 100% 1 167ms
9/29/2026, 6:00:00 AM 100% 1 94ms
9/29/2026, 8:00:00 AM 100% 1 91ms
9/29/2026, 10:00:00 AM 100% 1 95ms
9/29/2026, 12:00:00 PM 100% 1 86ms
9/29/2026, 2:00:00 PM 100% 1 114ms
9/29/2026, 4:00:00 PM 100% 1 168ms
9/29/2026, 6:00:00 PM 100% 1 94ms
9/29/2026, 8:00:00 PM 100% 1 184ms
9/29/2026, 10:00:00 PM 100% 1 167ms
9/30/2026, 1:00:00 AM 100% 1 169ms
9/30/2026, 3:00:00 AM 100% 1 86ms
9/30/2026, 5:00:00 AM 100% 1 164ms
9/30/2026, 7:00:00 AM 100% 1 92ms
9/30/2026, 9:00:00 AM 100% 1 99ms
9/30/2026, 11:00:00 AM 100% 1 95ms
9/30/2026, 1:00:00 PM 100% 1 92ms
9/30/2026, 3:00:00 PM 100% 1 90ms
9/30/2026, 5:00:00 PM 100% 1 114ms
9/30/2026, 7:00:00 PM 100% 1 170ms
9/30/2026, 9:00:00 PM 100% 1 88ms
9/30/2026, 11:00:00 PM 100% 1 85ms
10/1/2026, 1:00:00 AM 100% 1 104ms
10/1/2026, 3:00:00 AM 100% 1 158ms
10/1/2026, 5:00:00 AM 100% 1 85ms
10/1/2026, 7:00:00 AM 100% 1 83ms
10/1/2026, 9:00:00 AM 100% 1 170ms
10/1/2026, 11:00:00 AM 100% 1 117ms
10/1/2026, 1:00:00 PM 100% 1 168ms
10/1/2026, 3:00:00 PM 100% 1 90ms
10/1/2026, 5:00:00 PM 100% 1 109ms
10/1/2026, 7:00:00 PM 100% 1 137ms
10/1/2026, 9:00:00 PM 100% 1 165ms
10/1/2026, 11:00:00 PM 100% 1 84ms
10/2/2026, 1:00:00 AM 100% 1 88ms
10/2/2026, 3:00:00 AM 100% 1 113ms
10/2/2026, 5:00:00 AM 100% 1 88ms
10/2/2026, 7:00:00 AM 100% 1 84ms
10/2/2026, 9:00:00 AM 100% 1 16ms
10/2/2026, 11:00:00 AM 100% 1 84ms
10/2/2026, 1:00:00 PM 100% 1 91ms
10/2/2026, 3:00:00 PM 100% 1 14ms
10/2/2026, 5:00:00 PM 100% 1 88ms
10/2/2026, 7:00:00 PM 100% 1 117ms
10/2/2026, 9:00:00 PM 100% 1 83ms
10/2/2026, 11:00:00 PM 100% 1 84ms
10/3/2026, 12:00:00 AM 100% 1 87ms
10/3/2026, 2:00:00 AM 100% 1 109ms
10/3/2026, 4:00:00 AM 100% 1 85ms
10/3/2026, 6:00:00 AM 100% 1 77ms
10/3/2026, 8:00:00 AM 100% 1 83ms
10/3/2026, 10:00:00 AM 100% 1 87ms
10/3/2026, 12:00:00 PM 100% 1 84ms
10/3/2026, 2:00:00 PM 100% 1 92ms
10/3/2026, 4:00:00 PM 100% 1 86ms
10/3/2026, 6:00:00 PM 100% 1 116ms
10/3/2026, 8:00:00 PM 100% 1 120ms
10/3/2026, 11:00:00 PM 100% 1 63ms
10/4/2026, 1:00:00 AM 100% 1 90ms
10/4/2026, 3:00:00 AM 100% 1 84ms
10/4/2026, 5:00:00 AM 100% 1 109ms
10/4/2026, 7:00:00 AM 100% 1 82ms
10/4/2026, 9:00:00 AM 100% 1 99ms
10/4/2026, 1:00:00 PM 100% 1 111ms
10/4/2026, 3:00:00 PM 100% 1 93ms
60
Composite reliability — the weighted average of the dimensions below, on a 0–100 scale.
Availability
100

How often it was reachable when we probed it (weight 35%).

Latency
100

How quickly it answers when it is up — fast scores high (weight 20%).

Security
100

Whether it serves over working TLS / https (weight 15%).

Transparency
61

Whether the operator disclosed what it does — description, schema, identity (weight 15%).

Activity
6

Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).

Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.

See the scoring methodology for exactly how each number is computed.

Payment

Currencies
USDC
Networks
base
Facilitator
unknown
SDK
unknown

Operator

Company
inferred — unknown
Jurisdiction
—
Registrar
Squarespace Domains II LLC.
Domain registered
2025-11-13
Hosting network
—
Hosting country
—

Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.

memoryrecallsearchcontinuitysessionprovenancereceiptsverification

On-chain activity (base)

20
payments (30d)
0.14
USD volume (30d)
6
paying wallets (30d)

Payments per day

last payment 10/4/2026
0 3 5 Sep 23Sep 25Sep 30Oct 4
Data table
Settled payments per day.
Day Payments Volume (USD) Paying wallets
9/23/2026 4 0.01 1
9/24/2026 5 0.05 3
9/25/2026 3 0.03 1
9/28/2026 2 0.02 1
9/30/2026 2 0.02 1
10/2/2026 1 0 1
10/4/2026 3 0.01 1

This payout wallet is shared: figures cover all 2 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.

Linked by wallet — likely same operator

On-chain agent identity and the x402 endpoint that shares its settlement wallet.

Response schema
{
  "input": {
    "body": {
      "id": 1,
      "jsonrpc": "2.0",
      "method": "tools/call",
      "params": {
        "arguments": {
          "thought": "recall where we left off"
        },
        "name": "wm"
      }
    },
    "bodyType": "json",
    "discoverable": true,
    "method": "POST",
    "type": "http"
  },
  "output": {
    "example": {
      "result": "recall results"
    },
    "type": "json"
  }
}