Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stylus Contracts vs Philidor

Philidor is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.

OpenZeppelin Stylus Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Philidor is a plugin bundle for AI coding tools published by Philidor. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceOpenZeppelin Stylus ContractsPhilidor
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace philidor-labs/philidor-mcp Not listed Removed on 2026-10-20
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 5
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

OpenZeppelin Stylus Contracts vs Philidor
FactOpenZeppelin Stylus ContractsPhilidorno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)No figure on GitHub5
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stylus/mcp)Remote server (mcp.philidor.io/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle6
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/philidor-labs/philidor-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-14
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. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of Philidor

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • Philidor DeFi Vault Risk Analytics

    Search 700+ DeFi vaults, compare risk scores, analyze protocols. No API key needed.

    by philidor.io · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Basis Protocol

    Stablecoin risk scores, wallet risk profiles, and transaction risk assessment.

    by shlok-lgtm · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • defiguard-mcp io.github.kota1026/defiguard-mcp

    DeFiGuard MCP Server - DeFi protocol risk analysis tools for AI coding agents. Analyze token co...

    by kota1026 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Veriql Risk

    Rug, honeypot and wallet-approval risk checks on Solana and EVM, with every penalty driver shown.

    by veriql.app · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • AtlasYield

    DeFi vault judgment for agents: 16-factor Atlas Score, route survival, blowup alerts. Read-only.

    by atlasyield.club · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • pigi.finance — DeFi Vault Intelligence

    DeFi vault data from pigi.finance: yields, TVL, history and risk ratings across chains.

    by pigi-fi · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

OpenZeppelin Stylus Contracts

In its own words, on Docker MCP Catalog:

Access to OpenZeppelin Stylus Contracts.

Philidor

In its own words, on Community GitHub marketplaces:

Read-only DeFi and RWA vault risk analytics from Philidor. Scores, tiers, lending markets, incidents, and loop-venue checks through the hosted MCP server. No API key.

How to run each

OpenZeppelin Stylus Contracts As a remote MCP server

Claude Code
claude mcp add --transport http openzeppelin-stylus https://mcp.openzeppelin.com/contracts/stylus/mcp

Philidor

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

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

Only OpenZeppelin Stylus Contracts has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Philidor publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: OpenZeppelin Stylus Contracts · What it can do: Philidor · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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