Ext Ops Panel
Open dashboard
Comparison

sourcery-agent vs Priority — TypeScript Compiler Intelligence

sourcery-agent is a plugin bundle for AI coding tools published by abyssbugg. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Priority — TypeScript Compiler Intelligence is an MCP server published by semanticreader.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacesourcery-agentPriority — TypeScript Compiler Intelligence
Community marketplace abyssbugg-labs/sourcery-agent-bundle Listed
Version: 0.2.4
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.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

sourcery-agent vs Priority — TypeScript Compiler Intelligence
Factsourcery-agentPriority — TypeScript Compiler Intelligence
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)On your machine (@abyssbugg/sourcery)Remote server (semanticreader.dev/mcp/registry)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)4Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/abyssbugg-labs/sourcery-agent-bundleNot stated
Changes in the last 7 days (differs)20
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 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

sourcery-agent

In its own words, on Community GitHub marketplaces:

Sourcery security findings for AI coding agents: triage and minimal-change remediation via the public Sourcery API (12 MCP tools + skills).

Priority — TypeScript Compiler Intelligence

In its own words, on Official MCP Registry:

Stateless TS/JS compiler facts for agents: references, imports, impact. No repo index or OAuth.

How to run each

sourcery-agent As a Codex plugin

Codex
codex plugin marketplace add abyssbugg-labs/sourcery-agent-bundle

Priority — TypeScript Compiler Intelligence As a remote MCP server

Claude Code
claude mcp add --transport http semantic-reader https://semanticreader.dev/mcp/registry

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

Only Priority — TypeScript Compiler Intelligence has a remote endpoint we 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

The marketplaces of Priority — TypeScript Compiler Intelligence publish no settings it asks for, so we do not compare settings.

What it can do: sourcery-agent · What it can do: Priority — TypeScript Compiler Intelligence · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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