Ext Ops Panel
Open dashboard
Comparison

equibles vs EDGAR 13F point-in-time

equibles is a plugin bundle for AI coding tools published by Equibles. Marketplaces we read that list it: 1 (Community GitHub marketplaces). EDGAR 13F point-in-time is an MCP server published by Serios16. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
MarketplaceequiblesEDGAR 13F point-in-time
Community marketplace davepoon/buildwithclaude Listed
Version: 1.0.0
Forks (GitHub): 653
Stars (GitHub): 3 680
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.2
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

equibles vs EDGAR 13F point-in-time
FactequiblesEDGAR 13F point-in-time
Marketplaces that list it11
Stars (GitHub) (differs)3 680 (better)0 (worse)
Forks (GitHub) (differs)653 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.equibles.com/mcp)On your machine (edgar13f-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/davepoon/buildwithclaudegithub.com/serios16/edgar13f-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-152026-10-22
Endpoint at the last check (differs)Not responding since 2026-10-27no 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

equibles

In its own words, on Community GitHub marketplaces:

US stock market research through the hosted Equibles MCP server: SEC filings with full-text search, XBRL financial statements, earnings call transcripts, insider and congressional trades, 13F institutional holdings, short interest, end-of-day prices, option chains and macroeconomic data. Sign in over OAuth from /mcp; free tier of 100 requests a day, no credit card.

EDGAR 13F point-in-time

In its own words, on Official MCP Registry:

SEC Form 13F holdings as they could have been known on a given date (stdio).

How to run each

equibles As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install equibles@buildwithclaude

EDGAR 13F point-in-time As a local MCP server: PyPI package

Claude Code
claude mcp add --env "SEC_USER_AGENT=<YOUR_SEC_USER_AGENT>" --transport stdio edgar13f-mcp -- uvx edgar13f-mcp

Requires: SEC_USER_AGENT

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

Only equibles 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 equibles publish no settings it asks for, so we do not compare settings.

What it can do: equibles · What it can do: EDGAR 13F point-in-time · 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