_ registry / mcp streamable-http · checked 1h ago

alpha402x-research

https://alpha402x.com

Registry code: aae59056dc6e6d41

api record

alpha402x publishes original, cited equity research that an agent can buy per call over the x402 protocol (USDC on Base) — no account, no API key. These tools are free: browse the catalog (list_research), read a product's exact payment terms (get_product_terms), check 10-Q coverage for any U.S. ticker (check_10q_coverage), pull a COMPLETE sample card free in the exact schema the paid cards return (get_sample_card), look up a three-year line-item trajectory sheet (get_line_item_trajectory), find a company's 10-K/10-Q filing bundle — filing HTML plus IS/BS/CF workbook as a ZIP…

endpoint
https://alpha402x.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is alpha402x-research live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is alpha402x-research free to use?
Yes — the hub reached it with no key and no payment.
What tools does alpha402x-research have?
7 tools: how_to_pay_x402, check_10q_coverage, get_line_item_trajectory, list_research, get_product_terms, get_sample_card, get_sec_filing_bundle.
Is alpha402x-research safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.3%· all time 99.5%

latency
673ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 768 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • buy cited equity research
  • get three-year financial statements
  • check 10-q coverage for a ticker
  • download an sec filing bundle
takes → gives
text → data, documents
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 11 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
4

distinct

settlements
11

last 2026-11-04

received on chain
0.75 USDC

no flags

_ what it can do 7 tools
6 open 1 never probed 6 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_10q_coverage reads open 4h ago

    Free coverage check against SEC EDGAR for any U.S. ticker: confirms whether 10-Q Highlights can serve it, lists available fiscal periods (newest first), and returns the payable URLs. No charge; the paid product is the extraction itself.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker"
      ],
      "properties": {
        "period": {
          "type": "string",
          "description": "Optional fiscal period like fy2026-q1; checks that this dated variant exists"
        },
        "ticker": {
          "type": "string",
          "description": "U.S. ticker symbol, e.g. AAPL"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • get_line_item_trajectory reads open 4h ago

    Three fiscal years of income statement, balance sheet and cash flow lines for one company, in one standard layout, scaled to revenue, with per-year slopes where computed. Levels and slopes only. AMD and AVGO return the COMPLETE sheet free, in the exact schema every paid sheet uses. Any other covered ticker returns its payable URL and x402 terms ($0.05 per call). Tickers outside the covered list return not_covered.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker"
      ],
      "properties": {
        "ticker": {
          "type": "string",
          "description": "A covered ticker, e.g. AMD (free), AVGO (free) or AAPL (paid)"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • list_research reads open 16h ago

    The full alpha402x catalog: every payable research product (empirical multibagger profiles, fiscal-year-end WACC builds, 10-Q highlight extractions, quarterly quantitative and qualitative cards) with prices, payable URLs, and free guide pages. All prices are USDC per call over x402.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • get_product_terms reads open 16h ago

    Exact x402 payment terms for one payable URL or product path (price, asset, network, payTo, scheme). The live 402 response's PAYMENT-REQUIRED header remains the authoritative terms document; this tool mirrors the same constants the gates are built from.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product"
      ],
      "properties": {
        "product": {
          "type": "string",
          "description": "A payable path or URL, e.g. /10q-highlights/AAPL, /wacc-build/AAPL/fye-2025-09-27, /quarterly-quant-card/AMD/fy2026-q2, /quarterly-qual-card/AMD/fy2026-q2, /profiles/100x-floor, /5x-stock-empirical-profile"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_sample_card reads open 16h ago

    One COMPLETE quarterly card, free — the identical payload the paid route returns for that card, not a trimmed preview. Two company-quarters (AMD fy2026-q2, MRVL fy2027-q2) are published free in both the quantitative and qualitative families, in the exact schema and field names every paid card uses, so a parser written against a sample works unchanged against any card you buy. Use it as a zero-cost integration test before paying for coverage. Any other ticker returns not_a_sample.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker"
      ],
      "properties": {
        "family": {
          "enum": [
            "quantitative",
            "qualitative"
          ],
          "type": "string",
          "description": "Which card family to return. Defaults to quantitative."
        },
        "ticker": {
          "type": "string",
          "description": "AMD or MRVL — the two company-quarters published free"
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
  • get_sec_filing_bundle reads open 4h ago

    One company's SEC 10-K or 10-Q as a ZIP: the filing HTML as filed, the SEC-rendered consolidated statements in a workbook (IS, BS, CF where present; the manifest names the sheets, and a two-sheet workbook is disclosed on the bundle), a manifest naming the accession, and a pointer to the quarterly cards for the same filing. Source material only; nothing inferred. Lists every bundle held for the ticker with its free manifest URL; AMD, MRVL, AVGO and MRCY are free in full. Other bundles return their payable URL and x402 terms ($0.05 each). Tickers with no bundle return not_covered. The ZIP bytes themselves are only served over the HTTP routes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Optional bundle slug like 10q-2026-06-27 or 10k-2026-07-03; defaults to listing every bundle held for the ticker"
        },
        "ticker": {
          "type": "string",
          "description": "U.S. ticker, e.g. AMD (free), AAPL (paid)"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • how_to_pay_x402 reads unknown never probed

    The x402 payment flow for these products, the client libraries that automate it, and where the authoritative terms live.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id aae59056dc6e6d41.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/aae59056dc6e6d41/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/aae59056dc6e6d41/badge.svg)](https://brick.blue/agent/aae59056dc6e6d41?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.