Frameworkqa MCP Server

frameworkqa-mcp npm v6.6.0

Published by brunoalz — 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 v6 — ferramentas consolidadas por domínio (fluxos_query, fluxo_relacionamentos, arquivar_fluxo, passos_query, passos_base_batch) + auth sliding window (access 7d + refresh 30d com rotacao) via /api/mcp/auth/*

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 42

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

  • arquivar_fluxono sensitive capability
  • atualizar_bugno sensitive capability
  • atualizar_fluxono sensitive capability
  • atualizar_ocorrenciano sensitive capability
  • busca_globalno sensitive capability
  • buscar_bugs_similaresno sensitive capability
  • componentes_batchno sensitive capability
  • criar_bugno sensitive capability
  • criar_fluxono sensitive capability
  • criar_ocorrencia_em_bugno sensitive capability
Show 32 more tools ↓
  • desvincular_bug_passo_baseno sensitive capability
  • execucoes_queryno sensitive capability
  • fechar_ocorrenciano sensitive capability
  • fluxo_relacionamentosno sensitive capability
  • fluxos_queryno sensitive capability
  • listar_bugs_telano sensitive capability
  • listar_lookupsno sensitive capability
  • loginno sensitive capability
  • login_tokenno sensitive capability
  • logoutno sensitive capability
  • modulos_batchno sensitive capability
  • navegacao_queryno sensitive capability
  • notas_batchno sensitive capability
  • obter_bugno sensitive capability
  • obter_componenteno sensitive capability
  • obter_documentacao_setupno sensitive capability
  • obter_ocorrenciano sensitive capability
  • obter_suiteno sensitive capability
  • obter_tela_completano sensitive capability
  • passo_imagemno sensitive capability
  • passos_base_batchno sensitive capability
  • passos_fluxo_batchno sensitive capability
  • passos_queryno sensitive capability
  • planos_opno sensitive capability
  • planos_queryno sensitive capability
  • reabrir_ocorrenciano sensitive capability
  • relacionamentos_componente_batchno sensitive capability
  • sistemas_batchno sensitive capability
  • statusno sensitive capability
  • telas_batchno sensitive capability
  • validacoes_batchno sensitive capability
  • vincular_bug_passo_baseno 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
v6.6.0 latest A 99/100 0 1.13.0 2026-09-07
v6.5.2 A 99/100 0 1.12.1 2026-08-03
v6.5.0 A 99/100 0 1.12.1 2026-07-29

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

Use the free API → How scoring works

More in Security & Testing