io.sparkletree/sparkletree

MCPcommunitylive
v1.0.2io.sparkletreeUnknownUpdated 19d ago

Create, publish and measure SparkleTree marketing campaigns from an AI client. OAuth 2.1 with PKCE.

Endpoint healthlive
checked 7 days ago · 341ms · auth required
100% of the last 4 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

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

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
19d agoLast update
Package
Authorio.sparkletree
LicenseUnknown
Version1.0.2
Sourcemcp-registry
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: this listing has no repository on file, so `forge publish` cannot verify ownership automatically. Use "Claim this listing" above — Forge reviews these by hand.
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · todayHow well does this scan work?
EvalsNone
IndexedSep 2, 2026

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

Tools

Source not readable7h ago

The repository archive could not be read at scan time (tarball fetch returned 406), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Create, publish and measure SparkleTree marketing campaigns from an AI client. OAuth 2.1 with PKCE.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.