_ index / mcp streamable-http

x402stock

https://x402stock.vercel.app

ccbcd43ec04063ba

api record

x402stock: real-time US stock market data plus options, crypto, forex, macro, SEC filings and alternative data — 143 endpoints. Flow: search_endpoints (find data) → get_endpoint (parameter docs) → call_endpoint (fetch it). Data calls are covered by an All-Access subscription key (unlimited calls) sent as "Authorization: Bearer sk_live_…" when this server was connected; check headroom with get_usage. Without a key, paid endpoints answer with subscribe instructions (or pay per call via x402 directly against https://x402stock.xyz).

endpoint
https://x402stock.vercel.app/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live

checked 11m ago

uptime
100%
latency
1,125ms

last good check

priced tools
0

of 4 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
1 open1 auth-required 2 never probed 2 of 4 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.

  • search_endpoints open 15h ago

    Search x402stock's 143 data endpoints (US stocks, options, crypto, forex, macro, SEC filings, alternative data) by keyword. Returns matching endpoints with method, path and a one-line summary. Start here, then use get_endpoint for parameter docs and call_endpoint to fetch data.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max results (default 12, max 50)."
    },
    "query": {
      "type": "string",
      "description": "Keywords, e.g. \"options chain\", \"insider trades\", \"inflation\". Omit to browse the whole catalog."
    }
  }
}
    arguments 13 lines
  • get_usage auth-required 15h ago

    Plan, status, and calls used this month for the API key this MCP server was connected with. Does not consume a call.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_endpoint unknown never probed

    Full documentation for one endpoint: description, path/query parameters with examples, and a ready-to-use example call. Pass the path from search_endpoints (template or concrete), e.g. "/api/v1/aggregates/{ticker}".

    mcp-tool

    {
  "type": "object",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "Endpoint path, e.g. \"/api/v1/quote/{ticker}\" or \"/api/v1/quote/AAPL\"."
    }
  }
}
    arguments 12 lines
  • call_endpoint unknown never probed

    Call a catalog endpoint and return its JSON. `path` must be concrete (real ticker/values substituted, e.g. "/api/v1/quote/AAPL"); pass query parameters via `query`. Covered by your subscription key (unlimited on All-Access). Note: AI-synthesis endpoints (research, report, filing-summary, smart screener, backtest) can take up to 60s.

    mcp-tool

    {
  "type": "object",
  "required": [
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "Concrete endpoint path, e.g. \"/api/v1/quote/AAPL\"."
    },
    "query": {
      "type": "object",
      "description": "Query parameters as key/value pairs, e.g. {\"timespan\": \"day\", \"limit\": 30}.",
      "additionalProperties": true
    }
  }
}
    arguments 17 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.

_ how we know
card completeness
80%

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.