US Economic, SEC EDGAR & On-Chain Data (x402) MCP server
online · 100% uptimenet.agentfund/us-economic-macro-sec-edgar-onchain-data·v0.2.021 paid tools: US macro data, SEC EDGAR filings, on-chain EVM reads. Settled in USDC on Base.
0 stars
Reviews
Write oneNobody has reviewed US Economic, SEC EDGAR & On-Chain Data (x402) yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
US Economic, SEC EDGAR & On-Chain Data (x402) tools (21)
write = sends, deletes, buys or postsbls_cpiFreeLatest U.S. CPI inflation from the Bureau of Labor Statistics, with the rates already computed. BLS publishes index levels, not inflation rates. This tool does the arithmetic: headline and core (all items less food and energy) CPI, each with year-over-year and month-over-month percent change. Year-over-year uses not-seasonally-adjusted data and month-over-month uses seasonally adjusted, matching how these figures are conventionally reported. When to use: you need the current inflation rate, a real-versus-nominal adjustment, or CPI context for a macro decision. When NOT to use: you need PCE (the Fed's preferred gauge), regional or category-level CPI detail, or a long historical series. Args: none. Returns structuredContent: { "asOf": "2026-07", "periodName": "July 2026", "headline": { "index": 333.918, "yoyPercent": 2.9, "momPercent": 0.2 }, "core": { "index": 337.133, "yoyPercent": 3.1, "momPercent": 0.3 }, "source": "https://www.bls.gov/cpi/" }
edgar_13f_holdingsFreeInstitutional stock holdings for a fund manager, from its latest SEC Form 13F. 13F filings split the actual holdings into a separate "information table" XML document that the filing index does not point at directly; this locates it, parses every position, and rolls up lots reported separately (different share classes, put/call splits) into one row per issuer. When to use: seeing what a fund or institution holds and how much, tracking "smart money" positioning, portfolio research. When NOT to use: real-time positions (13F is filed up to 45 days after quarter end, so this is always historical), short positions (13F does not require disclosing shorts), or non-U.S. filers. Args: - ticker (string, required): the FILER's ticker (if it has one) or its SEC CIK, e.g. "1067983" for Berkshire Hathaway. - limit (integer, optional, default 25): maximum holdings to return, largest by value first (1-200). Returns structuredContent: { "cik": "0001067983", "filer": "BERKSHIRE HATHAWAY INC", "periodOfReport": "2026-06-30", "filedAt": "2026-08-14", "totalPositions": 45, "totalValueUsd": 293000000000, "holdings": [ { "issuer": "ALLY FINL INC", "cusip": "02005N100", "valueUsd": 900335661000, "shares": 19593812, "lots": 3 } ], "source": "https://www.sec.gov/edgar" } Reports the most recently FILED 13F-HR. Values are whole USD, taken directly from the filing.
edgar_filings_feedFreeRecent SEC filings for a company, newest first, with 8-K item codes translated to plain English. A general-purpose filings feed: any form type, or a specific set (8-K for material events, 10-K/10-Q for periodic reports, S-1 for new-issue prospectuses, SC 13D/13G for activist and passive stakes). 8-K filings include their item numbers (e.g. "5.02") decoded into a label ("Departure/appointment of directors or officers") rather than leaving you to look up the code. When to use: monitoring a company's material-event stream, building a filings watchlist, or finding a specific filing type. When NOT to use: you need the parsed FINANCIAL content of a filing (use edgar_financials) or insider trades (use edgar_insider_transactions). Args: - ticker (string, required): a ticker such as "AAPL", or a bare CIK such as "320193". - forms (string[], optional): filter to specific form types, e.g. ["8-K"] or ["10-K","10-Q"]. Omit for all forms. - limit (integer, optional, default 20): maximum filings to return (1-100). Returns structuredContent: { "cik": "0000320193", "entity": "Apple Inc.", "ticker": "AAPL", "count": 1, "filings": [{ "form": "8-K", "filedAt": "2026-08-01", "reportDate": "2026-07-31", "items": [{ "code": "2.02", "label": "Results of operations and financial condition" }], "documentUrl": "https://www.sec.gov/Archives/..." }], "source": "https://www.sec.gov/edgar" }
edgar_financialsFreeKey financials for a U.S. public company, pulled from SEC XBRL company facts. Returns revenue, net income, diluted EPS, total assets, total liabilities, shareholders' equity and cash, each with the most recent ANNUAL and QUARTERLY figure, the period covered, and the form it came from. Handles two things that trip up naive XBRL queries: filers migrated from the "Revenues" tag to "RevenueFromContractWithCustomerExcludingAssessedTax" under ASC 606, so each concept tries several tags in order; and the SEC repeats facts across filings with differing period lengths, so observations are classified as annual or quarterly by their actual duration rather than by trusting the fiscal-period label. When to use: fundamentals for valuation or screening, checking latest reported revenue or EPS, pulling balance-sheet lines. When NOT to use: you need full statements line by line, segment detail, non-GAAP measures, or analyst estimates. Args: - ticker (string, required): a ticker such as "AAPL", or a bare CIK such as "320193". Returns structuredContent: { "cik": "0000320193", "entity": "Apple Inc.", "ticker": "AAPL", "concepts": { "revenue": { "label": "Revenue", "tag": "RevenueFromContractWithCustomerExcludingAssessedTax", "annual": { "end": "2025-09-27", "start": "2024-09-29", "value": 416000000000, "unit": "USD", "fiscalYear": 2025, "fiscalPeriod": "FY", "form": "10-K" }, "quarterly": { "end": "2026-06-27", "value": 94000000000, "unit": "USD", "form": "10-Q" } }, "netIncome": {}, "epsDiluted": {}, "assets": {} }, "source": "https://www.sec.gov/edgar" } A concept the filer does not report comes back with tag null and both periods null, rather than a fabricated zero.
edgar_full_text_searchFreeFull-text search across all SEC EDGAR filings since 2001 for a keyword or phrase. Wraps EDGAR's own full-text search index, so it covers every filer and form type, not just a single company. Useful for finding who is disclosing a particular risk, technology, litigation, or event across the entire market. When to use: cross-company research ("who is disclosing AI-related risk factors"), finding filings that mention a specific term, litigation or regulatory tracking. When NOT to use: you already know the company (use edgar_filings_feed, which is company-scoped and cheaper), or you need results from before 2001 (EDGAR full-text search does not cover that far back). Args: - query (string, required): search text. Wrap an exact phrase in double quotes, e.g. "\"material weakness\"". - forms (string[], optional): restrict to form types, e.g. ["10-K"]. - dateFrom (string, optional): ISO start date (YYYY-MM-DD). - dateTo (string, optional): ISO end date (YYYY-MM-DD). - limit (integer, optional, default 10): maximum hits to return (1-50). Returns structuredContent: { "query": "material weakness", "totalMatches": 10000, "totalIsApproximate": true, "count": 2, "hits": [ { "id": "0001193125-26-123456:doc.htm", "entity": "Example Corp.", "form": "10-K", "filedAt": "2026-03-01", "cik": "0000320193" } ], "source": "https://www.sec.gov/edgar" } "totalMatches" is a lower bound and "totalIsApproximate" is true once EDGAR's own count exceeds its display cap (10,000) — narrow with forms/dateFrom/dateTo for a precise count.
edgar_insider_transactionsFreeInsider buying and selling for a U.S. public company, parsed from SEC Form 4 filings. Form 4 is published as raw ownership XML, one document per filing, with the machine-readable file hidden behind an XSL-rendered URL. This resolves the ticker to a CIK, finds the most recent filings, fetches each XML document, and returns clean transactions: who traded, their role, the date, the SEC transaction code with its plain-English meaning, share count, price, computed dollar value, and shares held afterwards. When to use: tracking insider sentiment, checking whether executives are buying or selling, auditing recent officer and director activity. When NOT to use: you need institutional holdings (that is Form 13F), or derivative/option detail (only non-derivative transactions are returned), or non-U.S. issuers. Args: - ticker (string, required): a ticker such as "AAPL", or a bare CIK such as "320193". - limit (integer, optional, default 5): how many recent filings to parse (1-20). - forms (string[], optional, default ["4"]): which ownership forms to include ("3", "4", "5"). Returns structuredContent: { "cik": "0000320193", "issuer": "Apple Inc.", "ticker": "AAPL", "count": 1, "filings": [{ "filedAt": "2026-08-13", "owner": "Newstead Jennifer", "ownerTitle": "SVP, GC and Secretary", "isOfficer": true, "isDirector": false, "transactions": [{ "date": "2026-08-11", "code": "S", "codeMeaning": "Open-market or private sale", "acquiredDisposed": "D", "shares": 1439, "pricePerShare": 307.75, "value": 442852.25, "sharesOwnedAfter": 40107 }], "documentUrl": "https://www.sec.gov/Archives/..." }], "source": "https://www.sec.gov/edgar" } An individual filing that cannot be parsed is skipped rather than failing the call. If nothing at all is parseable the call errors and is not billed.
macro_energyFreeLatest U.S. energy market data from the Energy Information Administration: WTI crude price, crude oil inventories, and natural gas storage. Combines three EIA series that usually require separate lookups: the WTI Cushing spot price, weekly U.S. crude oil ending stocks (with week-over-week percent change), and weekly natural gas underground storage (with week-over-week percent change). When to use: energy-sector context, inflation pass-through analysis (energy prices feed CPI/PCE), trading around the weekly EIA inventory releases. When NOT to use: you need regional/PADD-level breakdowns, refined product prices (gasoline, diesel), or non-U.S. energy data. Args: none. Returns structuredContent: { "asOf": "2026-08-07", "wtiSpotUsdPerBbl": 84.77, "crudeStocksThousandBbl": 420000, "crudeStocksWowPercent": -1.2, "naturalGasStorageBcf": 3100, "naturalGasStorageWowPercent": 0.8, "source": "https://www.eia.gov/petroleum/" }
macro_gdpFreeLatest U.S. real GDP growth rate, from BEA's National Income and Product Accounts. Returns the annualized quarter-over-quarter growth rate for the most recent quarter (the headline "how is the economy growing" number), plus the prior two quarters for trend context. BEA publishes this table as a percent-change series already, so no growth-rate math is needed here. When to use: reading the pace of economic growth, recession-risk context (two consecutive negative quarters), or macro backdrop for a market decision. When NOT to use: you need GDP in dollar levels, expenditure-component detail (consumption, investment, government, net exports), or real-time/nowcast estimates (this is BEA's official, lagged release). Args: none. Returns structuredContent: { "asOf": "2026Q2", "growthAnnualizedPercent": 1.5, "priorQuarters": [ { "quarter": "2026Q1", "growthAnnualizedPercent": 2.1 }, { "quarter": "2025Q4", "growthAnnualizedPercent": 0.5 } ], "source": "https://www.bea.gov/data/gdp/gross-domestic-product" }
macro_housingFreeLatest U.S. new residential construction: housing starts and building permits, seasonally-adjusted annualized rate. Housing starts (ground broken) and permits (approved but not necessarily started, a leading indicator) are the two headline figures from the Census Bureau's New Residential Construction survey, reported at a seasonally-adjusted annualized rate in thousands of units. When to use: gauging housing-market momentum, a leading indicator for construction activity (permits lead starts), macro context for rate-sensitive sectors. When NOT to use: you need single-family vs multi-family breakdown, regional detail, or completions data. Args: none. Returns structuredContent: { "asOf": "2026-06", "startsThousands": 1427, "permitsThousands": 1380, "startsMomPercent": 19.0, "permitsMomPercent": 2.1, "source": "https://www.census.gov/construction/nrc/index.html" } Figures are in thousands of units at a seasonally-adjusted annual rate (SAAR), the standard convention for this release.
macro_jobsFreeLatest U.S. labour-market data from the Bureau of Labor Statistics, with the headline changes computed. Returns the unemployment rate, labour force participation rate, total nonfarm payrolls, the month-over-month change in payrolls (the "jobs added" number that leads the Employment Situation report), average hourly earnings, and year-over-year wage growth. All series are seasonally adjusted. BLS publishes levels; the month-over-month and year-over-year changes are computed here. When to use: reading the state of the labour market, wage-inflation context, or Fed-policy reasoning. When NOT to use: you need state or metro level detail, industry breakdowns, or JOLTS openings and quits. Args: none. Returns structuredContent: { "asOf": "2026-07", "periodName": "July 2026", "unemploymentRate": 4.1, "participationRate": 62.4, "nonfarmPayrolls": 158858, "payrollsChange": 73, "avgHourlyEarnings": 37.62, "earningsYoyPercent": 3.8, "source": "https://www.bls.gov/ces/" } Payrolls are in thousands of jobs, so payrollsChange 73 means +73,000 jobs on the month.
macro_pceFreeThe Fed's preferred inflation gauge: Personal Consumption Expenditures (PCE) price index, headline and core. The Federal Reserve targets PCE inflation, not CPI, when setting policy. Returns the headline index and "PCE excluding food and energy" (the actual core measure the Fed watches), each with year-over-year and month-over-month percent change computed from BEA's published index levels. When to use: Fed-policy reasoning, comparing the Fed's actual inflation target against CPI, macro research that specifically needs PCE rather than CPI. When NOT to use: you want CPI (use bls_cpi, which is timelier and what headlines usually report) or category-level PCE detail. Args: none. Returns structuredContent: { "asOf": "2026-06", "headline": { "index": 129.5, "yoyPercent": 2.6, "momPercent": 0.3 }, "core": { "index": 131.2, "yoyPercent": 2.8, "momPercent": 0.2 }, "source": "https://www.bea.gov/data/personal-consumption-expenditures-price-index" }
macro_release_calendarFreeUpcoming U.S. economic data releases, with dates and times, from the official BLS news-release schedule. Answers "what macro data drops next, and when" without scraping a web page. Covers the BLS release set that moves markets: CPI, PPI, the Employment Situation (nonfarm payrolls and unemployment), JOLTS, Employment Cost Index, real earnings and productivity. When to use: planning around data risk, checking whether a print lands before a decision, or building a watchlist of upcoming events. When NOT to use: you need the released VALUES (use bls_cpi for CPI), Fed/FOMC meeting dates, or non-U.S. statistical calendars. Args: - limit (integer, optional, default 10): maximum releases to return (1-100), soonest first. - filter (string, optional): case-insensitive substring match on the release title, e.g. "CPI". Returns structuredContent: { "asOf": "2026-08-14", "count": 1, "releases": [ { "date": "2026-09-10", "datetime": "2026-09-10T12:30:00Z", "title": "Consumer Price Index", "source": "BLS" } ], "source": "https://www.bls.gov/schedule/" } Only releases on or after today are returned, soonest first.
macro_retail_salesFreeLatest U.S. retail sales, seasonally adjusted, excluding motor vehicles and parts — the "ex-autos" figure most commonly cited as a consumer-spending signal. Returns the seasonally-adjusted monthly sales total in millions of dollars, with month-over-month and year-over-year percent change computed from the Census Bureau's Advance Monthly Retail Trade Survey. When to use: gauging consumer spending strength, a component of GDP nowcasting, retail-sector demand signal. When NOT to use: you need category-level detail (e.g. just electronics, or just restaurants), the auto-inclusive headline total, or real-time/weekly data (this is a monthly government release). Args: none. Returns structuredContent: { "asOf": "2026-06", "salesMillions": 766192, "momPercent": 0.9, "yoyPercent": 3.4, "source": "https://www.census.gov/retail/index.html" }
onchain_cross_chain_balancesFreeThe same token's balance for one address across multiple EVM chains, in a single call. USDC (and similar assets) has a DIFFERENT contract address on every chain; checking a wallet's total position means resolving each chain's canonical address and querying it separately. This does that and sums the total, so a multi-chain treasury view does not require N separate calls. Supported chains: base, ethereum, optimism, arbitrum, polygon. Supported tokens: USDC (more may be added over time). When to use: totaling a stablecoin position spread across chains, treasury reporting for a multi-chain operation, checking where a wallet's funds actually sit. When NOT to use: you only care about one chain (use onchain_token_balances, which is cheaper), or a token not in the supported set. Args: - address (string, required): the wallet address to check. - token (string, optional, default "USDC"): which token to check across chains. - chains (string[], optional): which chains to include. Defaults to all five supported chains. Returns structuredContent: { "address": "0x...", "token": { "symbol": "USDC", "decimals": 6 }, "totalBalance": "1234.56", "chains": [ { "chain": "base", "chainId": 8453, "raw": "1000000000", "balance": "1000", "failed": false }, { "chain": "ethereum", "chainId": 1, "raw": "234560000", "balance": "234.56", "failed": false } ] } A chain that could not be read reports failed: true with null balances rather than a misleading 0; if every chain fails the call errors and is not billed.
onchain_gasFreeCurrent gas price across multiple EVM chains in a single call. Reads eth_gasPrice on every requested chain in parallel and returns gwei, so you do not have to query each chain's RPC separately and convert units yourself. Supported chains: base, ethereum, optimism, arbitrum, polygon. When to use: choosing the cheapest chain to transact on right now, cost estimation before submitting a transaction, monitoring for a low-gas window. When NOT to use: you need an EIP-1559 fee breakdown (base fee vs priority fee) rather than a single legacy gas price, or historical gas data. Args: - chains (string[], optional): which chains to check. Defaults to all five supported chains. Returns structuredContent: { "chains": [ { "chain": "base", "chainId": 8453, "gasPriceGwei": 0.006 }, { "chain": "ethereum", "chainId": 1, "gasPriceGwei": 0.0986 }, { "chain": "polygon", "chainId": 137, "gasPriceGwei": 278.97 } ], "source": "Live RPC eth_gasPrice, each chain's public network" } A chain whose RPC could not be reached returns gasPriceGwei null rather than a stale or fabricated value; if every requested chain fails the call errors and is not billed.
onchain_oracle_priceFreeRead any Chainlink price feed directly on-chain — a named pair or a raw feed address. Calls latestRoundData on the feed contract itself, so there is no price-API vendor, no rate limit, and no key. Includes the feed's last-updated timestamp and its age in seconds, so you can judge staleness yourself rather than trusting an unlabeled number. Known named pairs on Base: ETH/USD, BTC/USD, USDC/USD. Any other feed address on any supported chain also works. When to use: getting a specific asset's price without depending on a centralized price API, verifying a feed is fresh before using it, cross-checking a price from another source. When NOT to use: you need a token that has no Chainlink feed (use onchain_portfolio's covered set, or a DEX quote instead), or historical/point-in-time prices. Args: - pair (string, required): a named pair (e.g. "ETH/USD") or a raw feed contract address (0x...). - chain (string, optional, default "base"): base | ethereum | optimism | arbitrum | polygon. Returns structuredContent: { "chain": "base", "feed": "0x71041dddad3595F9CEd3DcCFBe3D1F4b0a16Bb70", "pair": "ETH/USD", "price": 1877.86, "decimals": 8, "updatedAt": "2026-08-14T12:00:00.000Z", "ageSeconds": 120, "source": "Chainlink on-chain price feed" }
onchain_portfolioFreeUSD-valued portfolio for a wallet on Base, priced from Chainlink on-chain oracles. Reads the wallet's native ETH plus major ERC-20 balances, reads each asset's Chainlink USD aggregator directly on-chain, and returns holdings with per-asset prices and dollar values, sorted largest first, stamped with the block height. Prices come from Chainlink contracts rather than a price API, so there is no vendor key, no rate limit, and no third-party terms attached to the result. Covered assets: ETH (native), WETH, USDC, cbBTC. Zero-balance assets are listed in "emptyAssets" rather than cluttering holdings. When to use: valuing a wallet, treasury reporting, checking what an address actually holds in dollar terms. When NOT to use: you need an exhaustive scan of every token a wallet has ever received (this checks a curated major-asset set, not an indexer), LP or staked positions, NFTs, or chains other than Base. Args: - address (string, required): the wallet address to value. Returns structuredContent: { "address": "0x...", "chain": "base", "chainId": 8453, "blockNumber": 49976942, "holdings": [ { "symbol": "ETH", "kind": "native", "address": null, "raw": "1500000000000000000", "balance": "1.5", "priceUsd": 3120.44, "valueUsd": 4680.66 } ], "totalValueUsd": 4680.66, "emptyAssets": ["cbBTC"], "priceSource": "Chainlink on-chain price feeds (Base)" } If every balance read fails the call errors and is not billed; a genuinely empty wallet returns an empty holdings list with totalValueUsd 0.
onchain_token_balancesFreeRead an ERC-20 token balance for up to 500 wallet addresses in a SINGLE call. Doing this yourself means issuing hundreds of eth_call requests, batching them, handling per-provider rate limits and partial failures, then scaling raw integers by token decimals. This does all of that and returns clean, ready-to-use numbers plus the block height the snapshot was taken at. Supported chains: base (default), ethereum, optimism, arbitrum, polygon. Defaults to canonical USDC on the selected chain when no token is given. When to use: portfolio or treasury roll-ups, airdrop and eligibility checks, holder analysis, reconciling a list of wallets. When NOT to use: you need native ETH balances (this reads ERC-20 contracts) or balances at a historical block. Args: - addresses (string[], required): 1-500 EVM addresses. Duplicates removed, order preserved. - chain (string, optional, default "base"): base | ethereum | optimism | arbitrum | polygon. - token (string, optional): ERC-20 contract address. Defaults to USDC on the chosen chain. Returns structuredContent: { "chain": "base", "chainId": 8453, "blockNumber": 34567890, "token": { "address": "0x8335...", "symbol": "USDC", "decimals": 6 }, "requested": 3, "queried": 3, "failed": 0, "totalBalance": "1234.56", "holders": [ { "address": "0x...", "raw": "1234560000", "balance": "1234.56" } ] } A read that fails at the provider returns null for that address rather than a misleading 0, and "failed" counts them. If every read fails the call errors and is not billed.
structured_json_repairFreeRepair messy or invalid JSON (the kind LLMs and tools often emit) into clean, valid JSON, and optionally validate/coerce it against a JSON Schema. Pure deterministic compute — no network or model calls. What it fixes: trailing commas, single-quoted strings, unquoted keys, Python literals (None/True/False), NaN/Infinity, Markdown code-fence wrappers, and truncated/garbled tails. When to use: you received text that should be JSON but JSON.parse fails, or you have JSON that must conform to a specific schema and want types coerced (e.g. "36" -> 36, "true" -> true). When NOT to use: the input is already known-valid JSON and no schema check is needed. Args: - input (string, required): the raw/malformed JSON text. - schema (object, optional): a JSON Schema (draft 2020-12) to validate and coerce against. - coerce (boolean, optional, default true): coerce primitive types to satisfy the schema before validating. Returns structuredContent: { "ok": boolean, // true if valid JSON (and schema-valid when a schema was given) "data": any, // the repaired/validated JSON value; null if unfixable "changed": boolean, // true if any repair or coercion modified the input "errors": string[], // actionable messages when ok is false "repairs": string[] // description of each fix applied }
tabular_to_jsonFreeConvert messy tabular text into clean, typed JSON rows. Auto-detects CSV, TSV, or a Markdown table and returns one JSON object per row plus an inferred column/type summary. Pure deterministic compute — no network or model calls. What it handles: delimiter sniffing (comma/semicolon/tab/pipe), quoted fields with embedded commas and newlines, BOM, ragged rows (padded/truncated), Markdown separator rows and escaped pipes, header auto-detection, and per-column type inference (integer/number/boolean/null/string). When to use: you have CSV/TSV/Markdown-table text (often emitted by tools or LLMs) and want structured, typed rows — optionally validated/coerced against a JSON Schema. When NOT to use: the data is already clean JSON, or it is HTML/xlsx/binary (not supported). Args: - input (string, required): raw tabular text. - format ("auto"|"csv"|"tsv"|"markdown", default "auto"): force a format or auto-detect. - hasHeader ("auto"|"true"|"false", default "auto"): whether the first row is a header. - inferTypes (boolean, default true): coerce cells to number/integer/boolean/null; else keep strings. - schema (object, optional): JSON Schema (draft 2020-12) to validate/coerce each row object against. Returns structuredContent: { "ok": boolean, // false if the input cannot be parsed as a table "format": "csv"|"tsv"|"markdown", "columns": [{ "name": string, "type": string }], "rows": [{ ... }], // one object per row, keyed by column name "rowCount": number, "changed": boolean, // true if any normalization/coercion happened "errors": string[], // actionable messages when ok is false "repairs": string[] // description of each normalization applied }
treasury_yield_curveFreeCurrent and recent U.S. Treasury par yield curve rates, with the spreads traders actually watch already computed. Returns every published tenor (1 month through 30 years) for the latest business day, plus the 2s10s spread, the 3m10y spread, and an inversion flag. Source is the U.S. Treasury's official daily par yield curve (public domain, no attribution required). When to use: you need risk-free rates for discounting, a read on the curve's shape, or recession-signal context (curve inversion). When NOT to use: you need intraday quotes (this publishes once per business day) or non-U.S. sovereign curves. Args: - days (integer, optional, default 1): how many recent business days to return, newest first (1-30). Returns structuredContent: { "asOf": "2026-08-14", "latest": { "date": "2026-08-14", "tenors": { "1M": 3.79, "3M": 3.86, "2Y": 4.17, "10Y": 4.68, "30Y": 5.25 }, "spread2s10s": 0.51, "spread3m10y": 0.82, "inverted": false }, "history": [ ...same shape, newest first... ], "source": "https://home.treasury.gov/..." }
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 774ms20/20
- Tool poisoning21 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 81 days ago12/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How US Economic, SEC EDGAR & On-Chain Data (x402) compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 87/100
- higher than 73% of 48,255 servers
- Tools
- 21
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 180 ms
- faster than 67% of 30,031 servers
What its tools let an agent do: 21 read
Install US Economic, SEC EDGAR & On-Chain Data (x402) in Claude Code, Cursor or VS Code
claude mcp add --transport http us-economic-macro-sec-edgar-onchain-data https://x402.agentfund.net/mcp
What the publisher says
From the US Economic, SEC EDGAR & On-Chain Data (x402) repository's README, as published. We do not edit it. Read it on GitHub
US Economic, SEC EDGAR & On-Chain Data — a pay-per-call MCP server
21 data tools that AI agents discover and pay for per call, settled in USDC on Base via the x402 payment protocol. No account, no API key, no subscription.
Live: · Agent guide · Verification ledger · Settlements
The tools
US macro — treasuryyieldcurve, blscpi, macropce, macrojobs, macrogdp, macroretailsales, macrohousing, macroenergy, macroreleasecalendar
SEC EDGAR — edgarfilingsfeed, edgarfinancials, edgarinsidertransactions, edgar13fholdings, edgarfulltextsearch
On-chain EVM — onchaintokenbalances, onchainportfolio, onchaincrosschainbalances, onchainoracleprice, onchain_gas
Pure compute — structuredjsonrepair, tabulartojson
Prices run $0.001–$0.03 per call.
Why these sources
Every tool wraps free public-domain US government data (Treasury, BLS, BEA, Census, EIA, SEC EDGAR) or a direct on-chain read via public RPC. There is no upstream vendor licence, so nothing here can be revoked or repriced by a third party, and the cost of goods is zero.
The trade-off is inherited from the publishers: government statistics are lagged and revised, 13F is quarterly and stale by design, and none of this is market data. Those limits are stated plainly in SKILL.md rather than buried.
Correctness
Every tool was checked against live upstream data before shipping — not only against unit tests, because a test written from the same wrong assumption as the code passes happily.
That caught six real defects, including 13F values being 1000× too large by following SEC's own documentation, and Census silently returning five regional rows where a national figure was expected. Each is documented with the evidence that exposed it, and locked in by a regression test: VERIFICATION.md.
A failed call is never billed. The MCP SDK turns a thrown tool error into an HTTP 200 carrying isError: true; the payment gate inspects the result and returns errors unsettled rather than charging for a result the caller never received.
Architecture
Node-http-based). Stateless JSON.
- x402 v2 (@x402/core, @x402/evm) with the Coinbase CDP facilitator on Base mainnet.
- MCP on Workers via @hono/mcp StreamableHTTPTransport (the SDK's own transport is
PaymentGate.chargeAndRun, so money-safety rules cannot drift between them.
- Two entry points, one payment path. /mcp and /x402/ both run through
— every catalog entry is type: "http" — so an MCP endpoint alone can never be listed.
- Per-tool HTTP routes exist for discovery. The x402 Bazaar indexes plain HTTP resources only
payment configuration, so the server introspects cleanly on a fresh clone or in a CI sandbox.
- Discovery needs no secrets. initialize, tools/list and ping are answered without
Workers forbid, and the schema is a runtime input so it cannot be precompiled.
- Validation uses @cfworker/json-schema, not Ajv — Ajv compiles via Function, which
private-key- or seed-shaped input.
- No private keys. The server holds only a public payout address; config.ts refuses
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-11-03restoreB → Ascore 87
US Economic, SEC EDGAR & On-Chain Data (x402): common questions
- Is US Economic, SEC EDGAR & On-Chain Data (x402) MCP server safe?
- Yes, by our scan: it is graded A (87/100). Read the US Economic, SEC EDGAR & On-Chain Data (x402) safety report
- How do I install US Economic, SEC EDGAR & On-Chain Data (x402)?
- It runs remotely at x402.agentfund.net. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does US Economic, SEC EDGAR & On-Chain Data (x402) need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is US Economic, SEC EDGAR & On-Chain Data (x402) maintained?
- The last commit was 81 days ago (2026-08-15). The latest release is v0.2.0.
- Is US Economic, SEC EDGAR & On-Chain Data (x402) up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of US Economic, SEC EDGAR & On-Chain Data (x402)?
- Servers from other publishers that do the same job: EdgarTools MCP server.
- How does US Economic, SEC EDGAR & On-Chain Data (x402) compare with other MCP servers?
- safety score 87/100 (higher than 73% of 48,255 servers); tools 21 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to US Economic, SEC EDGAR & On-Chain Data (x402)
Same job from other publishers: the closest match first, then the best rated.
- EdgarToolsOpen-source SEC EDGAR toolkit — 13 tools, 7 prompts, every filing type. No API key required.not reviewedWidely usedA