@verygoodplugins/mcp-freescout

MCPattested
v3.1.0Very Good PluginsGPL-3.0Updated 1mo agonpmGitHub

MCP server for FreeScout ticket management and workflow automation

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
325Downloads/wk
29GitHub stars
15Forks
1mo agoLast update
Needs 1 credential before it runs
  • FREESCOUT_API_KEYAPI keyrequired

    FreeScout API key with read/write permissions

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorVery Good Plugins
LicenseGPL-3.0
Version3.1.0
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 2a8100f
Dependencies✓ 4 resolved · none vulnerable
Tool surface8 tools · none privileged
Security scan✓ Cleanv3.0.1 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 15, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · none privileged
Statically extracted from the published packagev3.0.1 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

freescout_get_ticketNo description published

This tool published no description. Forge does not invent one.

freescout_analyze_ticketNo description published

This tool published no description. Forge does not invent one.

freescout_add_noteNo description published

This tool published no description. Forge does not invent one.

freescout_update_ticketNo description published

This tool published no description. Forge does not invent one.

freescout_create_draft_replyNo description published

This tool published no description. Forge does not invent one.

freescout_get_ticket_contextNo description published

This tool published no description. Forge does not invent one.

freescout_search_ticketsNo description published

This tool published no description. Forge does not invent one.

freescout_get_mailboxesNo description published

This tool published no description. Forge does not invent one.

0 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for FreeScout ticket management and workflow automation

Keywords
mcpmcp-servermodelcontextprotocolfreescouthelpdeskticket-managementworkflow-automation
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.