Kshana PNT-resilience simulator runs on your own machine — the client starts it, so there is no endpoint to ping. 300 installs a week from npm. Last commit 8 Nov 2026.
Validated Kshana PNT simulator: orbits, GNSS, fusion, receiver trust, interference maps.
We read the source, 6 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
return subprocess.call([str(binary), *args])
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
cn0_drop_db: cn0_drop + z(&mut rng, nm * 0.3),
out = os.path.join(OUT_DIR, f"{name}.hgt")
const k = spawn(bin, ['receiver-trust', 'live', session, '--gate', '--listen', `tcp:${port}`, '--replay'], {
vm.runInNewContext(mapText, sandbox);
pub const LEGENDRE_10223_HEX: &str = "3DE552ECC61973C3E2F82F06D61DE035F019FD80BB7682DB6CD2A76F7A289CEDFC82058F75C78883BD16FCD100B9CF36794B64313A5EF97E5FB299038FE3F9CFDFEB2210A2C729DCFE6D6A750BA328159DEEACF17D6BC42C2A2395A5637E3472FDAC6394D0C8148E1FB0EDF95F865FF2C5D794332704089F29…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add kshana-mcp -- uvx kshana-mcp
{
"mcpServers": {
"kshana-mcp": {
"command": "uvx",
"args": [
"kshana-mcp"
]
}
}
}
[mcp_servers.kshana-mcp]
command = "uvx"
args = ["kshana-mcp"]
{
"mcpServers": {
"kshana-mcp": {
"command": "uvx",
"args": [
"kshana-mcp"
]
}
}
}
{
"servers": {
"kshana-mcp": {
"type": "stdio",
"command": "uvx",
"args": [
"kshana-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
KSHANA_MCP_IQ_DIR (Folder the GNSS IQ tools (iq_scene, iq_acquire, iq_track, iq_frontend, iq_info, iq_campaign, iq_campaign_status) may read and write; every IQ path argument is relative to it. Unset leaves the IQ file tools off; the other tools are unaffected. In a container, mount a volume and point this at it), KSHANA_MCP_IQ_MAX_SAMPLES (Most complex samples one IQ call may generate or process (default 50000000)).
Adaptive WebRTC jitter buffer simulation and inter-arrival jitter telemetry
Verifiable receipts for governed process changes; emit, validate, and gate trust
Compiles source-agent outputs into validated, receiver-ready handoff packages.
Physics-based validation of simulation results: receipts with per-check verdicts, via MCP.
Version-true web3 docs, ABIs and human-validated integration recipes over MCP.
Korean business record validation and workflow safety gates for AI agents.
Cloud PLC simulator: validate and step-run LAD/SCL programs, run scenarios, return PASS/FAIL.
Paid x402 API and MCP for trusted public master data, golden records, and reference data.
Answers built from our own checks of this server.