Other · Remote MCP server
Patchistry MCP Server
DTC modular hat brand MCP server. 6 tools for AI agents: catalog, curated builds, shipping.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.patchistry/patchistry-mcp-server- Version
- 0.2.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-06-12
- Updated
- 2026-06-12
- Publisher
- patchistry (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/patchistry) · how
- Website
- patchistry.com
- Repository
- github.com/patchistry/patchistry-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://patchistry-mcp-server.vercel.app/rpc | None |
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 200)
- Handshake
- patchistry-mcp 0.3.0 · protocol 2025-03-26
- Tools discovered
- 6:
list_canvases,list_patches,get_curated_build,recommend_build,get_shipping_policy,get_contact - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | patchistry-mcp-server | 0.2.0 | stdio |
How to connect Patchistry MCP Server
Patchistry MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://patchistry-mcp-server.vercel.app/rpc, 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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: patchistry-mcp-server version 0.2.0. 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 patchistry-mcp-server@0.2.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"patchistry-mcp-server": {
"command": "npx",
"args": [
"-y",
"patchistry-mcp-server@0.2.0"
]
}
}
}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 |
|---|---|
| PasteGive AI tools access to your Mac clipboard history and pinboards from Paste. Runs locally. | Local · stdio |
| PasteHTMLPublish, update, and organize HTML and Markdown pastes on PasteHTML as the authorized user. | Remote · HTTPLive check: sign-in required |
| PastepileDurable, versioned memory for AI assistants. Remote memory needs a Pastepile subscription. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| PasteSheet - Google SheetsQuery your Google Sheets as structured JSON: list sheets and tabs, read schemas, filter rows. | Remote · HTTPLive check: sign-in required |
| PatchloomAgent-safe structured edits: JSON/YAML/TOML/md/AST, dry-run, batch/tx. Not a filesystem MCP. | Local · stdio |
| PatchroomsAgent-ready feedback for AI-built apps - read and close UI feedback reports over MCP. | Remote · HTTPLive check: sign-in required |
| PathmintBefore you pay an x402 URL, ping it live or dead. One cent, USDC on Base. | Remote · HTTPLive check: ✓ handshake |
| pathmodeio MCP-SERVERDeterministic intent preflight before your agent builds: six gates, keyless, no model call. | Local · stdio |