Fio MCP Server

fio-mcp npm v1.0.0

Published by themanwithanrx7 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A Model Context Protocol server for FIO / Prosperous Universe

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 41

Each tool and what it can reach — statically extracted from the published source.

  • fio_get_all_buildingsno sensitive capability
  • fio_get_all_exchangesno sensitive capability
  • fio_get_all_materialsno sensitive capability
  • fio_get_all_planetsno sensitive capability
  • fio_get_all_recipesno sensitive capability
  • fio_get_all_systemsno sensitive capability
  • fio_get_buildingno sensitive capability
  • fio_get_burn_rateno sensitive capability
  • fio_get_company_local_marketno sensitive capability
  • fio_get_contract_concernsno sensitive capability
Show 31 more tools ↓
  • fio_get_contract_shipmentsno sensitive capability
  • fio_get_contractsno sensitive capability
  • fio_get_exchangeno sensitive capability
  • fio_get_exchange_fullno sensitive capability
  • fio_get_exchange_ordersno sensitive capability
  • fio_get_exchange_tradesno sensitive capability
  • fio_get_exchange_trades_csvno sensitive capability
  • fio_get_infrastructureno sensitive capability
  • fio_get_jump_countno sensitive capability
  • fio_get_jump_routeno sensitive capability
  • fio_get_local_marketno sensitive capability
  • fio_get_materialno sensitive capability
  • fio_get_materials_by_categoryno sensitive capability
  • fio_get_planetno sensitive capability
  • fio_get_planet_sitesno sensitive capability
  • fio_get_price_historyno sensitive capability
  • fio_get_productionno sensitive capability
  • fio_get_production_on_planetno sensitive capability
  • fio_get_ship_flightsno sensitive capability
  • fio_get_ship_fuelno sensitive capability
  • fio_get_shipsno sensitive capability
  • fio_get_sitesno sensitive capability
  • fio_get_storageno sensitive capability
  • fio_get_storage_on_planetno sensitive capability
  • fio_get_systemno sensitive capability
  • fio_get_userno sensitive capability
  • fio_get_workforceno sensitive capability
  • fio_get_workforce_needsno sensitive capability
  • fio_get_workforce_on_planetno sensitive capability
  • fio_search_local_marketno sensitive capability
  • fio_search_planetsno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest A 99/100 0 1.12.1 2026-07-28

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/fio-mcp/badge.svg)](https://mcptrustchecker.com/registry/fio-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/fio-mcp"><img src="https://mcptrustchecker.com/registry/fio-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/fio-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan fio-mcp --online

Use the free API → How scoring works

More in Gaming & Entertainment