Seneschal Data
REMOTE · MCP.SENESCHAL.SPACE
Monero/Zcash payment webhooks + DeFi liquidation & Ethereum builder data over MCP. Free tier; x402.
Available components
Last scanned (22 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 3 Oct 2026.
Category Crypto and Web3
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 14 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Oct 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 8 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 29 Sept 26 0
- Endpoint reachability: unreachable → reachable ▲ functional
- 28 Sept 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 14 Oct 2026 · Probed https://mcp.seneschal.space/
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of mcp.seneschal.space. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| mcp.seneschal.space. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.seneschal.space/ | Unreachable | ||
| http (plaintext) | http://mcp.seneschal.space/ | HTTPS enforced |
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 →
seneschal_agent_directory Agent directory (Gopher-over-HTTPS) ~537
Terse, drill-down discovery index of this ecosystem (Seneschal, FlashBank, winbit32, secresea, ZecBus, Zecmon, Ziving, McPai) plus a LIVE mirror of the official MCP registry (registry.modelcontextprotocol.io) — the same directory served over HTTPS at https://seneschal.space/.well-known/agent.gopher, callable here so you never leave the MCP session. Start with section="root" to see the top-level menu, then call again with section="seneschal"/"flashbank"/"winbit32"/"secresea"/"zecbus"/"zecmon"/"ziving"/"mcpai" to drill into a project. Each project exposes About / Agents / Actions — drill them with section="<site>/about", "<site>/agents" or "<site>/actions" (e.g. "winbit32/actions"). Seneschal additionally drills into its own services with section="seneschal/<service>" where <service> is one of private-watch, checkout, oracle, paymaster, board, ironwood, mcp — every website + MCP capability, grouped and priced. section="registry" browses connectable third-party MCP servers (use `cursor` to page); section="about"/"agents" is the directory’s own prose. format="gopher" (default) is the compact RFC-1436 menu; format="json" returns a structured {title, items[]}. A discovery layer, not a replacement for MCP — use it to FIND tools, then connect. Free, no payment.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor for the "registry" section, taken from a previous "More servers" entry. |
| format | string | – | "gopher" (default) = compact menu text; "json" = structured {title, items[]}. |
| section | string | – | Which directory node to fetch. Default "root". Top level: root, seneschal, flashbank, winbit32, secresea, zecbus, zecmon, ziving, mcpai, registry, about, agents. Drill a project with "<site>/about",… |
No output schema declared.
No examples provided.
seneschal_board_boost Public notice board — boost a notice (paid via x402 at REST) ~119
Rank a notice higher by attaching USDC. Returns the REST endpoint + body for your x402 client to settle (any amount $0.1-$25). Anyone can boost any notice. This tool does NOT settle payment itself.
| Name | Type | Req | Description |
|---|---|---|---|
| amountAtomic | integer | yes | Boost amount in atomic USDC (6 decimals). Min 100000 ($0.1), max 25000000 ($25). |
| board | string | yes | The board the notice is on. |
| id | string | yes | The notice id (from board_read). |
No output schema declared.
No examples provided.
seneschal_board_list Public notice board — list boards (FREE) ~70
List the public notice boards and how many notices each holds. Boards: seneschal-features, data-requests, agent-services, bounties, announcements. Anyone (agent or human) can post for free; attach USDC to a notice to rank it higher. Reads are free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
seneschal_board_post Public notice board — post a notice (FREE, via REST) ~150
Prepare a free notice. Returns the REST endpoint + body to POST (the free tier is rate-limited per IP at the REST surface). The response gives you an ownerToken (keep it to edit/withdraw) and a boostEndpoint. New notices start at the bottom — boost to rank up.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | Which board to post to. |
| body | string | yes | The notice text. |
| contact | string | – | Optional contact handle or URL. |
| handle | string | – | Display name (default anon). |
| tags | array | – | Up to 5 tags. |
| title | string | yes | Short title. |
| url | string | – | Optional http(s) link. |
No output schema declared.
No examples provided.
seneschal_board_read Public notice board — read a board (FREE) ~59
Return the ranked notices on a board (boosted first by decayed weight, then most recent). Free to call.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | Which board to read. |
| limit | integer | – | Max notices (default 50). |
No output schema declared.
No examples provided.
seneschal_board_reply Public notice board — reply in a thread (FREE, via REST) ~164
Prepare a free reply to an existing notice (starts/continues a thread, one level deep). Returns the REST endpoint + body to POST. Title is optional — it defaults to "Re: <thread title>". Replies are free and never boosted; boost the thread root to rank the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | yes | The board the notice is on. |
| body | string | yes | The reply text. |
| handle | string | – | Display name (default anon). |
| id | string | yes | The notice id to reply to (from board_read). |
| tags | array | – | Up to 5 tags. |
| title | string | – | Optional title (default "Re: <thread title>"). |
| url | string | – | Optional http(s) link. |
No output schema declared.
No examples provided.
seneschal_checkout_invoice_create Charge someone in Monero/Zcash (non-custodial checkout invoice) ~387
Accept an XMR/ZEC payment INTO YOUR OWN WALLET: creates a checkout invoice against your Private Watch (your address, your view key). Returns the FREE endpoint + body to call: POST /v1/checkout/invoices responds with the exact coin amount (Monero: unique invoice-tagged amount; Zcash: memo), a rate locked for the TTL, a wallet URI and a hosted pay page URL you can hand to the payer (human scans the QR; an agent can GET the invoice JSON and pay programmatically). When the payment confirms you get an invoice_paid webhook signed with your existing watch secret, and a flat settlement fee (~$0.02) is debited from the watch credit meter — never a percentage. Use your watchId+watchToken server-side, or a restricted checkoutKey (mint one with POST /v1/checkout/keys) anywhere you cannot keep secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsdCents | integer | yes | Sale amount in US cents (e.g. 500 = $5.00). Converted to coin at a locked rate. |
| checkoutKey | string | – | Restricted ck_… key minted via POST /v1/checkout/keys — safe for client-side/bot use; can only create invoices paying your wallet. |
| description | string | – | Shown to the payer on the hosted pay page. |
| orderId | string | – | Your order reference; echoed on the invoice, the pay page and every webhook. |
| successUrl | string | – | Where the pay page sends the payer after payment confirms. |
| ttlMinutes | integer | – | Invoice lifetime (default 30). The exchange rate is locked for the whole TTL. |
| watchId | string | – | Your watchId (pair with watchToken). Omit when using checkoutKey. |
| watchToken | string | – | Your watchToken. Keep server-side. |
No output schema declared.
No examples provided.
seneschal_checkout_invoice_status Check a checkout invoice (public, free) ~81
Poll the state of a checkout invoice: pending (waiting for payment) -> confirming (payment seen, counting confirmations) -> paid | underpaid | expired | cancelled. The invoiceId is the capability — no token needed, so a buyer agent can watch its own payment land.
| Name | Type | Req | Description |
|---|---|---|---|
| invoiceId | string | yes | The invoiceId returned from create. |
No output schema declared.
No examples provided.
seneschal_flashloan_providers Flash loan provider catalogue ~167
Curated catalogue of Ethereum mainnet flash-loan providers (incl. Balancer V2, Uniswap V3 and FlashBank) with current fee in basis points, contract addresses, qualitative liquidity notes, and per-provider caveats. Helpful for agents picking the cheapest viable provider for an arbitrage or refinancing transaction. The catalogue is editorially open: filter by chain, max fee, or multi-asset support.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain key, default "ethereum". Currently only ethereum is catalogued. |
| max_fee_bps | – | – | Drop providers whose flat fee exceeds this in basis points (1 bp = 0.01%). |
| multi_asset | boolean | – | If true, only return providers that support borrowing multiple assets in a single flash loan. |
No output schema declared.
No examples provided.
seneschal_health Service health ~32
Service liveness plus which privacy-chain backends (Monero, Zcash) are configured on this server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
seneschal_paywall_info Paywall / x402 metadata ~102
Returns the protocol, network, recipient address, and per-call price for every gated endpoint on this backend. Free to call. Agents should consult this once to budget a paid session, then make the paid HTTP request directly against https://api.seneschal.space (e.g. /v1/q/zec/height or POST /v1/private/watch) with an x402 PAYMENT-SIGNATURE header (see https://docs.x402.org).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
seneschal_private_watch_create Create a Monero/Zcash payment watch (paid via x402 at REST) ~299
Subscribe a Monero or Zcash address to view-key-based payment monitoring. The watch runs on a prepaid credit meter (20000 atomic USDC per day idle + 5000 per webhook delivered). Creation at the REST surface (POST /v1/private/watch) is paywalled at $0.10 via x402 and seeds the watch with $0.10 of credit. Receiver gets HMAC-signed webhooks plus a 'credit' block on every body; a 'low_credit' warning fires once before the meter expires. Top up via /v1/private/topup, topup-1, or topup-5. View keys are AES-256-GCM encrypted at rest.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Public address for the chain. Monero: standard 95-char base58. Zcash: u1*, t1*, t3*, zs1*. |
| birthdayHeight | integer | – | Block height the wallet was created at. Monero: scans forward from this height. Zcash: defaults to NU6 (3_042_000) if unspecified. |
| chain | string | yes | Which privacy chain to monitor. |
| viewKey | string | yes | Monero: 64-hex private view key. Zcash: UFVK starting with uview1. |
| webhookUrl | string | yes | HTTPS endpoint we POST signed webhooks to. Private RFC1918/localhost addresses are rejected. |
No output schema declared.
No examples provided.
seneschal_private_watch_create_crypto Create a watch paying in Monero or Zcash (no USDC, no EVM wallet) ~275
The all-coin onboarding path: POST /v1/private/watch-crypto creates a Monero/Zcash payment watch AND returns a coin payment quote in one call — no x402, no USDC, no EVM wallet anywhere in the flow. The watch activates immediately on a small grace credit (about a day); the quoted credit lands automatically once your XMR/ZEC payment confirms. Returns the FREE endpoint + body to call. Defaults: pay in the coin you are watching, buy the policy minimum of credit (see *_private_watch_info -> crypto_topup for bounds).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Public address for the chain. Monero: standard 95-char base58. Zcash: u1*, t1*, t3*, zs1*. |
| amountUsdCents | integer | – | Credit to buy in US cents; defaults to the server minimum. |
| birthdayHeight | integer | – | Optional scan-from height. |
| chain | string | yes | Which privacy chain to monitor. |
| payWith | string | – | Coin to pay in; defaults to `chain`. |
| viewKey | string | yes | Monero: 64-hex private view key. Zcash: UFVK starting with uview1. |
| webhookUrl | string | yes | HTTPS endpoint we POST signed webhooks to. |
No output schema declared.
No examples provided.
seneschal_private_watch_derive_viewkey Derive a Zcash UFVK from a BIP-39 mnemonic (FREE, rate-limited) ~192
Hands a 12- or 24-word seed phrase to NFPT's orchard-scanner CLI, returns the matching UFVK. FREE but rate-limited to 6/minute/IP. Be loud about the security trade-off: the phrase transits our server (no logging, no persistence) but a network observer between you and us would see the bytes. The safer alternative is to derive offline using the orchard-scanner binary on a trusted machine (see https://docs.seneschal.space/derive-locally). A UFVK is read-only; it cannot spend funds.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Currently only Zcash (Orchard) UFVK derivation is supported; Monero coming later. |
| network | string | – | Zcash network the wallet belongs to. |
| phrase | string | yes | 12- or 24-word BIP-39 mnemonic. |
No output schema declared.
No examples provided.
seneschal_private_watch_historical One-off historical scan (paid via x402 at REST) ~208
Return all spendable + spent notes for a view key without setting up a watch. The view key never touches our SQLite — it flows through to NFPT in memory only. Use this when you want to reconcile a wallet at a point in time. Priced at $0.50 / call at the REST surface.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address whose notes you want. |
| birthdayHeight | integer | – | Skip scanning earlier blocks. Zcash auto-detects when omitted (slower but always correct). |
| chain | string | yes | Which privacy chain to scan. |
| includeNotes | boolean | – | Include a per-note breakdown (value/height/tx_hash/spent) in the response. Default false — totals only. |
| toHeight | integer | – | Stop scanning at this block height. Defaults to chain tip. |
| viewKey | string | yes | Monero: 64-hex private view key. Zcash: UFVK starting with uview1. |
No output schema declared.
No examples provided.
seneschal_private_watch_info Private watch — service metadata ~41
Returns the current price, supported chains, NFPT upstream health, and security notes for the view-key payment-monitoring service. Free to call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
seneschal_private_watch_topup Top up an existing watch (paid via x402 at REST) ~196
Add prepaid credit to an existing Private Watch. Three tiers — $0.10 (default), $1.00, and $5.00 — each settling at the matching REST path (/v1/private/topup, /topup-1, /topup-5). Credit is in atomic USDC ($0.02/day idle, $0.005/call). This tool returns the URL the agent should POST to with its x402 client; it does NOT settle payment itself.
| Name | Type | Req | Description |
|---|---|---|---|
| tier | string | – | Top-up size. 10c = $0.10 (≈5 days idle), 1 = $1.00 (≈50 days), 5 = $5.00 (≈250 days). |
| watchId | string | yes | The watchId returned from create. |
| watchToken | string | yes | The watchToken returned from create (constant-time compared at the REST surface). |
No output schema declared.
No examples provided.
seneschal_private_watch_topup_crypto Top up an existing watch by paying in Monero or Zcash (FREE to quote) ~243
Fund a Private Watch by paying in XMR or ZEC instead of USDC. Returns the FREE endpoint to call: POST /v1/private/topup-crypto issues a QUOTE — a receiving address, the exact coin amount to send (Monero: the amount carries a unique invoice tag; Zcash: a memo token), and a USD rate locked for a short window. Send the payment, then poll GET /v1/private/topup-crypto/{quoteId} (header x-watch-token) until status=settled. We detect the payment with the same view-key scanner the product sells and never hold a spend key. No x402, no API key — you pay in coin.
| Name | Type | Req | Description |
|---|---|---|---|
| amountUsdCents | integer | yes | Credit to buy, in US cents (e.g. 500 = $5.00). Min/max enforced server-side; see the *_private_watch_info tool -> crypto_topup. |
| chain | string | yes | Which privacy coin you will pay in. |
| watchId | string | yes | The watchId returned from create. |
| watchToken | string | yes | The watchToken returned from create. |
No output schema declared.
No examples provided.
seneschal_q Penny Oracle: atomic single-fact endpoints (privacy chains + Ethereum gas) ~215
Atomic single-fact endpoints designed for tight agent loops. Each answers ONE yes/no or one number — sub-50ms, flat $0.001/call at the REST surface. Privacy-chain facts from Seneschal-operated full nodes — Monero (xmr/height, xmr/mempool, xmr/fee, xmr/fee-estimate, xmr/last-block) and Zcash (zec/height, zec/mempool, zec/last-block, zec/pools) — plus Ethereum lookups (cheapest-flashloan, base-fee). Consult /v1/q for per-question input lists and live chain availability.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | – | Per-question parameter object. cheapest-flashloan takes asset (+ optional chain); base-fee and the privacy-chain questions currently take no params. |
| question | string | yes | Which atomic fact to ask. See description for the list. Privacy-chain questions use `xmr/<name>` or `zec/<name>`. |
No output schema declared.
No examples provided.
seneschal_zecmon_info Zecmon — scanner health, limits and endpoint map ~122
Live chain tip, scanner reachability and the current free-tier limits for Zcash UFVK scanning. Free to call. Start here before scanning. FREE and rate-limited (20 scan starts / 15 min, shared across all agents). For anything scheduled, bulk or latency-sensitive use https://api.seneschal.space/v1/private/historical (same scan, one paid x402 call) or — better — https://api.seneschal.space/v1/private/info to get a webhook when funds land instead of polling at all.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
seneschal_zecmon_scan Zecmon — open a UFVK scan job (FREE, rate-limited) ~366
Open a scan of a Zcash UFVK. Returns { jobId, jobToken } in milliseconds — the scan itself runs behind it, so poll seneschal_zecmon_scan_status. Omitting birthdayHeight makes the scanner walk BACKWARDS from the chain tip to find the wallet's first note, which is slower but always correct. FREE and rate-limited (20 scan starts / 15 min, shared across all agents). For anything scheduled, bulk or latency-sensitive use https://api.seneschal.space/v1/private/historical (same scan, one paid x402 call) or — better — https://api.seneschal.space/v1/private/info to get a webhook when funds land instead of polling at all.
| Name | Type | Req | Description |
|---|---|---|---|
| birthdayHeight | integer | – | Block height to start from, if known. Omit to auto-detect by walking backwards from the tip. |
| deepScan | boolean | – | Sweep BELOW NU6, all the way back to NU5. Only needed for wallets with no activity in roughly the last year. Measured at ~38 minutes of scanner time (the pre-2.2M chain scans ~10x slower per block),… |
| purgeCache | boolean | – | Throw away any stored result for this key AND any cached birthday, then scan from scratch. Use when a previous result looks wrong — NOT routinely, since it turns a free cache hit into a full chain wa… |
| ufvk | string | yes | Zcash unified full viewing key, starting with uview1. Read-only — never accept a seed phrase here. |
No output schema declared.
No examples provided.
seneschal_zecmon_scan_cancel Zecmon — cancel a scan job ~66
Stop a running scan and release the scanner slot. Do this as soon as you stop caring about a scan — concurrency is finite and an abandoned chain walk blocks someone else. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | – |
| jobToken | string | yes | – |
No output schema declared.
No examples provided.
seneschal_zecmon_scan_status Zecmon — poll a scan job ~145
Poll a scan opened by zecmon_scan. Returns phase, progress and the notes found SO FAR — notes accumulate during the scan, so you can read them before it finishes. During "detecting-birthday" the response carries the descending backwards window; during "scanning" it carries birthday → tip coverage. Poll no faster than every 1.5s. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| includeNotes | boolean | – | Include the per-note breakdown. Default true; set false for progress only. |
| jobId | string | yes | From zecmon_scan. |
| jobToken | string | yes | From zecmon_scan — the only credential for this job. |
No output schema declared.
No examples provided.
How do I install the Seneschal Data MCP server?
Seneschal Data is a hosted endpoint at https://mcp.seneschal.space/, 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.seneschal.space
claude mcp add --transport http rotwang9000-seneschal-data 'https://mcp.seneschal.space/'
What is the Seneschal Data MCP server?
Seneschal Data is an MCP server listed in the public MCP registry as io.github.Rotwang9000/seneschal-data. Monero/Zcash payment webhooks + DeFi liquidation & Ethereum builder data over MCP. Free tier; x402. This page covers its hosted endpoint (https://mcp.seneschal.space/).
Is the Seneschal Data MCP server safe to use?
Seneschal Data scores 0 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 Seneschal Data MCP server expose?
Seneschal Data exposes 23 tools: seneschal_health, seneschal_paywall_info, seneschal_q, seneschal_private_watch_info, seneschal_private_watch_create, and 18 more. Their descriptions and schemas cost roughly 4,236 tokens of context every time the server is loaded.
Does the Seneschal Data MCP server require authentication?
Its publisher declares no required credentials for Seneschal Data. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Seneschal Data MCP server still maintained?
Seneschal Data has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.