io.github.ABWerks/pequod-mcp
PYPI · PEQUOD-MCP · SCANNED SEP 16
Complete US ETF holdings from SEC N-PORT filings + ticker/CUSIP/FIGI crosswalk. Primary source.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 20 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 665 tokens (~133/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.ABWerks/pequod-mcp server?
io.github.ABWerks/pequod-mcp runs locally as a PyPI package, launched with uvx pequod-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · pequod-mcp
claude mcp add abwerks-pequod-mcp -- uvx pequod-mcp
{
"mcpServers": {
"abwerks-pequod-mcp": {
"command": "uvx",
"args": [
"pequod-mcp"
]
}
}
} {
"servers": {
"abwerks-pequod-mcp": {
"command": "uvx",
"args": [
"pequod-mcp"
]
}
}
} codex mcp add abwerks-pequod-mcp -- uvx pequod-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"abwerks-pequod-mcp": {
"type": "local",
"command": [
"uvx",
"pequod-mcp"
],
"enabled": true
}
}
} openclaw mcp add abwerks-pequod-mcp --command uvx --arg pequod-mcp
mcp_servers:
abwerks-pequod-mcp:
command: "uvx"
args: ["pequod-mcp"] {
"McpServers": {
"abwerks-pequod-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"pequod-mcp"
]
}
}
} assistant mcp add abwerks-pequod-mcp -t stdio -c uvx -a pequod-mcp
{
"mcpServers": {
"abwerks-pequod-mcp": {
"command": "uvx",
"args": [
"pequod-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Sept 2026 · Analysed pypi/pequod-mcp@0.2.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 20 packages
| Packages resolved | 20 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_etf_holdings Get Etf Holdings ~156
Get the complete holdings of any US-registered ETF via SEC EDGAR. Uses Form N-PORT filings (filed monthly by all US ETFs) as the single, consistent primary source. Each holding includes name, ticker, ISIN, FIGI, LEI, shares, USD value, percent of net assets, country, and currency. (CUSIPs are deliberately not included in output.)
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | – | Optional 10-digit SEC CIK (from lookup_cik). Skips the ticker→CIK lookup if provided. |
| ticker | string | yes | The ETF ticker symbol (e.g. 'QQQ', 'SPY', 'SCHD', 'IHDG'). |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_cik Lookup Cik ~145
Look up a ticker's SEC Central Index Key (CIK) and entity metadata. This is the first step before calling get_etf_holdings. The CIK is the SEC's unique identifier for every filing entity. The submissions endpoint also returns the entity name, SIC code, tickers, exchanges, fiscal year end, and addresses. The ticker→CIK mapping comes from SEC's company_tickers.json (covers 10,000+ US tickers), cached on disk with a 24-hour freshness window.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Stock or ETF ticker symbol (e.g. 'SCHD', 'QQQ', 'AAPL'). |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_cusip Resolve Cusip ~155
Resolve a CUSIP (or SEDOL) identifier to a Yahoo-convention ticker symbol. Queries OpenFIGI (one batched request trying both ID_CUSIP and ID_SEDOL), maps the result to a Yahoo-convention symbol via pure suffix mapping, and verifies the mapping against SEC company_tickers.json name/ticker agreement. A gross name mismatch between OpenFIGI and SEC vetoes the mapping. Note: the CUSIP is accepted as INPUT only — tool outputs carry ticker/ISIN/FIGI identifiers, never CUSIPs.
| Name | Type | Req | Description |
|---|---|---|---|
| cusip | string | yes | A 9-character CUSIP (or 7-character SEDOL) identifier. |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_figi Resolve Figi ~89
Resolve a Bloomberg FIGI (Financial Instrument Global Identifier) to a Yahoo-convention ticker symbol. Queries OpenFIGI, maps the exchange code to a Yahoo suffix (pure string mapping), and verifies the mapping against SEC company_tickers.json name/ticker agreement.
| Name | Type | Req | Description |
|---|---|---|---|
| figi | string | yes | A Bloomberg FIGI identifier (e.g. 'BBG000BVRVT1'). |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_ticker Resolve Ticker ~120
Resolve a raw ticker symbol to its Yahoo-convention equivalent. Applies exchange suffix mapping and known manual fixes as a pure string transformation (no Yahoo network calls), then verifies the mapping against SEC company_tickers.json and/or OpenFIGI.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange_code | string | – | Optional exchange code — MIC format like 'XASX' or short format like 'AU', 'LN', 'SW', 'JP'. |
| symbol | string | yes | Raw ticker symbol (e.g. 'AAPL', 'SCMN', 'BHP'). |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.ABWerks/pequod-mcp server?
io.github.ABWerks/pequod-mcp is listed in the public MCP registry as io.github.ABWerks/pequod-mcp. Complete US ETF holdings from SEC N-PORT filings + ticker/CUSIP/FIGI crosswalk. Primary source. This page covers its PyPI package (pequod-mcp).
Is the io.github.ABWerks/pequod-mcp server safe to use?
io.github.ABWerks/pequod-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.ABWerks/pequod-mcp server expose?
io.github.ABWerks/pequod-mcp exposes 5 tools: lookup_cik, resolve_ticker, resolve_cusip, resolve_figi, get_etf_holdings. Their descriptions and schemas cost roughly 665 tokens of context every time the server is loaded.
Is the io.github.ABWerks/pequod-mcp server still maintained?
io.github.ABWerks/pequod-mcp is still listed as active in the MCP registry. We last reached this channel on 16 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.