Agileconfig MCP Server
agileconfig-mcp-server
npm
v1.0.1
Published by animacaeli — 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.
MCP Server for AgileConfig - 将 AgileConfig 配置中心的 RESTful API 暴露为 MCP 工具，让 AI 助手直接管理配置
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:
| Points | Adoption-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
Tools 45
Each tool and what it can reach — statically extracted from the published source.
agileconfig_create_appreads sensitive dataagileconfig_update_appreads sensitive dataagileconfig_add_nodeno sensitive capabilityagileconfig_change_passwordno sensitive capabilityagileconfig_create_configno sensitive capabilityagileconfig_create_userno sensitive capabilityagileconfig_delete_appno sensitive capabilityagileconfig_delete_configno sensitive capabilityagileconfig_delete_nodeno sensitive capabilityagileconfig_delete_userno sensitive capability
Show 35 more tools ↓
agileconfig_deployno sensitive capabilityagileconfig_disconnect_clientno sensitive capabilityagileconfig_get_all_configsno sensitive capabilityagileconfig_get_appno sensitive capabilityagileconfig_get_configno sensitive capabilityagileconfig_get_publish_historyno sensitive capabilityagileconfig_get_published_configsno sensitive capabilityagileconfig_get_settingsno sensitive capabilityagileconfig_get_syslogsno sensitive capabilityagileconfig_get_userno sensitive capabilityagileconfig_get_user_permissionsno sensitive capabilityagileconfig_inspectno sensitive capabilityagileconfig_list_appsno sensitive capabilityagileconfig_list_clientsno sensitive capabilityagileconfig_list_nodesno sensitive capabilityagileconfig_list_servicesno sensitive capabilityagileconfig_list_usersno sensitive capabilityagileconfig_offline_configno sensitive capabilityagileconfig_onboard_userno sensitive capabilityagileconfig_publish_configno sensitive capabilityagileconfig_publish_single_configno sensitive capabilityagileconfig_register_serviceno sensitive capabilityagileconfig_rollback_configno sensitive capabilityagileconfig_set_user_permissionsno sensitive capabilityagileconfig_sync_envno sensitive capabilityagileconfig_unregister_serviceno sensitive capabilityagileconfig_update_configno sensitive capabilityagileconfig_update_settingsno sensitive capabilityagileconfig_update_userno sensitive capabilityagileconfig_user_loginno sensitive capabilityappIdno sensitive capabilityenvno sensitive capabilitysourceEnvno sensitive capabilitytargetEnvno sensitive capabilityuserNameno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (45 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.1 latest |
A 96/100 | 0 | 1.13.0 | 2026-09-09 |
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.
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 agileconfig-mcp-server --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Generates production-ready UI components from natural language, inspired by v0.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.