MCP server for interacting with the Scryfall MTG API
Nothing to run from here
Nightbreak Forge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
95/100
tool-list score
10
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read-only knowledge of Nightbreak Minecraft plugins: wiki, source, config schemas and validation.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http nightbreak-forge-mcp https://forge.nightbreak.io/mcp
# 2 — ask your agent for something these tools do
# search_plugin_source, fetch_plugin_source_file, get_local_lua_reference and 7 more
Nightbreak Forge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NIAll 1 server
nightbreak1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http nightbreak-forge-mcp https://forge.nightbreak.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search the EliteMobs, MagmaCore, BetterStructures, FreeMinecraftModels, CannonRTP and ResurrectionChest source code for a query. By default searches every mirrored repo by file content (grep). MagmaCore contains shared core functionality (Lua engine, base entity tables, scripting helpers) used by every plugin — always check it for hooks, helpers, or context methods that feel like they should be co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Text or regex to grep for. Symbol names, hook names, error messages. |
| repos | array | no | Optional. Defaults to every mirrored repo. |
| mode | string | no | "content" (default) greps file contents; "path" matches file paths. |
| path_prefix | string | no | Optional. Restrict to a subdirectory like "src/main/java/". |
| max_results | number | no | Default 20. |
Fetch a file from a mirrored plugin source repo. Optional line slicing for large files.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | yes | — |
| path | string | yes | Repo-relative path, e.g. "src/main/java/com/magmaguy/elitemobs/powers/lua/LuaPowerRuntime.java". |
| line_start | number | no | Optional. Read from this line (1-indexed). |
| line_end | number | no | Optional. Read up to and including this line. |
Read the current Nightbreak Forge local Lua validator/editor reference. Use this to see which hooks, fields, methods, exact values, and handle helpers the editor currently knows about. Pass script_type matching the file you are working on: "lua-power" (default, EliteMobs boss powers — includes context handles, em, and exact values), "fmm-script" (FMM props), or "npc-script" (EliteMob
| Parameter | Type | Required | Notes |
|---|---|---|---|
| script_type | string | no | Which script type's reference to return. Defaults to "lua-power". |
| scope | string | no | Optional scope. For lua-power: "hooks", "context", "boss", "player", "event", "script", "handles", "em", or "values". For fmm-script/npc-script: "hooks", "context", or a context namespace name (e.g. " |
Validate a draft Lua script against the local Nightbreak Forge Lua validator. Use this before finalizing generated Lua files to catch unknown helpers, invalid fields, or malformed file structure. IMPORTANT: pass script_type matching the file you are generating. Use "lua-power" (default) for EliteMobs custom-boss Lua powers (files in powers/), "fmm-script" for FreeMinecraftModels prop s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content | string | yes | Full Lua script file content to validate. |
| script_type | string | no | Which validator ruleset to apply. "lua-power" for EliteMobs boss powers, "fmm-script" for FMM prop scripts, "npc-script" for EliteMobs NPC scripts, "mind-behavior" for behaviors/ programs and |
| path | string | no | Optional path such as "powers/example.lua" or "scripts/fireball_wand.lua" for reporting context. |
Search the Nightbreak wiki for relevant pages and snippets. Matching is by word and case-insensitive, ranked by title, page name and body. Each result has a page value to pass to fetch_wiki_page. Use for high-level docs, examples, and tutorials — not for symbol verification (use search_plugin_source for that).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keywords to search for, such as "lua power files", "creating bosses", or "elitescript bridge". |
| max_results | number | no | Maximum number of results to return. Defaults to 10. |
Fetch and extract readable content from a specific Nightbreak wiki page such as "EliteMobs/lua_getting_started". Page names change as the wiki grows: take them from search_wiki results. A missing page returns suggestions with the closest existing pages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| path | string | yes | Wiki page path relative to the site root, for example "EliteMobs/lua_getting_started" or "EliteMobs/creating_bosses". |
Where each config type's files go and the plugin rules Forge's own assistant follows: per-type notes, the newer plugins' knowledge, boss movement and combat AI, and the Lua hook quick reference. Read it once before writing files.
No parameter schema on file.
The config file types Forge knows for the released plugins, with each type's plugin, label, server path, format and wiki page. Pass a type to get_config_schema or as the path when validating.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plugin | string | no | Optional plugin id to filter by, such as "elitemobs", "betterstructures" or "fmm". |
One config type's fields as Forge edits and validates them: key, value type, default, whether it is required, description and allowed values. Long option lists are shortened; pass field to get one field with all its options.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | A type from list_config_types, such as "custom-boss" or "fmm-pet". |
| field | string | no | Optional field key; returns only that field, with every allowed value. |
Validate plugin config files (YAML and Lua) with Forge's validator: required fields, allowed values, plugin rules, Lua analysis, and references between the files you send (a boss's powers, a dungeon's bosses). Send each file with its server path, such as "plugins/EliteMobs/custombosses/frost_king.yml", so Forge can tell its type. A reference to a file you did not send is reported as not found in t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| files | array | yes | The files to check together. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Nightbreak Forge or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 95 / 100
Release 1.0.0 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score99
Client score95
Findings1 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestdcadefa8b8d4744841a3f60bec88fa05cc336a94cdfbf171a97646cbd82db267
Score vectorthreat 99 → client 95
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_plugin_source | no tags | |
| fetch_plugin_source_file | untrusted-input | untrusted-input: keyword "fetch" |
| get_local_lua_reference | no tags | |
| validate_lua_power_draft | no tags | |
| search_wiki | no tags | |
| fetch_wiki_page | untrusted-input | untrusted-input: keyword "fetch" |
| get_authoring_notes | no tags | |
| list_config_types | no tags | |
| get_config_schema | no tags | |
| validate_config_files | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestdcadefa8b8d47448
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Nightbreak Forge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.