Ext Ops Panel
Open dashboard
Comparison

reco vs AgentDiet Domain OSINT, TLS Certificate & Security Headers Recon

reco is a plugin bundle for AI coding tools published by RecoLabs. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). AgentDiet Domain OSINT, TLS Certificate & Security Headers Recon is an MCP server published by agentdiet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplacerecoAgentDiet Domain OSINT, TLS Certificate & Security Headers Recon
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 7.0.17
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

reco vs AgentDiet Domain OSINT, TLS Certificate & Security Headers Recon
FactrecoAgentDiet Domain OSINT, TLS Certificate & Security Headers Recon
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-21
Where it runs (differs)Installs as a plugin bundleRemote server (domain-osint.agentdiet.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)8Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/recolabs/reco-mcp-pluginsgithub.com/robertoyanguas-ops/assay
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-19
Endpoint at the last check (differs)no remote endpoint we checkResponded 8 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

reco

In its own words, on Claude Code: claude-plugins-community:

Reco SaaS & AI security — query app risks, shadow IT, AI agents, user posture, and access events directly from Claude Code

AgentDiet Domain OSINT, TLS Certificate & Security Headers Recon

In its own words, on Official MCP Registry:

Inspects live IPv4/IPv6 DNS resolution, TLS certificate issuer/expiry, and HTTP security grade.

How to run each

reco As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install reco@claude-community

AgentDiet Domain OSINT, TLS Certificate & Security Headers Recon As a remote MCP server

Claude Code
claude mcp add --transport http domain-osint https://domain-osint.agentdiet.dev/mcp

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

Only AgentDiet Domain OSINT, TLS Certificate & Security Headers Recon 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: reco · What it can do: AgentDiet Domain OSINT, TLS Certificate & Security Headers Recon · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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