Refua MCP Server

refua-mcp PyPI v0.8.0

Published by agentcures — 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.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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.
A Why this grade threat 100 − adoption risk = 96/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 − 4 = 96. 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
−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 42

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

  • refua_data_fetchingests untrusted input
  • refua_admet_profileno sensitive capability
  • refua_affinityno sensitive capability
  • refua_antibody_designno sensitive capability
  • refua_bench_baselineno sensitive capability
  • refua_bench_compareno sensitive capability
  • refua_bench_gateno sensitive capability
  • refua_bench_initno sensitive capability
  • refua_bench_runno sensitive capability
  • refua_clinical_simulatorno sensitive capability
Show 32 more tools ↓
  • refua_data_listno sensitive capability
  • refua_data_materializeno sensitive capability
  • refua_data_queryno sensitive capability
  • refua_data_validate_sourcesno sensitive capability
  • refua_deploy_planno sensitive capability
  • refua_deploy_renderno sensitive capability
  • refua_foldno sensitive capability
  • refua_jobno sensitive capability
  • refua_preclinical_batch_recordno sensitive capability
  • refua_preclinical_bioanalysisno sensitive capability
  • refua_preclinical_cmc_planno sensitive capability
  • refua_preclinical_cmc_templatesno sensitive capability
  • refua_preclinical_planno sensitive capability
  • refua_preclinical_release_assessno sensitive capability
  • refua_preclinical_scheduleno sensitive capability
  • refua_preclinical_stability_assessno sensitive capability
  • refua_preclinical_stability_planno sensitive capability
  • refua_preclinical_templatesno sensitive capability
  • refua_preclinical_workupno sensitive capability
  • refua_protein_propertiesno sensitive capability
  • refua_regulatory_bundleno sensitive capability
  • refua_regulatory_checklistno sensitive capability
  • refua_regulatory_summaryno sensitive capability
  • refua_regulatory_verifyno sensitive capability
  • refua_validate_specno sensitive capability
  • refua_wetlab_compile_protocolno sensitive capability
  • refua_wetlab_lms_getno sensitive capability
  • refua_wetlab_lms_postno sensitive capability
  • refua_wetlab_providersno sensitive capability
  • refua_wetlab_run_protocolno sensitive capability
  • refua_wetlab_run_statusno sensitive capability
  • refua_wetlab_validate_protocolno 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
v0.8.0 latest A 96/100 0 1.8.0 2026-07-23

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

Use the free API → How scoring works

More in Learning & Documentation