MCP bridge and shared tools for NextScope.
Lootatlas 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.
What it does
DayZ game data: item database, loot spawns, weapon comparisons, server search and config checks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user lootatlas-mcp '--' npx -y @reneturcios/lootatlas mcp
# 2 — ask your agent for something these tools do
# search_items, get_item, where_to_find_item and 9 more
Lootatlas costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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 Lootatlas 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.
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 lootatlas-mcp '--' npx -y @reneturcios/lootatlas mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
12 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Search the DayZ item database (vanilla game files, about 5,000 classes) by name in any language or by class name, optionally filtered by category or loot tier. Returns class names, weight, inventory size and loot tiers. Use get_item for the full record of one item and compare_weapons for damage to…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Name or class name, e.g. 'akm', 'Verband', 'bandage' |
| category | string | no | — |
| tier | string | no | Only items that spawn in this loot tier |
| sort | string | no | name = best match first when a query is given; damage = ammo hit value; rpm = full-auto rate of fire |
| include_mods | boolean | no | Also list Namalsk mod items |
| page | integer | no | — |
| limit | integer | no | — |
| lang | string | no | Language for names, descriptions and links |
Full record of one DayZ item by class name (or dzpage.com slug): weight, inventory and cargo size, stack size, weapon stats, compatible magazines, ammunition and attachments, loot tiers, usages, maps, nominal/min counts, lifetime, building classes it spawns in, crafting recipes and repair kits.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| class_name | string | yes | DayZ class name, e.g. AKM or Mag_AKM_30Rnd |
| lang | string | no | Language for names, descriptions and links |
Where an item can spawn on a map: the places with the most loot buildings that can hold it, with coordinates, grid square, loot tier zone and building types, plus the total number of buildings, the item's loot tiers and nominal count, and a link to the dzpage.com interactive loot map with every…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| item | string | yes | Class name or item name, e.g. AKM, KA-M, BandageDressing |
| map | string | no | — |
| limit | integer | no | How many places to list |
| lang | string | no | Language for names, descriptions and links |
Compare up to 6 DayZ firearms by damage per shot (health, blood, shock) at given distances, torso hits to kill a fresh player with and without a vest, muzzle velocity, rate of fire, dispersion and magazine size. Values are computed from the game's ammo config and speed falloff, the same way as the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| weapons | array | yes | Weapon class names, e.g. ['AKM', 'M4A1']. Append ':<ammo class>' to pick non-default ammo, e.g. 'AKM:Ammo_762x39Tracer' |
| distances_m | array | no | — |
| vest | string | no | Armor class name for the 'with vest' column, e.g. PlateCarrierVest or PoliceVest |
| lang | string | no | Language for names, descriptions and links |
Stats of a DayZ infected type: health per hit zone and damage multipliers, attack damage and bleed chance, movement speed, what it drops (chance per item on the chosen map, computed from cfgspawnabletypes.xml and cfgrandompresets.xml) and which spawn events use it. Search by display name in any…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| map | string | no | — |
| lang | string | no | Language for names, descriptions and links |
Search the dzpage.com list of DayZ community servers for PC, PlayStation and Xbox. PC servers come with live player count, queue, version, first or third person, time acceleration and address; console servers only with their listed details. 20 results per page. Server names, maps, versions and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Part of the server name or an IP address |
| platform | string | no | — |
| map | string | no | Map, e.g. Chernarus, Livonia, Sakhal, Namalsk, Deer Isle (mission names like chernarusplus or enoch work too) |
| tags | array | no | — |
| region | string | no | PC only: eu, na, sa, as, oc, me, af |
| perspective | string | no | PC only |
| only_online | boolean | no | PC only |
| min_players | integer | no | PC only |
| free_slots | boolean | no | PC only: hide full servers |
| no_password | boolean | no | PC only |
| sort | string | no | players, best (votes), free (slots), newest or name; consoles support best, newest and name |
| page | integer | no | — |
| lang | string | no | Language for names, descriptions and links |
What each DayZ update changed in the vanilla Central Economy files (types.xml, events.xml, cfgspawnabletypes.xml, globals.xml, cfggameplay.json), taken from Bohemia's public repository. Without version: the list of updates. With version: added, removed and changed entries. With item and no…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | no | Update id from the list (e.g. '1-29-2026-07-15') or a version like '1.29' for its first release |
| item | string | no | Only entries for this class or setting name, e.g. 'AKM' |
| map | string | no | — |
| lang | string | no | Language for names, descriptions and links |
Turn the wanted real-time length of day and night into serverTimeAcceleration and serverNightTimeAcceleration for serverDZ.cfg, using the real sunrise and sunset of the map on the in-game date. Returns the values, the resulting real durations and a ready serverDZ.cfg block.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| map | string | no | — |
| day_minutes | number | yes | Wanted daylight duration in real minutes |
| night_minutes | number | yes | Wanted night duration in real minutes |
| date | string | no | Pin the server to this in-game date (MM-DD). Without it the server keeps serverTime = "SystemTime" and the values are computed for today |
| lang | string | no | Language for names, descriptions and links |
Explain one setting of a DayZ server's db/globals.xml (e.g. LootDamageMax, CleanupLifetimeDeadPlayer, ZombieMaxCount) or cfggameplay.json (e.g. staminaMax, disableBaseDamage, PlayerData.StaminaData.staminaMax): what it does, the vanilla value (per map for cfggameplay.json), the engine default…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setting | string | yes | Variable name from globals.xml, or key or path from cfggameplay.json |
| map | string | no | cfggameplay.json only: vanilla value of this map instead of all maps |
| lang | string | no | Language for names, descriptions and links |
Check a DayZ server file (types.xml, events.xml, cfgspawnabletypes.xml, globals.xml, mapgroupproto.xml, cfggameplay.json, mod configs) for syntax errors the server would choke on: unclosed tags, raw &, wrong nesting, trailing commas, comments, BOM. Finds all errors at once with line and column,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content | string | yes | Full file content |
| file_name | string | no | Used to tell XML from JSON |
| lang | string | no | Language for names, descriptions and links |
Analyze a DayZ server log (.RPT, script_*.log or crash_*.log) and explain each problem in plain words: crashes, script errors with the likely mod, broken economy files, missing classes, spawn point and persistence problems, low server FPS. Groups repeated lines, marks messages that also appear on…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| log | string | yes | Log text; for very long logs send the part around the problem |
| file_name | string | no | Original file name, e.g. DayZServer_x64_2026-10-06_12-00-00.RPT |
| lang | string | no | Language for names, descriptions and links |
Find the dzpage.com browser tool for a task described in plain words, e.g. 'more loot on my server', 'shorter nights', 'place buildings on the map', 'why does my server crash'. Returns tool names, what they do and links. With an empty task it lists all tools. To answer where a specific item…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | no | What the user wants to do, in any of the site languages |
| lang | string | no | Language for names, descriptions and links |
- 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 Lootatlas or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
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. minimal 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. | ||
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
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 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
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.
Any signed-in account that does not publish Lootatlas can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.