Ext Ops Panel
Open dashboard
Comparison

Falcon Builder vs Perceptdot Core

Falcon Builder is an MCP server published by falconbuilder.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Perceptdot Core is an MCP server published by perceptdot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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 BuilderPerceptdot Core
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.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 Perceptdot Core
FactFalcon BuilderPerceptdot Core
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)On your machine (@perceptdot/core)
Transport (differs)Streamable HTTPstdio
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)not checked yetno remote endpoint we check

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.

Perceptdot Core

In its own words, on Official MCP Registry:

B2A2H MCP server — AI agent app store. Auto-discover and recommend MCP servers for any project.

How to run each

Falcon Builder

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Perceptdot Core As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio core -- npx -y @perceptdot/core

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

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: Perceptdot Core · 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