MCP server for interacting with the Scryfall MTG API
Nothing to run from here
Gdharness 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.
94/100
trust score
1k
downloads a day
local
runs on your machine
42k
downloads in 30d
What it does
A harness for driving a Godot 4 project from an agent: addons, runtime bridge, MCP server, CLI.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user gdharness-mcp '--' npx -y gdharness
# 2 — ask your agent for something these tools do
# project_info, project_settings, project_search and 24 more
Gdharness costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
PublisherVerified · since 2026
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Gdharness as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user gdharness-mcp '--' npx -y gdharnessReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take GODOT_PATH (Absolute path to the Godot 4.7 or newer executable. Without it, the usual install locations are searched.) if you want to set it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
27 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.
What a project is: its name and main scene from project.godot, the Godot that answers, and how many scenes, scripts and assets it holds, with optional sections on top.
No parameter schema on file.
Reads or writes project.godot: settings, autoloads, the main scene, input actions, plugins and audio buses.
No parameter schema on file.
Searches text or a regular expression across project files and returns file paths with line numbers.
No parameter schema on file.
What a resource depends on, or what depends on it.
No parameter schema on file.
The import pipeline: what needs importing, how a resource is imported, reimports, UIDs, and the global class list the editor and the engine read.
No parameter schema on file.
Export presets and exports.
No parameter schema on file.
Runs the project
No parameter schema on file.
Creates a scene file, saves one, or saves a copy under a new path. Needs the editor connected.
No parameter schema on file.
The nodes of a scene file: names, classes and hierarchy, with properties when asked. Needs the editor connected.
No parameter schema on file.
Signal connections in a scene file. Needs the editor connected.
No parameter schema on file.
Animations in an AnimationPlayer and states in an AnimationTree state machine. Needs the editor connected.
No parameter schema on file.
Creates a GDScript file, or adds functions, variables and signals to one. Every declaration written carries a type. create loads what it wrote under the project
No parameter schema on file.
What a script contains: its structure from the file, or symbols, completions and hover text from the editor
No parameter schema on file.
Errors and warnings for a script from the editor
No parameter schema on file.
Resource files: create any ClassDB resource as .tres, change one, write a shader, build a TileSet, or set a Theme colour or font size. A material is a create with resourceType StandardMaterial3D, ShaderMaterial or CanvasItemMaterial. Needs the editor connected.
No parameter schema on file.
What the project started by editor_run has printed, as entries with a severity: the errors and warnings the engine reported, each with where it happened, and everything else as info. Answers with the counts and the verdict as well as the entries.
No parameter schema on file.
Whether the editor addon is connected, which Godot answers, whether the editor is playing something, and whether a game with the runtime addon is reachable.
No parameter schema on file.
Makes the running editor scan the project filesystem, so files written outside it, and any class_name they declare, become visible. Needs the editor connected.
No parameter schema on file.
The engine
No parameter schema on file.
Questions about the running game: the scene tree, the nodes matching a query, where one node is on screen, what one property reads, or the performance metrics. Needs the game running with the runtime addon.
No parameter schema on file.
Sets a property or calls a method on a node in the running game. Needs the game running with the runtime addon.
No parameter schema on file.
A picture of the running game: the whole screen or one viewport, as an image. Needs the game running with a window.
No parameter schema on file.
Input to the running game: a whole click on a Control named by path, or a raw action, key, mouse button or mouse motion. All of it works headless, where the window is 64 by 64 and the GUI only takes what is inside it.
No parameter schema on file.
Lets the running game get on with it and answers when something has happened: a number of frames, a signal, or a property reaching a value. Needs the game running with the runtime addon.
No parameter schema on file.
Sets or removes a breakpoint through the editor
No parameter schema on file.
Continues or steps the debugged game through the editor
No parameter schema on file.
Where the debugged game is stopped: the stack trace, what is in scope at a frame with the values, or the debug adapter
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Gdharness 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: —
ATrust score 94 / 100
Release 1.2.27 · scanned 14 Oct 2026
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 score100
Client score94
Findings5 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digest7e66621dfb3939e36136fb505f13ea447e91afd370d0ffb257d642c158467cf3
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
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 digest7e66621dfb3939e3
Scanned2026-10-14
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.2.27. Pin a release below and the command asks for exactly that one.
1.2.27
14 Oct 2026
latestNo release note was published with this version.
1.2.26
14 Oct 2026
No release note was published with this version.
1.1.50
8 Oct 2026
No release note was published with this version.
1.1.48
7 Oct 2026
No release note was published with this version.
1.1.47
6 Oct 2026
No release note was published with this version.
1.1.45
6 Oct 2026
No release note was published with this version.
1.1.44
6 Oct 2026
No release note was published with this version.
1.1.43
5 Oct 2026
No release note was published with this version.
1.1.42
4 Oct 2026
No release note was published with this version.
1.1.41
3 Oct 2026
No release note was published with this version.
1.1.40
3 Oct 2026
No release note was published with this version.
1.1.39
3 Oct 2026
No release note was published with this version.
1.1.37
3 Oct 2026
No release note was published with this version.
1.1.35
2 Oct 2026
No release note was published with this version.
1.1.33
2 Oct 2026
No release note was published with this version.
1.1.26
30 Sep 2026
No release note was published with this version.
1.1.13
27 Sep 2026
No release note was published with this version.
1.1.0
25 Sep 2026
No release note was published with this version.
1.0.18
23 Sep 2026
No release note was published with this version.
0.13.39
20 Sep 2026
No release note was published with this version.
0.12.16
18 Sep 2026
No release note was published with this version.
0.10.0
16 Sep 2026
No release note was published with this version.
0.5.3
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 Gdharness 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.