World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Local MCP gateway: approved tools behind a signed authority check, per call or as exactly-once jobs
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 11/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 23/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Irontrellis Gateway. Follow https://mcp.popnx.com/i/zerohourzulu-irontrellis-gateway.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Irontrellis Gateway for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "irontrellis-gateway": { "command": "npx", "args": [ "-y", "@ramex-labs/irontrellis-mcp-gateway", "--config" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Irontrellis Gateway tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"irontrellis-gateway": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/irontrellis-mcp-gateway",
"--config"
]
}
}
}Use Irontrellis Gateway and tell me what you can do for me, then show me one thing✓ If Claude says it is using Irontrellis Gateway or shows a Irontrellis Gateway tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Irontrellis Gateway yet
Irontrellis Gateway runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Irontrellis Gateway
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Irontrellis Gateway for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user irontrellis-gateway -- npx -y @ramex-labs/irontrellis-mcp-gateway --config 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Irontrellis Gateway tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user irontrellis-gateway -- npx -y @ramex-labs/irontrellis-mcp-gateway --configYou should see Irontrellis Gateway listed as connected
Use Irontrellis Gateway and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Irontrellis Gateway or shows a Irontrellis Gateway tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Irontrellis Gateway for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "irontrellis-gateway": { "command": "npx", "args": [ "-y", "@ramex-labs/irontrellis-mcp-gateway", "--config" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Irontrellis Gateway tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
~/.cursor/mcp.json
Paste these settings, fill in the empty values and save
{
"mcpServers": {
"irontrellis-gateway": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/irontrellis-mcp-gateway",
"--config"
]
}
}
}Use Irontrellis Gateway and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Irontrellis Gateway or shows a Irontrellis Gateway tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Irontrellis Gateway for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "irontrellis-gateway": { "type": "stdio", "command": "npx", "args": [ "-y", "@ramex-labs/irontrellis-mcp-gateway", "--config" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Irontrellis Gateway tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
MCP: Open User Configuration
Paste these settings, fill in the empty values and save
{
"servers": {
"irontrellis-gateway": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ramex-labs/irontrellis-mcp-gateway",
"--config"
]
}
}
}Use Irontrellis Gateway and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Irontrellis Gateway or shows a Irontrellis Gateway tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user irontrellis-gateway -- npx -y @ramex-labs/irontrellis-mcp-gateway --configClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"irontrellis-gateway": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/irontrellis-mcp-gateway",
"--config"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"irontrellis-gateway": {
"command": "npx",
"args": [
"-y",
"@ramex-labs/irontrellis-mcp-gateway",
"--config"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"irontrellis-gateway": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ramex-labs/irontrellis-mcp-gateway",
"--config"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
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 19, 2026
The registry name was verified with the GitHub account zerohourzulu, which owns the repo
Code last changed 7 days ago
Uses Apache-2.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for @ramex-labs/irontrellis-mcp-gateway@1.0.0-rc.2
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/zerohourzulu-irontrellis-gateway)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed 7 days ago, and the latest version (1.0.0-rc.2) reached the registry 20 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Irontrellis Gateway | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | Apache-2.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
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.
@ramex-labs/irontrellis-mcp-gateway 1.0.0-rc.2.3 puts the MCP tools you approve behind IronTrellis (formerly Continuity), which keeps a signed, replayable history of what each AI agent may do. Before a call reaches an upstream tool, the gateway checks the agent's current authority in that history (format 2); for exactly-once jobs and recorded calls, it also keeps the state of the attempt on disk. MCP client and server dependencies are pinned to 2.2.0.
An agent that calls its tools directly can act on authority that was taken away a minute ago, or send the same request twice after a lost reply. The gateway sits between your MCP client and the upstream MCP servers you approve, and handles these cases:
| What goes wrong | What the gateway does |
|---|---|
| A grant is revoked while the agent runs | It reads the history afresh on every call, so new work under that grant answers DENIED |
| A reply is lost and the agent asks again | An exactly-once job answers from its original attempt and never forwards it again |
| An upstream tool's definition changes | It compares the tool with the approved definition before each new admission or per-call forward, and refuses a mismatch (TOOL_CHANGED) |
Install from the next tag, or use a verified packed installation; the 1.0.0-rc.2 build is not claimed publicly released.
npm install -g @ramex-labs/irontrellis-mcp-gateway@next # provides irontrellis-mcp-gateway and irontrellis-mcp-ops
irontrellis-mcp-gateway setup /absolute/new-case # a private synthetic case; add --mode per-call for the other mode irontrellis-mcp-gateway --config /absolute/new-case/gateway.json # serves stdio: put this command in your MCP client's settings irontrellis-mcp-ops inspect --config /absolute/new-case/gateway.json irontrellis-mcp-ops revoke --config /absolute/new-case/gateway.json --authority write
setup creates a format-2 history with one worker agent, two local upstream servers (documents and tickets) and two jobs, read_incident and create_incident_ticket (two tools of the same names in per-call mode). The worker's grants and session expire after an hour. From your MCP client:
| You call | The gateway answers |
|---|---|
create_incident_ticket | RESPONSE_RETAINED: forwarded once, and the reply kept on disk |
create_incident_ticket again, with the same title | RECONCILIATION_ONLY: the retained reply; nothing is forwarded. A different title is refused (OPERATION_CONFLICT) |
create_incident_ticket after the revoke | RECONCILIATION_ONLY with its retained reply, because it already ran. Had it never run, it would answer DENIED: the write grant covers this job |
The server speaks stdio and waits for an MCP client. The setup is a disposable case with local credentials and synthetic tools. Protect its private directory and never reuse its credentials in production. An unknown outcome needs investigation of the original business key, not a new key to force a retry.
Exactly-once jobs, mode: "exactly-once" (the default) | Per-call tools, mode: "per-call" | |
|---|---|---|
| One operation is | A fixed tool and business key | One call |
| A repeat | Reconciles the original attempt and never deliberately forwards it again; changed arguments conflict | Is a new call, checked again |
| Every call checks | The job's fixed schema and current authority; a new admission also checks the approved tool definition | Current authority and the configured tool definition |
| Admitted as an intent in the history | Every job, once | Each call, only with recordCalls: true: set it when each call must be admitted and charged through the recorded path |
The profile name is not a guarantee of exactly-once effects inside an arbitrary upstream service. A query-only ALLOW is not a dispatch permit.
enforceFromReadOnlyHistory (set by hand) keeps enforcing from a never-migrated legacy or format-1 history read-only: every open warns, and it serves only calls that need no record: a call that must be recorded is refused (FORMAT_READ_ONLY with a remedy) before anything is dispatched. Migrate to write.
Keep the authenticated history ID/domain, agent, runtime session, signers, role/tenure, trusted clock, upstream executable, business mapping and storage outside agent control. A model supplies only the bounded business arguments permitted by the fixed schema. Retiring or revoking authority cannot undo an effect already sent.
| Subpath | Purpose |
|---|---|
| root | createGateway, gateway/server integration and public types |
/operations | Operator inspection, lease recovery, snapshots and revocation helpers |
/access-policy | Trusted access-policy configuration |
/server | MCP server integration |
/data | The bounded private-file and canonical-data helpers the anchor outbox shares (durableCreate, readPrivate, privateDirectory, …) |
| `/http` | serveGatewayHttp for loopback evaluation; serveGatewayRouter and serveGatewayBackend for the explicit router/backend profile |
| `/cooperative` | createCooperativeGateway, with run, status, recover, cancel and observe over a pinned cooperative destination |
| `/tasks` | createTaskManager and routeTaskRequest for io.modelcontextprotocol/tasks, bound to the configured cooperative gateway and caller identity |
| `/access-http` | createAccessVerifier, binding issuer, resource, keys and the fixed caller/tenant/revision mapping |
The four subpaths in bold are separate capabilities; importing one does not enable another or establish a secure public deployment. Public HTTPS deployment is not part of this release. Each subpath has its compiled runtime and declaration exports and a default export key.
The loopback HTTP helper is an evaluation profile. The router/backend profile requires its explicit TLS/mTLS configuration, pinned private peer, channel-bound assertions, nonce storage and independent bearer/Core checks. Trusted isActive and current-access guards must remain effective across asynchronous work. A token or authenticated transport is not native authority to perform an operation. HTTP and Tasks do not turn an uncertain effect into a new attempt.
A refusal decided by the history is returned with its recording status; a recording failure cannot turn a refusal into ALLOW. Core and budget refusals are distinguished from connector reports. Upstream effect or receipt fields are assertions under the connector/counterparty profile; replay does not prove an external business outcome. Replies retain externalOutcome: NOT_PROVEN where applicable.
| Result | Operator interpretation |
|---|---|
RESPONSE_RETAINED | An upstream reply was retained; inspect its error status and scope |
RECONCILIATION_ONLY | Original retained attempt, with no new forwarding |
OUTCOME_UNKNOWN | A dispatch start exists but the usable reply/outcome is not established |
DELAYED / NOT_DISPATCHED / STOPPED | Dispatch has not started (anchoring, or an admission without a start record); inspect the reason and, with anchoring, the resume horizon |
FORWARDED | Per-call forwarding occurred; inspect whether it was recorded |
DENIED / REFUSED | Read the decision and the bounded refusal reason; do not bypass it |
BUSY | Exclusion or a resource boundary prevents concurrent work |
Every message from the agent is checked before the MCP layer sees it: at most 16 KiB, strict JSON, and no more than 1,024 messages within any 60 seconds. A flood ends the gateway (INPUT_REFUSED); a long session of ordinary calls does not. Upstream servers are bounded the same way, and one that stops or floods is disconnected and started again, with its tool definition checked, on the next governed call to it.
Access is checked again after the attempt is durably retained and immediately before the call enters the upstream tool. A revocation at that point prevents the new effect, while an attempt already admitted keeps its uncertain state. No callback, old approval or retained result can replace that check.
Use operations, recovery and access-policy for operator procedures. Snapshot contents are sensitive; protect them as credentials/evidence until the chosen profile's exclusions are verified. Never clear a live lock or recovery journal to make a stuck operation run again.
Privileged hosts can configure the live anchoring barrier through the programmatic API. It retains an admitted request while waiting for eligible protected reports, checks a stop latch, and resumes only while no dispatch start exists. The CLI setup does not enable anchoring.
Know its limits in 1.0.0-rc.2. This build includes no qualified report producer, and nothing in it verifies a chain anchor: verifyAnchor returns no report, irontrellis verify takes none, and the diagnostic connector reports cannot release this barrier. A production-profile barrier therefore never opens unless an external producer supplies reports, and it takes the mode a report declares, CONSENSUS_VERIFIED included, on that producer's word. No consensus-verified anchoring is claimed; the separate tools used for the demonstration anchoring records report TRUSTED_NODE only, never consensus-verified.
The package's tests cover the real engine, crash and retry, transport, strict declarations and a packed install. The source tests are src/http-test.test.mjs, src/cooperative-test.test.mjs and src/http-twohop-test.test.mjs; the packed verifier is src/http-verify-install.py with the selected offline dependencies. These are the package's own tests; no separate review of the transport subpaths is claimed here.
This is not a hostile-code sandbox, distributed transaction manager, proof of downstream success or production chain/finality implementation. Upstreams share the configured host trust boundary. Cooperating destinations need their own checkpoint, fencing and deduplication contract. Whole-directory rollback, compromised administrators, a destination's unseen revocation and irreversible effects after dispatch remain distinct risks.
What the gateway records (admissions, refusals, effects, receipts) is signed with runtime session keys, not the owner key, so it stays unattested and unwitnessed until the next owner write; see operations. The attestation policy for PHL, Proof of Human Lineage (ATTESTED), ships in the 1.0.0-rc.2 core; transport test success does not establish every such policy combination.
Dependencies: @ramex-labs/irontrellis, @ramex-labs/irontrellis-remote, jose, @modelcontextprotocol/server and @modelcontextprotocol/client (jose 6.2.12 and the MCP SDK 2.2.0, pinned exactly). Apache-2.0.
*Last reviewed: 24 October 2026. This page is revisited at each release.*