Developer · Remote MCP server
FlurryPORT
Webhook capture and replay, delivery pipes, and signed multi-agent rooms. No signup to start.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.flurryport/webhooks-and-rooms- Version
- 0.6.12
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-22
- Updated
- 2026-09-22
- Publisher
- io.flurryport
- Namespace
- Namespace verified by the MCP Registry via the domain flurryport.io · how
- Website
- flurryport.io
- Repository
- github.com/flurryport/cli
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.flurryport.io/mcp | 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 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
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | flurryport | 0.6.12 | stdio |
How to connect FlurryPORT
FlurryPORT is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.flurryport.io/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.
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: flurryport version 0.6.12. 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 flurryport@0.6.12.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"webhooks-and-rooms": {
"command": "npx",
"args": [
"-y",
"flurryport@0.6.12"
]
}
}
}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 |
|---|---|
| FlowboardDiscover cloud shapes and create, inspect, validate, patch, and review architecture diagrams. | Remote · HTTPLive check: ✓ handshake |
| FlowCastleBuild, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform. | Remote · HTTPLive check: ✓ handshake |
| FlowSentrySecurity scanner for n8n workflows + live MCP Trust-Check. 18 rules, OWASP mapped. Paid x402 API. | Remote · HTTPLive check: ✗ no handshake |
| FluidTalkCreate AI Characters and generate their DM and comment replies from any MCP client. | Remote · HTTPLive check: sign-in required |
| Flutter LampLive runtime data from a running Flutter app: exceptions, logs, network, frames, diagnosis. | Local · stdio |
| Flutter SkillAI-powered E2E testing for 10 platforms. 253 MCP tools. Zero test code needed. | Local · stdio |
| Flutter Structure MCPAudit architecture, security, memory, and code quality in Flutter, Laravel, Node, Python, & Vue. | Local · stdio |
| FlutterGoCreate, edit, preview, and build Flutter apps via FlutterGo.AI cloud MCP (OAuth). | Remote · HTTPLive check: sign-in required |