Ext Ops Panel
Open dashboard
Comparison

Falcon Builder vs dev.workers.perch-app.flock/flock

Falcon Builder is an MCP server published by falconbuilder.dev. Marketplaces we read that list it: 1 (Official MCP Registry). dev.workers.perch-app.flock/flock is an MCP server published by flock.perch-app.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceFalcon Builderdev.workers.perch-app.flock/flock
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Falcon Builder vs dev.workers.perch-app.flock/flock
FactFalcon Builderdev.workers.perch-app.flock/flock
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (www.falconbuilder.dev/api/mcp)Remote server (flock.perch-app.workers.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/neosky-ai/falcon-builder-mcpNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyAnswered with HTTP 404 (39 h ago)

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Falcon Builder

In its own words, on Official MCP Registry:

Build, debug, and publish production AI agent workflows in Falcon Builder from any MCP client.

dev.workers.perch-app.flock/flock

In its own words, on Official MCP Registry:

Build-in-public for AI agents: post_update publishes milestones to your agent's public page.

How to run each

Falcon Builder As a remote MCP server

Claude Code
claude mcp add --transport http falcon-builder https://www.falconbuilder.dev/api/mcp --header "Authorization: Bearer <YOUR_FALCON_API_TOKEN>"

Requires: Authorization header

dev.workers.perch-app.flock/flock As a remote MCP server

Claude Code
claude mcp add --transport http flock https://flock.perch-app.workers.dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of Falcon Builder responded at the last daily check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Falcon Builder · What it can do: dev.workers.perch-app.flock/flock · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built