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

io.stockmap/stockmap

https://stockmap.io

Registry code: 2da1e658ba735757

api record

StockMap's tools answer questions about how US stocks, sectors and the market look, from a model's nightly 14-day calls and how its past calls did, whether or not the person names StockMap: stock_call for one stock, compare_stocks for two to five side by side, market_map for the market and which sectors lead or lag, sector for one sector or industry, and last_night for what changed overnight. Show the not-advice line and the run date with each answer.

endpoint
https://stockmap.io/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
0 · newcomer
_ is it live, free and safe measured by this hub
Is io.stockmap/stockmap live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is io.stockmap/stockmap free to use?
Yes — the hub reached it with no key and no payment.
What tools does io.stockmap/stockmap have?
12 tools: stock_call, compare_stocks, last_night, market_map, sector, bitcoin_test, my_watchlists, watch, ….
Is io.stockmap/stockmap 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 100%· all time 100%

latency
248ms

last good check

priced tools
0

of 12 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 12 tools
3 open 9 never probed 3 of 12 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.

  • crypto_today open 2h ago

    Why crypto is up or down today, from StockMap's Crypto today page: Bitcoin's 24-hour move, how many coins beat it, funding, and the hour's paragraph, every number with its source. Market data with no call on any coin. Show the stamp, the sources and the not-advice line with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "crypto_todayArguments",
      "properties": {}
    }
    arguments 5 lines
  • crypto_stocks open 2h ago

    Which US crypto stocks StockMap's model leans on: how many it leans outperform, neutral or underperform, how many of its graded two-week windows on them were right, and Bitcoin's move since the last US close. The calls are the stock model's, on the stocks, never on coins. Show the stamp, the sources and the not-advice line with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "crypto_stocksArguments",
      "properties": {}
    }
    arguments 5 lines
  • is_it_altseason open 2h ago

    Is it altseason: how many of the top-100 coins (stablecoins out) beat Bitcoin over the last 7 days, beside how many lag it in a typical week, from StockMap's Altseason page. Market data with no call on any coin. Show the stamp, the sources and the not-advice line with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "is_it_altseasonArguments",
      "properties": {}
    }
    arguments 5 lines
  • stock_call unknown never probed

    StockMap's call on one US stock, by symbol or company name: the model's nightly 14-day call, the strongest reasons for and against, how its past calls on the stock did, the price and the day's change, and what changed last night. Use it when someone asks how a US stock looks, whether it is strong or weak right now, or what to make of it, whether or not they name StockMap. Show the not-advice line and the run date with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "stock_callArguments",
      "required": [
        "stock"
      ],
      "properties": {
        "stock": {
          "type": "string",
          "title": "Stock",
          "description": "A US stock's symbol (NVDA, BRK.B) or its company name (Nvidia)"
        }
      }
    }
    arguments 14 lines
  • compare_stocks unknown never probed

    StockMap's calls on two to five US stocks side by side, by symbol or company name: each stock's nightly 14-day call, whether it changed last night, the insights for and against it, and how the model's past calls on it did. Use it when someone asks how two to five US stocks stack up against each other, or which of them looks stronger, whether or not they name StockMap. Show the not-advice line and the run date with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "compare_stocksArguments",
      "required": [
        "stocks"
      ],
      "properties": {
        "stocks": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "title": "Stocks",
          "maxItems": 5,
          "description": "Two to five US stocks, each by symbol (NVDA, BRK.B) or company name (Nvidia)"
        }
      }
    }
    arguments 18 lines
  • last_night unknown never probed

    What changed in StockMap's calls last night: how many stocks' calls changed band on the market map and the biggest of them, the calls graded last night (made 14 days earlier) with one line on why each was right or wrong, and when the next run starts. Show the not-advice line and the run date with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "last_nightArguments",
      "properties": {}
    }
    arguments 5 lines
  • market_map unknown never probed

    The US stock market on StockMap's map: the 11 sectors, each with its share of the market, its 2-week lean from the model's nightly calls on its stocks, its move on the day and its best and worst stock. A summary, not every stock. Use it when someone asks how the US market looks, or which sectors lead or lag, whether or not they name StockMap. Show the not-advice line and the run date with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "market_mapArguments",
      "properties": {}
    }
    arguments 5 lines
  • sector unknown never probed

    StockMap's read of one US sector or industry, by name (Information Technology, semiconductors, banks): its 2-week lean from the model's nightly calls, how its stocks' calls split, its industries, and its largest stocks with each one's call and move on the day. Use it when someone asks how a US sector or industry looks, or which of its stocks look strong or weak, whether or not they name StockMap. Show the not-advice line and the run date with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "sectorArguments",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "title": "Name",
          "description": "A US sector or industry by name: Information Technology, Health Care, semiconductors, banks, software"
        }
      }
    }
    arguments 14 lines
  • bitcoin_test unknown never probed

    Did the person's coins beat Bitcoin: their holdings as they would paste them on StockMap's Bitcoin test page ("ETH 2, SOL 40 since Jan 15"), priced then and now beside the same dollars held in Bitcoin, from CoinGecko's prices. Nothing is stored. Market data with no call on any coin. Show the stamp, the sources and the not-advice line with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "bitcoin_testArguments",
      "required": [
        "holdings"
      ],
      "properties": {
        "since": {
          "anyOf": [
            {
              "type": "string",
              "format": "date"
            },
            {
              "type": "null"
            }
          ],
          "title": "Since",
          "default": null,
          "description": "When they bought, for holdings the paste gives no date (the page's \"Held since\"), YYYY-MM-DD"
        },
        "holdings": {
          "type": "string",
          "title": "Holdings",
          "maxLength": 4000,
          "minLength": 1,
          "description": "The coins and amounts as the person would paste them, with a date if they gave one: \"ETH 2, SOL 40, DOGE 10000 since Jan 15\""
        }
      }
    }
    arguments 30 lines
  • my_watchlists unknown never probed

    The signed-in person's StockMap watchlists: each list's stocks with the model's call on each, the calls that changed last night first. Show the not-advice line and the run date with the answer.

    mcp-tool

    {
      "type": "object",
      "title": "my_watchlistsArguments",
      "properties": {}
    }
    arguments 5 lines
  • watch unknown never probed

    Add a US stock to the signed-in person's StockMap watchlist: to the list named (made if it is new) or their first list. A stock is on one list at a time, so naming another list moves it.

    mcp-tool

    {
      "type": "object",
      "title": "watchArguments",
      "required": [
        "stock"
      ],
      "properties": {
        "stock": {
          "type": "string",
          "title": "Stock",
          "description": "A US stock's symbol (NVDA, BRK.B) or its company name (Nvidia)"
        },
        "watchlist": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Watchlist",
          "default": null,
          "description": "The list's name, made if the person has none by that name; left out, their first list"
        }
      }
    }
    arguments 27 lines
  • unwatch unknown never probed

    Remove a US stock from the signed-in person's StockMap watchlists.

    mcp-tool

    {
      "type": "object",
      "title": "unwatchArguments",
      "required": [
        "stock"
      ],
      "properties": {
        "stock": {
          "type": "string",
          "title": "Stock",
          "description": "A US stock's symbol (NVDA, BRK.B) or its company name (Nvidia)"
        }
      }
    }
    arguments 14 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 2da1e658ba735757.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2da1e658ba735757/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/2da1e658ba735757/badge.svg)](https://brick.blue/agent/2da1e658ba735757?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.