Developer · Remote MCP server
Snipara Project Intelligence
Hosted MCP for source-backed project context, memory, code impact, and agent workflow continuity.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Snipara/snipara- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-21
- Updated
- 2026-07-21
- Publisher
- Snipara (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Snipara) · how
- Repository
- github.com/Snipara/snipara-examples
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.snipara.com/mcp/{project_slug} | 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.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect Snipara Project Intelligence
Snipara Project Intelligence is a remote MCP server: there is nothing to install. Its endpoint is https://api.snipara.com/mcp/{project_slug}, 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 URL contains placeholders to fill in before connecting: {project_slug}.
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.
Derived from the registry entry, not tested here. 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 developer servers
| Server | Runs |
|---|---|
| snapdiff.aiVisual-diff & change-detection tools that catch agentic UI drift for coding agents. | Local · stdio |
| SnapgrabURL to screenshot with metadata. Python MCP server. Claude Vision optimized. | Local · stdio |
| sncroLive browser debugging for AI assistants - DOM, console, network via MCP. | Remote · HTTPLive check: ✗ no handshake |
| SNHP - free negotiation math + agent memoryFree game-theory negotiation advisor for agents, plus paid receipted sessions and agent memory. | Remote · HTTPLive check: ✓ handshake |
| Snipper MCPSearch, read, create and organise code snippets in SnipperApp 3, a native macOS snippet manager. | Local · stdio |
| Snow Leo Risk & ComplianceScreen names against OFAC, EU and UN lists; check CVEs, domain DNS and WHOIS, and public tenders. | Remote · HTTPLive check: sign-in required |
| Snowfakery MCPMCP server for authoring, analyzing, debugging, and running Snowfakery recipes. | Local · stdio |
| Snowflake MCP ServerA Snowflake MCP server - SQL queries, schema exploration, and data insights for AI assistants. | Local · stdio |