Bios MCP Server

bios-mcp npm v0.2.1

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

BIOS MCP server — train and deploy AI models from MCP-compatible automation clients

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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
Moderate
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 = 95/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 − 5 = 95. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 42

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

  • get_checkpoint_download_manifestingests untrusted input
  • get_training_checkpointsingests untrusted input
  • chat_with_inferenceno sensitive capability
  • create_inferenceno sensitive capability
  • create_training_jobno sensitive capability
  • delete_datasetno sensitive capability
  • delete_inferenceno sensitive capability
  • delete_training_checkpointno sensitive capability
  • get_gpu_pricingno sensitive capability
  • get_inference_bookingno sensitive capability
Show 32 more tools ↓
  • get_inference_gpu_optionsno sensitive capability
  • get_inference_metricsno sensitive capability
  • get_inference_notificationsno sensitive capability
  • get_inference_statusno sensitive capability
  • get_model_configno sensitive capability
  • get_platform_guideno sensitive capability
  • get_recommended_gpuno sensitive capability
  • get_training_capabilitiesno sensitive capability
  • get_training_evalsno sensitive capability
  • get_training_logsno sensitive capability
  • get_training_metricsno sensitive capability
  • get_training_statusno sensitive capability
  • get_wallet_balanceno sensitive capability
  • import_huggingface_datasetno sensitive capability
  • introspect_api_keyno sensitive capability
  • list_datasetsno sensitive capability
  • list_inferencesno sensitive capability
  • list_integrationsno sensitive capability
  • list_modelsno sensitive capability
  • list_supported_architecturesno sensitive capability
  • list_training_jobsno sensitive capability
  • preflight_inferenceno sensitive capability
  • preflight_training_jobno sensitive capability
  • preview_datasetno sensitive capability
  • restart_inferenceno sensitive capability
  • resume_inferenceno sensitive capability
  • resume_training_jobno sensitive capability
  • search_modelsno sensitive capability
  • stop_inferenceno sensitive capability
  • stop_training_jobno sensitive capability
  • update_inference_policyno sensitive capability
  • upload_datasetno sensitive capability

What this scan could not see

Versions 3

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
v0.2.1 latest A 95/100 0 1.13.0 2026-09-07
v0.2.0 B 87/100 0 1.12.1 2026-07-29
v0.1.1 B 87/100 0 1.12.1 2026-07-27

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/bios-mcp/badge.svg)](https://mcptrustchecker.com/registry/bios-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/bios-mcp"><img src="https://mcptrustchecker.com/registry/bios-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bios-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 bios-mcp --online

Use the free API → How scoring works

More in Data Science & ML