MCP.Market

Prism — Crossdeck MCP server

not responding
by cross-deck.com·com.cross-deck/prism·v0.4.0

Ask your app anything — revenue, errors, read-cost, growth — and get rendered charts back.

C60/100grade C
What users say
No reviews yet
Be the first
Safety scan
C60/100

full report

Adoption
Growing

0 stars80 downloads/wk

Reviews

Write one

Nobody has reviewed Prism — Crossdeck yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Prism — Crossdeck tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it

1 high
  • Code scan7 source files scanned25/25
  • Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: <html><head> <meta http-equiv="content-type" content="text/html;charset=utf-8"> <title>404 Page not found</title> </head> <body text=#000000 bgcolor=0/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 63 days ago12/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (1)

  • highRemote endpoint did not respondreliability.unreachable

    Streamable HTTP error: Error POSTing to endpoint: <html><head> <meta http-equiv="content-type" content="text/html;charset=utf-8"> <title>404 Page not found</title> </head> <body text=#000000 bgcolor=

Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Prism — Crossdeck compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
60/100
higher than 15% of 48,243 servers
Uptime
75%
of our recent checks; the typical remote server answers 100%
Response time
189 ms
faster than 68% of 30,027 servers
Downloads a week
80
more than 57% of 12,306 servers with a package

Install Prism — Crossdeck in Claude Code, Cursor or VS Code

claude mcp add --transport http prism https://api.cross-deck.com/mcp
Add to Cursor

What the publisher says

From the Prism — Crossdeck repository's README, as published. We do not edit it. Read it on GitHub

Prism — Crossdeck's intelligence layer for AI

Ask your app anything — revenue, errors, database read-cost, growth — in plain English, and get rendered charts and dashboards back.

"Which paying customer did this crash hit, and how much revenue is at risk?" — one question, answered across error, identity, and revenue. No single-layer tool can do that.

What Prism does → · Developer docs · Crossdeck

Why Prism is different

Most MCP servers are a connector to one system. Prism is an intelligence layer over your whole app — because Crossdeck already joins the layers about your users (identity · revenue · entitlements · errors · analytics · database read-cost) into one source of truth, by identity.

The point isn't "let AI read my data." It's the crossing: one question can span layers no other tool joins —

"This error a1b2c3 — who did it hit, and how many of them pay us?"

→ the named paying users behind the crash, each with their monthly revenue at risk, sorted by what's on the line.

That's the moat sentence. Prism gives it a voice in Claude, ChatGPT, Cursor, or any MCP client.

Permissions & data access

Secure, read-only access to your live Crossdeck workspace. Prism reads; it never writes.

Prism can see (the layers Crossdeck already owns about your app):

Row-level customer identity is returned only when your connection was explicitly granted that scope — otherwise Prism answers from aggregates and tells you so. That boundary is enforced by Crossdeck, not left to the model.

Prism cannot create, modify, delete, or configure anything in your projects. There is no write path — every tool is read-only (readOnlyHint: true). Ask it to change something and it will tell you it can't.

Data is fetched live at question time over an OAuth-protected endpoint; the connector stores nothing.

Connect in 60 seconds

Remote (recommended) — one-click OAuth, no keys to paste

Prism is a hosted, OAuth-protected MCP endpoint:

https://api.cross-deck.com/mcp

Add it as a connector in your client, sign in with your Crossdeck account, pick a project, and approve. That's it — the client receives a short-lived, scoped workspace credential automatically.

  • Claude (web / desktop): Settings → Connectors → Add custom connector → paste the URL above.
  • ChatGPT: Settings → Connectors → Add → paste the URL.
  • Cursor: Settings → MCP → Add → paste the URL.

Or open your dashboard at app.cross-deck.com → Developers → Prism → Connect AI for one-click "Add to Claude / ChatGPT / Cursor".

Local (Claude Desktop / Cursor / Claude Code) — stdio + a secret key

No install step — npx fetches the package and its dependencies on each launch, so it self-heals and stays current (nothing local to go stale):

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-04downgradeA → Cscore 60: Remote endpoint did not respond

Prism — Crossdeck: common questions

Is Prism — Crossdeck MCP server safe?
With care: it is graded C, so read the findings first (60/100). Read the Prism — Crossdeck safety report
How do I install Prism — Crossdeck?
It runs remotely at api.cross-deck.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Prism — Crossdeck need an API key?
Yes. The registry entry asks for CROSSDECK_SECRET_KEY.
Is Prism — Crossdeck maintained?
The last commit was 64 days ago (2026-09-02). The latest release is v0.4.0.
Is Prism — Crossdeck up?
75% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Prism — Crossdeck compare with other MCP servers?
safety score 60/100 (higher than 15% of 48,243 servers); uptime 75% (of our recent checks; the typical remote server answers 100%); response time 189 ms (faster than 68% of 30,027 servers). Full comparison.