@framedash/mcp-server

MCPattested
v0.1.4io.github.crane-valleyUnknownUpdated 16d agonpmGitHub

MCP server for Framedash game telemetry: query analytics, heatmaps, perf regressions, and alerts

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.
16d agoLast update
Needs 1 credential before it runs
  • FRAMEDASH_API_KEYAPI keyrequired

    Framedash API key. Create one on your project's API Keys page at https://app.framedash.dev.

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
Authorio.github.crane-valley
LicenseUnknown
Version0.1.4
Sourcenpm+mcp-registry
npm@framedash/mcp-server
GitHubcrane-valley/framedash-mcp-server
SBOMCycloneDX 1.6 ↓
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 · ed35be8
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · none privileged
Security scan✓ Cleanv0.1.3 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 17, 2026

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

Tools

12 tools · none privileged
Statically extracted from the published packagev0.1.3 · 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.

list_alertsNo description published

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

get_alert_historyNo description published

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

get_dashboardNo description published

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

get_retentionNo description published

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

get_funnelNo description published

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

get_insightsNo description published

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

get_heatmapNo description published

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

list_projectsNo description published

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

get_project_statusNo description published

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

list_mapsNo description published

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

list_contentNo description published

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

queryNo description published

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

0 of 12 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 Framedash game telemetry: query analytics, heatmaps, perf regressions, and alerts

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

12 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

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