Caveat verdict

tempo-api-mcp

88
๐ŸŸข Trusted
No high-risk patterns surfaced by the deep scan โ€” automated capability review, not behavioral proof.

Standard MCP server wrapper for the Tempo time-tracking API using a user-supplied API token; behavior matches stated purpose of time tracking and worklog management.

โš  Flagged for review โ€” coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis โ€” not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

95
security
70
transparency
70
maintenance

Permission integrity

Installs packages at runtime โ€” transitive dependencies are not auditable

package_install

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class B). Final tier capped at Caution โ€” cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions โ€” minimal attack surface.

network_inpackage_install

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API