CanopiiCanopiiAll serversEnterprise →
io.github.paivapiovesan/next-finance

io.github.paivapiovesan/next-finance v0.9.133

Security Trust Score
Grade B · Moderate posture
Tier 1 · Public sourceHigh confidence · 91%
Declared MCP capabilities
ResourcesPrompts

Host io.github.paivapiovesan/next-finance in a governed environment — SSO in front, every tool call attributed and audited.

Reputation7.4kdownloads/mo

Security controls

Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Warn
    Strict JSON Schema Enforcementschemas not strict

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

    Fix: Set additionalProperties:false and require explicit parameters on every tool.

  • Warn
    Tool Definition Integrityguard1 tool description(s) drifted after publish (no risk signals in diff)

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

    listar_plano_de_contas

    Fix: Never add hidden directives or destructive scope to an already-published tool; document description changes in release notes.

  • Pass
    Indirect Prompt Injection (IPI) Defensesguardno injection markers

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

  • Pass
    User-in-the-Loop / Approval Scopeguardno destructive tool scope

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

Application Security Checks

  • Warn
    Dependencies pinned (lockfile)no lockfile found

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

    Fix: Commit a lockfile (package-lock.json / pnpm-lock.yaml / poetry.lock).

  • Warn
    Published with provenanceno provenance attestation

    Build provenance attests the artifact was built from the claimed source by CI.

    Fix: Publish with npm provenance (--provenance) from a trusted CI.

  • Warn
    Established maintainersingle maintainer

    Brand-new / single anonymous maintainers raise takeover and malware risk.

    Fix: Publish under an established account/org; add multiple maintainers.

  • Warn
    Has a security policyno security policy

    A SECURITY.md gives a private path to report vulnerabilities.

    Fix: Add SECURITY.md with a disclosure contact and process.

  • Pass
    No command-injection sinksguardno sinks found

    Untrusted tool input reaching a shell yields remote code execution.

  • Pass
    No dynamic code executionguardno sinks found

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

  • Pass
    No path traversalguardno sinks found

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

  • Pass
    No SSRF sinksguardno sinks found

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

  • Pass
    No unsafe deserializationguardno sinks found

    pickle/yaml.load/etc. on untrusted data can execute code.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    No known-vulnerable dependencies1 runtime deps, no known CVEs

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

  • Pass
    No install/post-install scriptsguardno install scripts

    install hooks run arbitrary code on every consumer at install time.

  • Pass
    Package name not typosquattingguarddistinct package name

    Names mimicking popular packages are a common malware delivery vector.

  • Pass
    Adoption & popularityestablished adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

  • Not checked
    Actively maintainedGitHub API unavailable

    Unmaintained servers don't receive security fixes.

  • Not checked
    Repository not archivedguardGitHub API unavailable

    Archived repositories will never be patched.

  • Not checked
    Declares a licenseGitHub API unavailable

    A clear license is required for legal enterprise use.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

Transport & Trust Model

  • Warn
    Execution Sandboxingruns natively (no container image)

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

    Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.

  • Pass
    Network Exposureno bind-all detected

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

  • N/A
    Transport Encryption (TLS)guardno remote endpoints

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • N/A
    IAM / Authentication Scopingno remote endpoints

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Tools (80)

loginlogoutversaocriar_contacriar_contatolistar_contaslistar_moedasbaixar_a_pagarbuscar_contatocriar_carteiracriar_contratocriar_propostasaldo_carteirabuscar_despesasconsultar_saldolistar_clienteslistar_contatospermissao_contabaixar_a_recebercriar_lancamentolistar_carteiraslistar_contratosresumo_categoriacalcular_reajustedetalhar_contratoeditar_lancamentobuscar_lancamentoscorrigir_cnpj_raizexcluir_lancamentolistar_tipos_contareajustar_contratocriar_transferencialistar_conciliacoesselecionar_carteiraassociar_conciliacaobuscar_itens_despesadetalhar_conciliacaoenviar_para_cobrancaexecutar_conciliacaoimportar_extrato_apilistar_inadimplentesultimo_preco_produtobuscar_contas_a_pagarconectar_open_financecriar_centro_de_custocriar_plano_de_contasenviar_email_cobrancareiniciar_conciliacaoatualizar_open_financebuscar_compras_produtolistar_plano_de_contasresumo_centro_de_custoverificar_open_financebuscar_contas_a_receberiniciar_open_finance_qrlistar_centros_de_custolistar_contas_correnteslistar_modelos_propostalistar_pj_sem_cnpj_raizlistar_anexos_lancamentoremover_anexo_lancamentoanexar_arquivo_lancamentobuscar_despesas_periodicasbuscar_receitas_periodicasgerar_faturamento_contratolistar_classes_de_cadastrolistar_contas_open_financelistar_documentos_emitidosobter_extrato_open_financeadicionar_filial_fornecedorassociar_conta_open_financeconferir_previsto_realizadoimportar_documento_recebidolistar_documentos_recebidoscadastrar_documento_recebidocriar_registro_relacionamentoclassificar_documento_recebidodesassociar_conta_open_financesubstituir_previsao_por_boletolistar_contas_do_item_open_finance

AI-flagged — for review

Observations from an AI review of tool descriptions. These are advisory only and do not affect the score — they can be noisy and need human judgement.

  • info
    Tool "listar_plano_de_contas" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.