Other · Remote MCP server
Prismism
Upload any file, get a tracked shareable link. DocSend for AI agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.prismism/mcp- Version
- 0.2.2
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-03-13
- Updated
- 2026-03-13
- Publisher
- dev.prismism
- Namespace
- Namespace verified by the MCP Registry via the domain prismism.dev · how
- Website
- prismism.dev
- Repository
- github.com/prismism-dev/mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://prismism.dev/mcp | x-api-key (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @prismism/mcp-server | 0.2.2 | stdio |
How to connect Prismism
Prismism is a remote MCP server: there is nothing to install. Its endpoint is https://prismism.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: x-api-key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @prismism/mcp-server version 0.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @prismism/mcp-server@0.2.2.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@prismism/mcp-server@0.2.2"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| PrismLocal-first repo intelligence for agents: DNA, health, blast radius, and Dispatch jobs. | Local · stdio |
| Prism - CrossdeckAsk your app anything - revenue, errors, read-cost, growth - and get rendered charts back. | Remote & Local · HTTP, stdioLive check: sign-in required |
| prismAId MCPMCP server for prismAId AI-assisted systematic reviews and protocol conformance checking. | Local · stdio |
| PrismHR MCPOpen-source MCP server for PrismHR. PEO workflow tools + Microsoft 365 connectors. | Local · stdio |
| Prismix Status MCPReal-time status for 75+ AI services (OpenAI, Anthropic, Cursor). No auth, CORS-enabled. | Remote · HTTPLive check: ✓ handshake |
| PrismsplitSplit bills from your AI: read bills & balances, create equal splits, request settlements. | Remote · HTTPLive check: sign-in required |
| PrivacyAudit websites for GDPR, CCPA, and ePrivacy compliance - trackers, consent, and policies. | Local · stdio |
| Privacypage MCPGenerate privacy policies, ToS, EULAs, cookie policies & disclaimers from your AI agent. | Local · stdio |