Apifox Mcp Community MCP Server

apifox-mcp-community PyPI v3.0.3

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.

Trust grade
A
90/100
Last scanned
Trust
A · 90/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 98 − adoption risk = 90/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 − 2.1 = 98. What the published surface and source actually contain:

PointsWhat was foundCategory
−2.1 Package has no source repository MTC-SUP-011 supply-chain

2. Client adoption risk — 98 − 8 = 90. 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
−5 publisher verification (unlocatable) — no provenance and no public repository to inspect
inspection depth (source) — how much of the target the scan could see

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 1

low Package has no source repositoryMTC-SUP-011

"apifox-mcp-community" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package apifox-mcp-community

Tools 81

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

  • delete_environmentreads sensitive data
  • get_environment_detailreads sensitive data
  • list_environmentsreads sensitive data
  • activate_domainno sensitive capability
  • analyze_project_healthno sensitive capability
  • batch_callno sensitive capability
  • check_apifox_configno sensitive capability
  • create_api_folderno sensitive capability
  • create_custom_endpointno sensitive capability
  • create_docno sensitive capability
  • create_environmentno sensitive capability
  • create_global_paramno sensitive capability
  • create_http_apino sensitive capability
  • create_responseno sensitive capability
  • create_response_folderno sensitive capability
  • create_schemano sensitive capability
  • create_schema_folderno sensitive capability
  • create_test_caseno sensitive capability
  • create_test_scenariono sensitive capability
  • create_websocket_apino sensitive capability
  • deactivate_domainno sensitive capability
  • delete_api_folderno sensitive capability
  • delete_custom_endpointno sensitive capability
  • delete_docno sensitive capability
  • delete_http_apino sensitive capability
  • delete_responseno sensitive capability
  • delete_response_folderno sensitive capability
  • delete_schemano sensitive capability
  • delete_schema_folderno sensitive capability
  • delete_test_caseno sensitive capability
  • delete_test_scenariono sensitive capability
  • delete_websocket_apino sensitive capability
  • export_openapino sensitive capability
  • get_active_domainsno sensitive capability
  • get_api_folder_detailno sensitive capability
  • get_custom_endpoint_detailno sensitive capability
  • get_doc_detailno sensitive capability
  • get_global_variablesno sensitive capability
  • get_http_api_detailno sensitive capability
  • get_project_infono sensitive capability
  • get_response_folder_detailno sensitive capability
  • get_schema_detailno sensitive capability
  • get_schema_folder_detailno sensitive capability
  • get_test_case_detailno sensitive capability
  • get_test_report_detailno sensitive capability
  • get_test_scenario_detailno sensitive capability
  • get_test_scenario_stepsno sensitive capability
  • get_tool_summaryno sensitive capability
  • get_websocket_api_detailno sensitive capability
  • import_openapino sensitive capability
  • list_api_foldersno sensitive capability
  • list_custom_endpointsno sensitive capability
  • list_docsno sensitive capability
  • list_global_paramsno sensitive capability
  • list_http_apisno sensitive capability
  • list_response_foldersno sensitive capability
  • list_responsesno sensitive capability
  • list_schema_foldersno sensitive capability
  • list_schemasno sensitive capability
  • list_test_case_categoriesno sensitive capability
  • list_test_casesno sensitive capability
  • list_test_reportsno sensitive capability
  • list_test_scenario_treeno sensitive capability
  • list_tool_domainsno sensitive capability
  • list_websocket_apisno sensitive capability
  • scaffold_crud_moduleno sensitive capability
  • search_projectno sensitive capability
  • update_api_folderno sensitive capability
  • update_custom_endpointno sensitive capability
  • update_docno sensitive capability
  • update_environmentno sensitive capability
  • update_global_paramno sensitive capability
  • update_global_variablesno sensitive capability
  • update_http_apino sensitive capability
  • update_responseno sensitive capability
  • update_response_folderno sensitive capability
  • update_schemano sensitive capability
  • update_schema_folderno sensitive capability
  • update_test_caseno sensitive capability
  • update_test_scenariono sensitive capability
  • update_websocket_apino sensitive capability

What this scan could not see

Versions

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

Use the free API → How scoring works

More in Developer Tools