Ext Ops Panel
Open dashboard
Comparison

ai.perfloop/perfloop vs Snipara Project Intelligence

ai.perfloop/perfloop is an MCP server published by perfloop.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Snipara Project Intelligence is an MCP server published by Snipara. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplaceai.perfloop/perfloopSnipara Project Intelligence
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

ai.perfloop/perfloop vs Snipara Project Intelligence
Factai.perfloop/perfloopSnipara Project Intelligence
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (app.perfloop.ai/mcp)Remote server (api.snipara.com/mcp/%7Bproject_slug%7D)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/snipara/snipara-examples
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 39 h ago, requires a keyResponded 2 days ago, requires a key

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

ai.perfloop/perfloop

In its own words, on Official MCP Registry:

Always-on performance engineering for your own code: proven pull requests, the merge stays yours.

Snipara Project Intelligence

In its own words, on Official MCP Registry:

Hosted MCP for source-backed project context, memory, code impact, and agent workflow continuity.

How to run each

ai.perfloop/perfloop As a remote MCP server

Claude Code
claude mcp add --transport http perfloop https://app.perfloop.ai/mcp

Snipara Project Intelligence

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

Requires: X-API-Key header

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

Both endpoints 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: ai.perfloop/perfloop · What it can do: Snipara Project Intelligence · 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