MCP Registry

@iflow-mcp/the-focus-ai-mastodon-mcp

a8d2b286-135f-5a1a-a67e-2b2f93cf1ba3 | Store v1.0.0
79/ 100
HIGH risk
Risk verdict
Review before use

Score-based assessment (high risk, 79/100). An AI review is available in the AI review tab.

Analysis record

Analysed
2 months ago 26 August 2026
Version
v1.0.0
Artifact
SHA256 e5b9309a…5a0d3b
Detail
Full list

Evidence ledger

Ranked by severity · findings with a source location link to the code viewer

44 findings

YARA Rule Matches

8 rules
SeverityRuleHitsFilesMetadata
LOWcredential env files 2
src/config.tsdist/config.js
-
LOWpostinstall persistence mechanism 9
dist/api.jssrc/api.tsdist/mastodon_types.d.ts +6 more
-
LOWpostinstall obfuscation 1
WARP.md
-
LOWpostinstall environment access 7
src/config.tsdist/api.jsdist/api.d.ts +4 more
-
LOWpostinstall crypto operations 5
src/mastodon_types.tssrc/mastodon_tool.tsdist/mastodon_tool.js +2 more
-
LOWpostinstall network communication 3
LICENSEdist/mcp-server.jssrc/mcp-server.ts
-
LOWpostinstall system command 4
src/config.tsWARP.mdREADME.md +1 more
-
LOWpostinstall file download 5
dist/api.jsWARP.mddist/mastodon_tool.js +2 more
-

Finding Categories

2
Secrets
6
Network
4
IoC Indicators

YARA Rules Matched

8 rules(36 hits)
credential env files postinstall persistence mechanism postinstall obfuscation postinstall environment access postinstall crypto operations postinstall network communication postinstall system command postinstall file download

MCP Server Analysis

MCP servers expose tools and resources to AI assistants. Unlike browser extensions, they run as standalone processes with direct system access. Tool definitions are analyzed for prompt injection, data exfiltration, and tool poisoning patterns.

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality weak.

This package presents a Critical risk score of 100 based on findings summaries, but the available evidence suggests this is likely a detection artifact rather than a genuine threat. The findings are concentrated in IoCs (26) and malware signatures (36), which are well-documented sources of noise in MCP analysis where bundled dependencies inflate scan counts. Notably absent are any findings related to the defining MCP threats: there are zero indicators of tool poisoning, zero secret/credential access findings, and zero network findings flagged.

The combination of high IoC/malware signature counts alongside zero tool-poisoning or credential-access flags typically indicates a benign package triggering generic YARA rules on bundled code or standard libraries. Without specific evidence of hidden AI directives, environment variable exfiltration, or suspicious network destinations, the Critical categorization appears unwarranted. This is likely a false positive driven by score inflation from non-specific rule matches.

Key Reasons

  • Zero tool-poisoning findings detected (primary MCP threat absent)
  • Zero credential or secret access findings (exfiltration architecture absent)
  • IoC and malware-signature counts consistent with bundled dependency noise
  • No network findings flagged to corroborate exfiltration claims

False Positive Considerations

  • IoC Extractor Garbage (high counts from generic hex strings or bundled modules)
  • YARA Code-Smell Rules (malware signatures firing on standard minified JS)
  • Score Inflation (high risk score driven by volume of low-fidelity findings)

Reviewed 2026-04-12; recommended action: suppress false positive; model confidence 60%.

Source Code Viewer

Source Code Not Available

Source code is not available for this version of the extension.

About This Extension

MCP server for Mastodon integration

Frequently Asked Questions