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.

midnight-cast

NPM · MIDNIGHT-CAST

Read-only tools for live Midnight networks: health, transactions, DUST, errors and example code

Available components

+3 this week 92 Trust /100

Last scanned (20 hours ago)

Scores higher than 95% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 1 of 8 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Kanasjnr/midnight-cast). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 11 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1621 tokens (~90/item across 18 items; 14 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 23 Oct 26 −4
    • Malware scan: pass → unverified ▼ security
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: Kanasjnr/midnight-cast security
    • Package version: 0.2.0 → 0.2.1 functional
  • 22 Oct 26 +3
    • Stability: unverified → 0.27 ▲ functional
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 4 Nov 2026 · Analysed npm/midnight-cast@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Kanasjnr/midnight-cast
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Kanasjnr/midnight-cast/.github/workflows/publish.yml@refs/tags/v0.2.1
Rekor log index 3420502162
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:05df1758c9d14f6e3ef5885985525f586e70f2cf58bffa95f9a4cb4463a65f81e8905cd832360c51c124db3cce08f3f06b9c1ebd32d52d3fd940d215c

Background: How many MCP packages publish verified provenance →

Dependencies 8 packages
Packages resolved 8
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~1,275 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
block ~59

Read a block header: the latest one, or the block at a height.

NameTypeReqDescription
heightinteger–Block height; omit for the latest block
networkstringyesMidnight network to query: preview, preprod, mainnet, local
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

contract ~127

Look up a deployed contract by address: whether it exists, its latest action (deploy, call or update) and the circuit a call ran, the deploy transaction and block (not reported after an update), unshielded balances, and the state's size and sha256.

NameTypeReqDescription
addressstringyesContract address, hex, optionally prefixed with 0x
includeStateboolean–Also return the full state hex, which can be hundreds of kilobytes (default false)
networkstringyesMidnight network to query: preview, preprod, mainnet, local
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

decode ~96

Explain a Midnight error. Paste the whole message from a wallet, node, toolkit or Blockfrost: 1010 rejections, Custom(N) ledger codes, pallet errors, JSON-RPC codes and known tooling messages are recognised. A bare code such as 170 works too.

NameTypeReqDescription
messagestringyesThe error message or code
networkstring–Network the error came from, to check the ledger map matches it
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

dust_event ~55

Read one DUST ledger event by id from the indexer subscription.

NameTypeReqDescription
idintegeryesDUST ledger event id
networkstringyesMidnight network to query: preview, preprod, mainnet, local
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

dust_events ~88

Read DUST ledger events from the indexer: the latest ones, or a run starting at an id.

NameTypeReqDescription
frominteger–First event id; omit for the latest events
limitinteger–How many events to read (default 10, at most 50)
networkstringyesMidnight network to query: preview, preprod, mainnet, local
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

dust_status ~93

DUST generation for Cardano reward addresses: whether each is registered, its NIGHT balance, generation rate, and current and maximum DUST capacity. Use when a wallet has no DUST.

NameTypeReqDescription
addressesarrayyesCardano reward addresses (stake1… on mainnet, stake_test1… on test networks)
networkstringyesMidnight network to query: preview, preprod, mainnet, local
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

examples ~121

Working code from Midnight's official examples (midnightntwrk/midnight-examples), each compiled and tested in CI. Give a topic such as "DUST sponsorship", "send shielded tokens" or "verify a signature in a circuit" to get the examples that show it, with file paths, line ranges, links pinned to a commit and the code itself. Without a topic, lists every example and what it covers. Prefer these over writing Midnight code from memory.

NameTypeReqDescription
topicstring–What the code should show; omit to list every example
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

explain ~35

Background on a Midnight topic: dust, 1010, versions, transcript, sync.

NameTypeReqDescription
topicstringyesTopic to explain
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

health ~113

Full check of a Midnight network: RPC and indexer reachability, indexer sync against the node, and live versions against the support matrix. data.examples says whether Midnight's own examples pass on the node the network runs. Start here when something might be wrong with the network rather than the user's code.

NameTypeReqDescription
networkstringyesMidnight network to query: preview, preprod, mainnet, local
thresholdinteger–Indexer lag, in blocks, that counts as out of sync (default 100)
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

ping ~54

Check whether the network's RPC node, indexer and proof server answer, with latency and a classified error kind for each failure.

NameTypeReqDescription
networkstringyesMidnight network to query: preview, preprod, mainnet, local
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

preflight ~133

Check that a network, its proof server and optionally a wallet are ready before the first transaction: the network answers and is in sync, the proof server answers at the expected version, and the wallet holds NIGHT registered for DUST generation. data.expectations quotes how long wallet sync and restore took in Midnight's examples run, so a long first sync isn't mistaken for a hang.

NameTypeReqDescription
addressstring–The wallet's Midnight unshielded address (mn_addr_…) or a Cardano reward address (stake…)
networkstringyesMidnight network to query: preview, preprod, mainnet, local
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

tip ~69

Compare the node's latest block height with the indexer's, to see whether the indexer is behind.

NameTypeReqDescription
networkstringyesMidnight network to query: preview, preprod, mainnet, local
thresholdinteger–Lag in blocks that counts as out of sync (default 100)
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

tx ~86

Look up a transaction on the indexer: status, segments, fees, contract actions and the DUST and Zswap events it produced.

NameTypeReqDescription
bystring–What hash is (default hash)
hashstringyesTransaction hash, or an identifier when by is identifier
networkstringyesMidnight network to query: preview, preprod, mainnet, local
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

versions ~146

Compare the network's live node, runtime, indexer API and proof server with Midnight's support matrix, and a project's Midnight packages (package.json and package-lock.json) with the matrix pins. data.localProject says which directory was checked and whether it had a package.json, and data.examples whether Midnight's own examples pass on the node the network runs.

NameTypeReqDescription
checkLocalPackagesboolean–Check the project's packages at all (default true)
networkstringyesMidnight network to query: preview, preprod, mainnet, local
projectDirstring–Absolute path of the user's project; defaults to the server's working directory, which may not be the project
NameTypeReqDescription
commandstring|nullyes–
data–yes–
error–yes–
networkstring|nullyes–
nextarrayyes–
okbooleanyes–
schemaVersionnumberyes–
warningsarrayyes–

No examples provided.

Install

How do I install the midnight-cast MCP server?

midnight-cast runs locally as an npm package, launched with npx -y midnight-cast. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · midnight-cast

# add to Claude Code
claude mcp add kanasjnr-midnight-cast -- npx -y midnight-cast
Common questions

What is the midnight-cast MCP server?

midnight-cast is an MCP server listed in the public MCP registry as io.github.Kanasjnr/midnight-cast. Read-only tools for live Midnight networks: health, transactions, DUST, errors and example code. This page covers its npm package (midnight-cast).

Is the midnight-cast MCP server safe to use?

midnight-cast scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 midnight-cast MCP server expose?

midnight-cast exposes 14 tools: health, preflight, ping, tip, versions, and 9 more. Their descriptions and schemas cost roughly 1,275 tokens of context every time the server is loaded.

Is the midnight-cast MCP server still maintained?

midnight-cast is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the midnight-cast MCP server under?

midnight-cast declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.