Ext Ops Panel
Open dashboard
Comparison

Contractor Licence Changes vs mcpgawk

Contractor Licence Changes is an MCP server published by ottobot.agency. Marketplaces we read that list it: 1 (Official MCP Registry). mcpgawk is an MCP server published by gawk-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceContractor Licence Changesmcpgawk
Official MCP Registry Listed
Version: 0.1.3
Forks (GitHub): 1 028
Stars (GitHub): 7 371
Not marked · First seen
Listed
Version: 0.1.78
Downloads/month (PyPI): 4 766
Downloads/week (PyPI): 1 072
Forks (GitHub): 0
Stars (GitHub): 1
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

Contractor Licence Changes vs mcpgawk
FactContractor Licence Changesmcpgawk
Marketplaces that list it11
Stars (GitHub) (differs)7 371 (better)1 (worse)
Forks (GitHub) (differs)1 028 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (license-changes-mcp.ottobot2025.workers.dev/mcp)On your machine (mcpgawk)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/modelcontextprotocol/registrygithub.com/gawk-dev/mcpgawk
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agono 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

Contractor Licence Changes

In its own words, on Official MCP Registry:

Did this contractor's licence change? Observed lapses and reinstatements, not a snapshot.

mcpgawk

In its own words, on Official MCP Registry:

Measure MCP servers, pin the approved tool surface, refuse calls to tools that changed. Local-first.

How to run each

Contractor Licence Changes As a remote MCP server

Claude Code
claude mcp add --transport http contractor-license-changes https://license-changes-mcp.ottobot2025.workers.dev/mcp

mcpgawk As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcpgawk -- uvx mcpgawk mcp

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

Only Contractor Licence Changes 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

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

What it can do: Contractor Licence Changes · What it can do: mcpgawk · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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