Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Marchward MCP

by marchwardversion 0.2.4i★ –iRuns on your computer
Registry nameai.marchward/mcp-server

Install

Overview

Description from the maker (original English)

Runtime authority for AI agents: credential mediation, spend cap, approval gates, audit log.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: MARCHWARD_API_URL, MARCHWARD_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: MARCHWARD_API_URL, MARCHWARD_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "marchward": {
      "command": "npx",
      "args": [
        "-y",
        "@marchward/mcp-server"
      ],
      "env": {
        "MARCHWARD_API_URL": "your-value",
        "MARCHWARD_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add marchward --env MARCHWARD_API_URL=your-value --env MARCHWARD_API_KEY=your-value -- npx -y @marchward/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "marchward": {
      "command": "npx",
      "args": [
        "-y",
        "@marchward/mcp-server"
      ],
      "env": {
        "MARCHWARD_API_URL": "your-value",
        "MARCHWARD_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "marchward": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@marchward/mcp-server"
      ],
      "env": {
        "MARCHWARD_API_URL": "your-value",
        "MARCHWARD_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • MARCHWARD_API_URL required env
    Marchward API base URL
  • MARCHWARD_API_KEY secret required env
    Your Marchward API key (mw_...)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain marchward.ai (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32489 servers in this category
  • Published to the registry more recently than 14% of the other 32489 servers in this category
  • Basic checks equal to or better than 100% of the other 32489 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Marchward MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MARCHWARD_API_URL, MARCHWARD_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.4) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Whisper

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Whisper

by whisper-sec

One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Marchward · runtime authority for AI agents

Marchward

Govern what your AI agents are allowed to _do_. Marchward is one open layer that sits in front of an agent's tool calls and enforces four controls before any action runs, then writes a tamper-evident record of every decision. Self-hostable, Apache-2.0, framework-agnostic.

  • Credential mediation. The agent holds one Marchward key, never your real GitHub, Stripe, or database credentials. The real secret is injected at execution, and the agent never sees it.
  • Inference spend cap. A hard ceiling on agent spend, so a runaway loop can't drain a budget.
  • Approval gates. Irreversible actions pause for a human instead of running unattended.
  • Tamper-evident audit. Every decision appends to a hash-chained log you can verify offline. Provable, not just logged.

Most tools in this space cover one of these. Marchward brings all four together in one place, open and self-hostable.

Output guardrails check what an agent _says_ (toxicity, PII, topic). Marchward governs what an agent _does_ (spend, delete, act). A check on the agent's output cannot stop an agent that still holds the keys and can make a different call. Marchward governs the action itself.

Built for teams already running agents in production (LangGraph, LangChain, raw SDKs, any MCP server, or one HTTP call from any runtime) who need an agent to be autonomous without being able to drain a budget, take an irreversible action unattended, or act without an audit trail.

Quickstart: govern an agent in 60 seconds (fully local, no account)

marchward-proxy wraps any MCP server as a child process and evaluates every tools/call against your policy before it runs (block, allow, or pause for human approval), entirely on your machine, with your own credentials.

# Write a policy (escalate anything destructive, allow the rest)

cat > policy.json <<'EOF' { "rules": [ { "match": { "toolPattern": "*delete*" }, "decision": "ESCALATE" }, { "match": { "toolPattern": "*" }, "decision": "ALLOW" } ]} EOF

Put Marchward in front of your agent's MCP server, local mode, no API

npx -p @marchward/proxy marchward-proxy \ --command "node my-mcp-server.js" \ --policy-file ./policy.json \ --local

Every tool call your agent makes now passes through policy first, and lands in a local tamper-evident (hash-chained) audit log you can verify offline. No account, no network call to us.

Prefer the SDK? pip install marchward and wrap calls with marchward.execute(). Point it at your own self-hosted setup, or at the managed plane (below).

What's open vs. what's hosted

The open packages in this repo are a fully functional self-host governor. Some operational features need shared state and run on the hosted plane (free tier, no card):

Open (self-host, this repo)Hosted plane (Marchward Cloud)
Execution control: allow / block / escalate tool calls by policyyesyes
Local governor (MCP/HTTP intercept, your own credentials)yesyes
Tamper-evident audit: hash-chain primitive + offline verifyyesretained, queryable, monitored
Approval-gate decisionyes+ managed workflow (notify, approve, resume)
Inference cost caplocal accountingenforced (rolling-window spend)
Credential mediation (agent holds one key, real cred injected, the agent never sees it)yes, from your own local secret storeyes, managed vault
Managed credential vault, multi-tenancy, SSO/RBACnoyes

So: self-host this for execution control, credential mediation from your own local store, a local cost cap, and a local audit log; add the free hosted tier for the managed credential vault (rotation, team sharing), approval workflows, retained audit-as-a-service, and cross-agent enforcement. Same engine underneath. The proxy's --remote mode just points at the plane.

How it works

  1. Your agent makes a tool call (MCP, HTTP, or via the SDK).
  2. Marchward evaluates it against your policy. Risk is judged by the resolved action: any destructive operation (a DELETE, a flagged destructive POST) is gated regardless of what the tool is _named_, so a custom-named destructive tool cannot slip past.
  3. The decision, ALLOW / ESCALATE / BLOCK, is enforced before the call runs and appended to a hash-chained audit log.
  4. Credential mediation means your agent holds only a Marchward key. The proxy injects the real service credential (from your own local store when self-hosted, or the managed vault on the hosted plane), so a rogue "different tool call" cannot misuse a credential the agent never held.

Packages

  • `@marchward/engine`: the deterministic decision engine + hash-chain audit primitive (zero dependencies).
  • `@marchward/proxy`: the local governor (MCP + HTTP), --local or --remote.
  • `@marchward/sdk` (TypeScript) and `marchward` (Python, on PyPI): clients.

Project

  • Contributing: CONTRIBUTING.md (DCO sign-off, git commit -s)
  • Security: SECURITY.md · Conduct: CODE_OF_CONDUCT.md · Governance: GOVERNANCE.md
  • Trademark: TRADEMARK.md. The code is open (Apache-2.0); the name is not.
  • What's open vs. commercial: OPEN-VS-COMMERCIAL.md · our licensing commitment (the engine stays open, no relicensing rug-pull).
  • License: Apache-2.0.
  • Hosted free tier: https://app.marchward.ai/signup (500 decisions/mo, no card).
Ask PopNx