Feedme Html Publisher MCP Server

feedme-html-publisher-mcp npm v1.2.1

Published by feedme-org — 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 pra criar e operar projetos do CRM da Rede FeedMe (projetos, equipe, tarefas, financeiro e publicação de HTML) direto do Claude Code, sem precisar de acesso ao código.

Trust grade
A
90/100
Last scanned get badge →
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 94 − 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 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Description names a credential store the tool cannot reach MTC-INJ-SCHEMA-1 injection

2. Client adoption risk — 94 − 4 = 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
−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 5

medium Description names a credential store the tool cannot reachMTC-INJ-SCHEMA-1

Tool "logout" describes a credential store (SSH keys, cloud credentials, a keychain or an equivalent) that nothing in its input schema can address. A tool's interface is the honest statement of what it touches; prose that reaches past it is addressed to the model, not to a reader.

Evidence: Keychain

Fix: Remove the reference, or expose the target as an explicit, validated parameter so the client can see and consent to what the tool reads.

Location: tool logout · description

medium Tool "unlink_person" can modify the filesystemMTC-CAP-002

Tool "unlink_person" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_person

medium Tool "unlink_company" can modify the filesystemMTC-CAP-002

Tool "unlink_company" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool unlink_company

low Mutating tool "unlink_person" declares no destructiveHintMTC-CAP-005

Tool "unlink_person" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_person

low Mutating tool "unlink_company" declares no destructiveHintMTC-CAP-005

Tool "unlink_company" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool unlink_company

Tools 37

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

  • unlink_companywrites files
  • unlink_personwrites files
  • clone_projectno sensitive capability
  • create_expenseno sensitive capability
  • create_projectno sensitive capability
  • create_revenueno sensitive capability
  • create_taskno sensitive capability
  • delete_expenseno sensitive capability
  • delete_projectno sensitive capability
  • delete_revenueno sensitive capability
Show 27 more tools ↓
  • delete_taskno sensitive capability
  • finance_summaryno sensitive capability
  • find_companyno sensitive capability
  • find_personno sensitive capability
  • find_studio_associateno sensitive capability
  • get_projectno sensitive capability
  • get_studio_associateno sensitive capability
  • link_companyno sensitive capability
  • link_personno sensitive capability
  • list_expensesno sensitive capability
  • list_finance_categoriesno sensitive capability
  • list_project_documentsno sensitive capability
  • list_projectsno sensitive capability
  • list_revenuesno sensitive capability
  • list_tasksno sensitive capability
  • loginno sensitive capability
  • logoutno sensitive capability
  • publish_htmlno sensitive capability
  • restore_versionno sensitive capability
  • update_expenseno sensitive capability
  • update_person_roleno sensitive capability
  • update_projectno sensitive capability
  • update_revenueno sensitive capability
  • update_taskno sensitive capability
  • view_current_htmlno sensitive capability
  • view_versionsno sensitive capability
  • whoamino 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
v1.2.1 latest A 90/100 5 1.13.0 2026-09-07

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

Use the free API → How scoring works

More in Business & CRM