Local MCP capabilities provider for Expo
Nothing to run from here
Magicsword 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.
97/100
trust score
7
downloads a day
local
runs on your machine
623
downloads in 30d
What it does
Manage MagicSword endpoints, alerts, policies, and private intelligence through MCP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'MAGICSWORD_API_KEY=${MAGICSWORD_API_KEY}' --transport stdio magicsword-mcp '--' npx -y @magicsword-io/magicsword-mcp
# 2 — ask your agent for something these tools do
# agent_install_instructions, apply_policy_to_endpoints, find_alerts and 18 more
It needs MAGICSWORD_API_KEY: this reads it from your environment, so export it first.
Magicsword costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MIAll 1 server
magicsword-io1 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. This one runs on your machine: your client starts Magicsword 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. Claude Code reads MAGICSWORD_API_KEY (MagicSword Customer API key from Portal settings) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx MAGICSWORD_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'MAGICSWORD_API_KEY=${MAGICSWORD_API_KEY}' --transport stdio magicsword-mcp '--' npx -y @magicsword-io/magicsword-mcpReconnect, 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
It reaches a system of yours, so it needs your own credential rather than the publisher’s: MAGICSWORD_API_KEY — MagicSword Customer API key from Portal settings.. You set it in your own client’s config, on your machine — this marketplace never holds 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
21 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.
Returns the install + enroll commands for the MagicSword agent on a given platform. No API call.
No parameter schema on file.
Resolves either an explicit endpoint_ids list or a hostname_pattern (glob) into a concrete set of endpoints,
No parameter schema on file.
Search MagicSword alerts by severity, ack state, time window, hostname, or MITRE technique.
No parameter schema on file.
Promotes a MagicSword policy from audit to enforcing mode through the Portal server confirmation flow.
No parameter schema on file.
Lists available MagicSword agent releases and per-platform latest markers before an upgrade is queued.
No parameter schema on file.
Lists private intelligence feeds and, optionally, a page of items for one feed. Requires intel:read.
No parameter schema on file.
Lists endpoints (devices) enrolled in the MagicSword org.
No parameter schema on file.
Lists normalized, rule-relevant org events as JSON without raw endpoint telemetry. Use this for requests like “show me the last day of audit events” or “find blocked events for this policy”. Requires alerts:read.
No parameter schema on file.
Lists policies in the MagicSword org, including each policy's current published version (name, version, status, policy mode).
No parameter schema on file.
Creates, updates, or deletes private intelligence feeds. Organizations are limited to 3 feeds. Requires intel:write.
No parameter schema on file.
Edits or deletes one item in a private intelligence feed. Requires intel:write.
No parameter schema on file.
Lists, attaches, or detaches global/customer-owned intel feeds on a policy current version. Customer feeds only affect endpoints in that org with the feed attached. List requires policies:read; attach/detach require policies:write.
No parameter schema on file.
Lists policy rules or creates a new policy version with explicit rules or event-derived rules.
No parameter schema on file.
Mints a one-time enrollment token used to register a new MagicSword agent against the org owning the API key.
No parameter schema on file.
Queues a check-in command for one endpoint. Requires endpoints:write.
No parameter schema on file.
Fetches one endpoint directly by UUID with OS, architecture, policy, compliance, agent version,
No parameter schema on file.
Returns the active version + status for one policy by id.
No parameter schema on file.
Fetches one alert directly by id and returns its severity, endpoint, MITRE mapping, triggering events,
No parameter schema on file.
Previews or queues agent upgrades for one endpoint, explicit endpoint IDs, all endpoints on a platform, or endpoints matching a hostname glob.
No parameter schema on file.
Bulk upserts up to 100 indicators into a private feed. This is the MCP path for “extract IOCs from this report and add them to MagicSword.” Requires intel:write.
No parameter schema on file.
Returns the MagicSword organization, API key id, and granted scopes for the configured key.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- 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 Magicsword 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 97 / 100
Release 0.1.1 · 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 score97
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest8ba5d01de8b08e1310a345437da6d5edd4d1f339145ef2a75973c94070006302
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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. moderate 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 start a fixed program (a process-spawning capability, not arbitrary code execution)
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 digest8ba5d01de8b08e13
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 0.1.1. Pin a release below and the command asks for exactly that one.
0.1.1
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 Magicsword 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.