Developer · Remote MCP server
Blinkbox
Open-source Zapier/n8n alternative as an MCP server: agents build, run and debug your workflows.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.blinkboxhq/blinkbox- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-16
- Updated
- 2026-09-16
- Publisher
- blinkboxhq (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/blinkboxhq) · how
- Listed under
- n8n MCP servers
- Website
- blinkbox.net
- Repository
- github.com/blinkboxhq/Blinkbox
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.blinkbox.net/mcp | Authorization (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 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Blinkbox
Blinkbox is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.blinkbox.net/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: Authorization (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; 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 developer servers
| Server | Runs |
|---|---|
| Blacklotusdev8 Test MGreet anyone by name with a friendly hello. Scrape webpages to extract content for quick reference… | Remote · HTTPLive check: ✗ no handshake |
| BlacksmithMCP server for Blacksmith CI - query runs, analyze test failures, detect flaky tests. | Local · stdio |
| BlackVeil DNS & Email Security ScannerDNS and email security scanner with 81 MCP tools for SPF, DMARC, DNSSEC, SSL, and brand audits. | Remote · HTTPLive check: ✓ handshake |
| BlackwallAPI-key pre-action risk gate: any irreversible agent action (money, SQL, delete, email). | Local · stdio |
| blitz.cloudHost apps in the EU from your assistant: App Store, Docker, GitHub, databases, logs. | Remote · HTTPLive check: sign-in required |
| BlogSearch and read the Radixia blog (enterprise AI, cloud, open source) via MCP. | Remote · HTTPLive check: ✓ handshake |
| Blue Synergy CortexLong-term, drift-free cognitive memory engine for AI Agents and Cursor IDE. | Remote · SSELive check: ✓ SSE reachable |
| Blueprint ChartThe open chart format an LLM writes and the browser renders - to interactive, accessible SVG. | Local · stdio |