Is stockmarketscan live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is stockmarketscan free to use?

Partly — some of its tools are open, others need a key or payment.

What tools does stockmarketscan have?

20 tools: search_setups, explain_concept, get_screener_data, get_stock_info, get_candles, get_chart_patterns, get_options_flow_timeline, get_stock_report, ….

Is stockmarketscan 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.

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

stockmarketscan

https://mcp.stockmarketscan.com

Registry code: 5978b3eaed780935

api record

StockMarketScan exposes US equity screeners, chart patterns, options flow and per-stock research.

Tool selection tips:

endpoint: https://mcp.stockmarketscan.com/mcp
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is stockmarketscan live?: Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is stockmarketscan free to use?: Partly — some of its tools are open, others need a key or payment.
What tools does stockmarketscan have?: 20 tools: search_setups, explain_concept, get_screener_data, get_stock_info, get_candles, get_chart_patterns, get_options_flow_timeline, get_stock_report, ….
Is stockmarketscan 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

99.8%

90 days 99.8%· all time 99.8%

latency

105ms

last good check

priced tools

of 20 tools

_ answered our checks, 90 days 562 checks · signed record

2026-10-21 00:06 degraded → live
2026-10-20 22:15 live → degraded· timeout after 20000ms
2026-10-12 10:46 degraded → live
2026-09-26 16:33 unknown → live

_ what it is for

topic: finance & markets stock & market data
used for: run us stock screeners
detect chart patterns for a stock
get unusual options activity
get a stock research report
get market breadth
takes → gives: text → data
tools: 20 reads

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 20 tools

2 open7 auth-required 11 never probed 9 of 20 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.

ping reads open 14h ago
Minimal sanity check. Returns { status, version, timestamp, cache_size }. No auth needed. Use this to verify the MCP server is reachable and responsive.

mcp-tool
{ "type": "object", "required": [], "properties": {} }
arguments 5 lines
list_screeners reads open 3h ago
Return metadata for all 24 stock screeners on the platform: slug, name, description, category, tier, whether the caller can read it, and its row fields with their JSON value types. Use this to discover which screeners are available before calling get_screener_data. Call this once per session; the list changes very rarely. Returns { data: [{ slug, name, description, category, tier, accessible, columns: [{ key, label, type, value_type }] }], meta: { caller_tier, total, accessible } }.

mcp-tool
{ "type": "object", "required": [], "properties": {} }
arguments 5 lines
get_market_momentum reads auth-required 11h ago
Return NYSE and NASDAQ market breadth: advancing/declining/unchanged issues, their percentages, and new highs/lows. Use when the user asks 'how's the market today' or 'is breadth strong'. Default (no params): last 7 trading days. Send either date or date_from/date_to (either end may be omitted). Returns { data: [{ data_date, exchange, advancing_issues, declining_issues, unchanged_issues, percent_advancing_issues, percent_declining_issues, percent_unchanged_issues, new_highs, new_lows }], meta: { as_of } }; all counts and percents are numbers (63 means 63%). Two rows per date (NYSE + NASDAQ). Tier: Basic+.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Single day (YYYY-MM-DD)" }, "date_to": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Range end" }, "date_from": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Range start" } }, "additionalProperties": false }
arguments 22 lines

get_options_flow_overview reads auth-required 3h ago

Return the daily options flow table for one trading day: aggregated call/put volume, premium, implied volatility, and consecutive-day streaks for every notable symbol. Use when the user asks 'what's the options flow today' or 'show me the largest premium'. Each row includes call_put_volume_ratio (> 1.0 means more call than put volume), consecutive_days (streak length), total_premium (dollar size), call_avg_iv/put_avg_iv. Returns { data: [...], meta: { as_of, market_stats, available_dates, pagination: { next_cursor } } }. Tier: Pro only. Basic users get 403.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Trading day (YYYY-MM-DD). Default = latest available day."
    },
    "sort": {
      "enum": [
        "streak",
        "volume",
        "callput",
        "premium"
      ],
      "type": "string",
      "default": "streak",
      "description": "Sort order: streak=longest streaks first, volume=highest volume, callput=most extreme C/P, premium=biggest dollar"
    },
    "limit": {
      "type": "integer",
      "default": 100,
      "maximum": 500,
      "minimum": 1,
      "description": "Rows to return (max 500)"
    },
    "cursor": {
      "type": "string",
      "minLength": 1,
      "description": "meta.pagination.next_cursor from the previous page"
    }
  },
  "additionalProperties": false
}

arguments 35 lines

get_options_flow_ranked reads auth-required 17h ago
Return ranked options flow records for a date range: the records that stand out by long consecutive-day streaks, large premium, and screener confluence. Each record includes data-only performance tracking measured from a realistic entry reference: entry_price = open of the trading day AFTER signal_date (the close of signal_date is not an available fill price). max_gain_pct/max_drawdown_pct/price_change_pct are computed against entry_price; if that day's US open hasn't happened yet, these fields and entry_price are null ('pending'). This is descriptive market data for your own research, not a recommendation. If date_from/date_to omitted, returns last 60 days. Returns { data: [...], meta: { as_of, pagination: { next_cursor }, parameters: { date_from, date_to } } }. Dates are YYYY-MM-DD and numbers are JSON numbers. Tier: Pro only.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "limit": { "type": "integer", "default": 500, "maximum": 2000, "minimum": 1, "description": "Max records returned (default 500)" }, "cursor": { "type": "string", "minLength": 1, "description": "meta.pagination.next_cursor from the previous page" }, "date_to": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "End date (YYYY-MM-DD)" }, "date_from": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Start date (YYYY-MM-DD)" } }, "additionalProperties": false }
arguments 29 lines
get_options_flow_sentiment reads auth-required 17h ago
Return daily options market sentiment: one row per trading day. Combines NYSE/NASDAQ market breadth (advance/decline + new highs/lows) with the market-wide call/put ratio. Each row includes market_breadth_score (0-100), market_call_put_ratio, the daily filter context (bullish_only/bearish_only/mixed), bullish_count/bearish_count of flow records that day, plus a derived sentiment_score (0-100) and sentiment_label (bullish/neutral/bearish). Use when the user asks 'what's market sentiment today', 'how bullish is the market', 'show me sentiment over the last week'. If date_from/date_to omitted, returns last 60 days. Returns { data: [...], meta: { as_of, pagination } }. Tier: Pro only.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "cursor": { "type": "string", "minLength": 1, "description": "meta.pagination.next_cursor from the previous page" }, "date_to": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "End date (YYYY-MM-DD)" }, "date_from": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "Start date (YYYY-MM-DD)" } }, "additionalProperties": false }
arguments 22 lines

get_trend_connections reads auth-required 11h ago

Return AI-computed connections between trending topics across categories (tech → patents, tech → funding, etc). Useful for spotting meta-trends. Use when the user asks 'what trends are connected' or 'show me cross-category signals'. Use one of latest, date, or days. Returns { data: [{ date, source_category, source_topic, target_category, target_topic, strength, rationale }], meta: { as_of } }. Tier: Pro only.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
    },
    "days": {
      "type": "integer",
      "default": 14,
      "maximum": 90,
      "minimum": 1
    },
    "limit": {
      "type": "integer",
      "default": 200,
      "maximum": 1000,
      "minimum": 1,
      "description": "Max connections returned (default 200)"
    },
    "latest": {
      "type": "boolean",
      "default": false
    }
  },
  "additionalProperties": false
}

arguments 28 lines

get_trends reads auth-required 11h ago

Return AI-detected trending topics in tech & science, patents, or funding events. Use when the user asks 'what's trending in tech' or 'show me patent trends'. Use one of latest, date, or days. Returns { data: [{ date, topic, weight }], meta: { as_of } } where weight is 0-1. Tier: Pro only.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Exact date lookup"
    },
    "days": {
      "type": "integer",
      "default": 10,
      "maximum": 180,
      "minimum": 1,
      "description": "Lookback window"
    },
    "latest": {
      "type": "boolean",
      "default": false,
      "description": "If true, only return most recent day"
    },
    "category": {
      "enum": [
        "techscience",
        "patents",
        "fundingevents"
      ],
      "type": "string",
      "default": "techscience",
      "description": "Trend category"
    }
  },
  "additionalProperties": false
}

arguments 34 lines

get_unusual_options_activity reads auth-required 3h ago

Return individual options contracts flagged as unusual activity (Vol/OI > 1.5). Each row is one contract, not one stock. Use when the user wants contract-level detail. Filter by symbol, side (call/put/both), minimum vol/oi, minimum premium, or max days to expiration. For aggregated stock-level flow use get_options_flow_overview instead. Returns { date, count, contracts: [...], next_cursor }.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "side": {
      "enum": [
        "call",
        "put",
        "both"
      ],
      "type": "string",
      "default": "both"
    },
    "limit": {
      "type": "integer",
      "default": 300,
      "maximum": 1000,
      "minimum": 1
    },
    "cursor": {
      "type": "string",
      "minLength": 1,
      "description": "meta.pagination.next_cursor from the previous page"
    },
    "symbol": {
      "type": "string",
      "pattern": "^[A-Z0-9.^=\\-]{1,20}$",
      "description": "Filter to one symbol"
    },
    "max_dte": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 0
    },
    "min_vol_oi": {
      "type": "number",
      "default": 1.5,
      "minimum": 0
    },
    "min_premium_usd": {
      "type": "number",
      "default": 25000,
      "minimum": 0
    }
  },
  "additionalProperties": false
}

arguments 47 lines

search_setups reads unknown never probed
List today's options flow records for one side (bullish or bearish), ranked by a descriptive composite score (strength score + consecutive-day streak + premium size). Use when the user asks which symbols had the most notable options flow today. This is descriptive market data, not a recommendation. Summarize the first few rows rather than dumping the raw JSON. Use get_stock_report to look at a single symbol in more detail. Returns { side, date, count, setups: [{ symbol, score, signal: { type, strength, consecutive_days, call_put_ratio, total_premium } }] }.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "side": { "enum": [ "bullish", "bearish" ], "type": "string", "default": "bullish", "description": "Side of setups to return" }, "limit": { "type": "integer", "default": 20, "maximum": 100, "minimum": 1, "description": "Max setups to return" } }, "additionalProperties": false }
arguments 23 lines
explain_concept reads unknown 17h ago
Return a plain-language explanation of a platform-specific term, metric, or screener. Use ONLY for terms that are specific to StockMarketScan (e.g. 'strength_score' which is our internal scoring, or 'hot_prospects' which is our curated screener). Do NOT use for generic finance terms the model already knows: answer those directly. Returns { term, title, explanation, interpretation, related_terms }.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "term" ], "properties": { "term": { "type": "string", "minLength": 1, "description": "Term to explain, e.g. 'call_put_ratio', 'golden_cross', 'consecutive_days', 'strength_score', 'vol_oi_ratio', 'streak'" } }, "additionalProperties": false }
arguments 15 lines
get_screener_data reads unknown 25h ago
Return the rows of a single stock screener for its latest snapshot. Use this when the user asks about a specific screener like 'hot prospects' or 'golden cross'. Common slugs: hot-prospects, golden-cross, death-cross, rsi-oversold, rsi-overbought, defensive-stocks, dividend-prospects, j-pattern, nearing-6-month-highs, week-52-high-top-picks, top-penny-pops, strong-volume-gains, top-tech-stocks, fundamentally-fine, income-and-growth, best-reits. If you don't know the slug, call list_screeners first. Numbers are JSON numbers (percent_change 1.25 means +1.25%), dates are YYYY-MM-DD. Returns { data: [rows], meta: { as_of, screener, pagination: { next_cursor, total } } }. For the next page pass meta.pagination.next_cursor as cursor.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "slug" ], "properties": { "slug": { "type": "string", "minLength": 1, "description": "The screener slug, e.g. 'hot-prospects', 'golden-cross', 'rsi-oversold'" }, "limit": { "type": "integer", "default": 50, "maximum": 500, "minimum": 1, "description": "Rows per page (max 500)" }, "cursor": { "type": "string", "minLength": 1, "description": "meta.pagination.next_cursor from the previous page. Omit for the first page." } }, "additionalProperties": false }
arguments 27 lines
get_stock_info reads unknown 25h ago
Return basic metadata for a stock: full company name, exchange, industry, last price, and daily percent change. Use this when you first encounter a symbol and need to identify it. Lighter than get_stock_report (composite) or get_candles (full history). Returns { data: { symbol, symbol_name, last_price, percent_change, exchange, industry }, meta: { as_of } }; percent_change 1.27 means +1.27%. Returns NOT_FOUND for unknown tickers.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "pattern": "^[A-Z0-9.^=\\-]{1,20}$", "description": "Stock ticker, e.g. AAPL" } }, "additionalProperties": false }
arguments 15 lines

get_candles reads unknown 6h ago

Return OHLCV price candles for a single stock, oldest first. Use when you need price history to compute indicators or answer 'how much is X up this month'. date is the trading day (YYYY-MM-DD; weekly candles use the Monday). Default range is 6mo. Use larger ranges like '1y' or '2y' only when the user explicitly asks for long history; max range is 20 years. Returns { data: [{ date, open, high, low, close, volume }], meta: { as_of, pagination: { total } } }.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "symbol"
  ],
  "properties": {
    "range": {
      "type": "string",
      "default": "6mo",
      "description": "Range: 1d, 5d, 1y, 2y, 5y, max, or {N}mo (1-240)"
    },
    "symbol": {
      "type": "string",
      "pattern": "^[A-Z0-9.^=\\-]{1,20}$",
      "description": "Stock ticker"
    },
    "interval": {
      "enum": [
        "1d",
        "1wk"
      ],
      "type": "string",
      "default": "1d",
      "description": "Daily or weekly candles"
    }
  },
  "additionalProperties": false
}

arguments 29 lines

get_chart_patterns reads unknown 6h ago
Return all chart patterns currently detected for a single stock symbol. Detectable pattern ids: double_top, double_bottom, triple_top, triple_bottom, head_shoulders, inv_head_shoulders, round_bottom, cup_handle, asc_triangle, desc_triangle, sym_triangle, channel_up, channel_down, rectangle, flag, wedge_rising, wedge_falling, abcd, gartley, bat, butterfly, crab, impulse_wave, corrective_wave. Use when the user asks 'what patterns does X have' or 'is X forming a head and shoulders'. Requires a Basic or Pro API key. Returns { data: { symbol, interval, computed_at, candle_count, patterns: [{ id, name, type, category, confidence, points, lines, target_price, last_structural_point }] } } where type is the pattern direction (bullish, bearish, neutral). Empty patterns array if none detected.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "pattern": "^[A-Z0-9.^=\\-]{1,20}$", "description": "Stock ticker, e.g. AAPL, TSLA, MSFT" }, "interval": { "enum": [ "1d", "1wk" ], "type": "string", "default": "1d", "description": "Chart interval" } }, "additionalProperties": false }
arguments 24 lines

get_options_flow_timeline reads unknown 6h ago

Return the historical options flow for a single stock: most recent days first. Use when the user asks 'show me X's options flow history' or 'how long has X been bullish'. Returns { data: [daily rows, newest first], meta: { as_of, pagination: { next_cursor } } }. Tier: Pro only.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "symbol"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 60,
      "maximum": 365,
      "minimum": 1,
      "description": "Days of history (max 365)"
    },
    "cursor": {
      "type": "string",
      "minLength": 1,
      "description": "meta.pagination.next_cursor from the previous page"
    },
    "symbol": {
      "type": "string",
      "pattern": "^[A-Z0-9.^=\\-]{1,20}$",
      "description": "Stock ticker"
    }
  },
  "additionalProperties": false
}

arguments 27 lines

get_stock_report reads unknown 25h ago
Return a comprehensive report on a single stock in one call: metadata, screener appearances, chart patterns, options flow, signal status, price summary, and upcoming earnings. THIS IS THE PREFERRED FIRST TOOL when a user asks about a single stock. It replaces 5-7 separate tool calls (get_stock_info + get_chart_patterns + get_options_flow_timeline + get_options_flow_ranked + screener lookups + get_candles). Do NOT also call the primitives after calling this: the composite already has everything. Parallel fetch under the hood, graceful partial failures (if one source errors, that section returns null with a note). Returns { symbol, as_of, info, screeners, patterns, options_flow, signal, candle_summary, overall_bias }. overall_bias is a heuristic hint, not financial advice.

mcp-tool
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "symbol" ], "properties": { "symbol": { "type": "string", "pattern": "^[A-Z0-9.^=\\-]{1,20}$", "description": "Stock ticker, e.g. AAPL" }, "interval": { "enum": [ "1d", "1wk" ], "type": "string", "default": "1d", "description": "Pattern detection interval" } }, "additionalProperties": false }
arguments 24 lines

search_patterns reads unknown 21h ago

Find all stocks across one or more screeners that currently exhibit specific chart patterns. Much faster than calling get_chart_patterns in a loop. Use when the user asks 'which stocks have a cup and handle' or 'find me hot prospects with bullish reversal patterns'. Requires a Basic or Pro API key; unknown slugs or pattern ids and screeners above the plan are errors. Results are capped per screener group via `limit` (default 100); capped groups carry truncated: true. Returns { data: [{ screener_slug, screener_name, count, truncated, stocks: [{ symbol, symbol_name, last_price, volume, data_date, matched_patterns }] }], meta: { total_unique_stocks } }.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "screener_slugs"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 100,
      "maximum": 500,
      "minimum": 1,
      "description": "Max matching stocks per screener group (default 100)"
    },
    "interval": {
      "enum": [
        "1d",
        "1wk"
      ],
      "type": "string",
      "default": "1d",
      "description": "Chart interval"
    },
    "pattern_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "default": [],
      "description": "Pattern ids to filter by. Empty = all patterns. Valid ids: double_top, double_bottom, triple_top, triple_bottom, head_shoulders, inv_head_shoulders, round_bottom, cup_handle, asc_triangle, desc_triangle, sym_triangle, channel_up, channel_down, rectangle, flag, wedge_rising, wedge_falling, abcd, gartley, bat, butterfly, crab, impulse_wave, corrective_wave"
    },
    "screener_slugs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 24,
      "minItems": 1,
      "description": "Screener slugs to search within"
    }
  },
  "additionalProperties": false
}

arguments 43 lines

search_stocks reads unknown 21h ago

Search for stocks by ticker prefix or company name. THE tool to use when the ticker is unknown ('what's the symbol for Palantir?') or ambiguous: resolve the name to a symbol here, then use get_stock_info / get_stock_report with the symbol. No API key required. Returns { data: [{ symbol, name }], meta } ordered by best match.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Max results (default 10)"
    },
    "query": {
      "type": "string",
      "maxLength": 60,
      "minLength": 1,
      "description": "Symbol prefix or part of the company name, e.g. 'Apple' or 'NVD'"
    }
  },
  "additionalProperties": false
}

arguments 23 lines

search_stocks_in_screeners reads unknown 21h ago

Find stocks that appear in multiple screeners simultaneously. Useful for finding overlap across screeners. Use when the user asks 'which stocks are in both X and Y' or 'find stocks in 3+ bullish screeners'. Returns { screeners_queried, mode, count, symbols: [{symbol, screeners, match_count}] }. Intersection mode returns only stocks in ALL listed screeners; union returns stocks in ANY.

mcp-tool

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "screener_slugs"
  ],
  "properties": {
    "mode": {
      "enum": [
        "intersection",
        "union"
      ],
      "type": "string",
      "default": "intersection",
      "description": "intersection = stocks in ALL screeners; union = stocks in ANY screener"
    },
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 500,
      "minimum": 1
    },
    "screener_slugs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 24,
      "minItems": 1,
      "description": "List of screener slugs to query (1-24)"
    }
  },
  "additionalProperties": false
}

arguments 34 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.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
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.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5978b3eaed780935.

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

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/5978b3eaed780935/badge.svg)](https://brick.blue/agent/5978b3eaed780935?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

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.