Skills/npm/tempo-mcp-server

tempo-mcp-server@1.8.0

CAUTION

Publisher claims: "MCP server for managing Tempo worklogs in Jira" Observed in sandbox: static analysis only — behavior not yet observed.

Registry npm (MCP server)Publisher ivelin-web · joined 0 days agoInstalls 538Last detonated 1 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-27 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Authorization escalation language; Prompt injection. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

HIGH
Authorization escalation languageREADME.md:49 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
CRITICAL
Prompt injectionREADME.md:49 · Prompt injection — known jailbreak technique referenceFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST01

What would make this Verified

10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim ivelin-web: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim ivelin-web