_ registry / mcp streamable-http · checked 50m ago

stormap

https://stormap.ai

Registry code: 21a1c344440bb4b1

api record

Stormap: read-only checks from public sources. Software: package_check (is an npm or PyPI package safe to install), vendor_trust_profile (vendor security and privacy claims). Companies: company_profile, company_changes (pricing, terms and privacy page history), email_domain_check, agentic_commerce_readiness. Payments: check_before_paying (vet an x402 seller or wallet), find_best_api (which paid API fits a task), x402_market_report. US stocks, facts only: why_is_it_moving (SEC filings behind a move), trading_halts. Ideas: brainstorm_ideas (scored ideas plus an interactive map). Web: read_url…

endpoint
https://stormap.ai/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 stormap live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is stormap free to use?
Yes — the hub reached it with no key and no payment.
What tools does stormap have?
19 tools: search_guides, get_guide, ai_visibility_score, check_ai_crawler_access, generate_llms_txt, generate_ai_robots_txt, x402_market_report, vendor_trust_profile, ….
Is stormap 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.8%· all time 99.8%

latency
502ms

last good check

priced tools
13

of 19 tools

_ answered our checks, 90 days 431 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • score a page's ai visibility
  • check ai crawler access
  • generate llms.txt
  • generate ai robots.txt rules
  • search guides on ai agents
takes → gives
web pages, text → data, text
tools
6 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 14 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
7

distinct

settlements
14

last 2026-11-17

received on chain
0.14 USDC

no flags

_ what it can do 19 tools
13 paid1 open 5 never probed 14 of 19 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.

  • x402_market_report 0.01 USDC paid never probed

    What paid AI-agent tools cost and who sells the most, from an hourly index of Coinbase's x402 marketplace (about 38,000 pay-per-call endpoints). For a category or a search phrase: the typical price that paying wallets actually accept (median, middle range, top 10%), a price distribution, the top sellers by distinct paying wallets in the last 30 days, new listings this week that are already being paid, and how concentrated the market is. Use it to price your own x402 endpoint, or to pick which paid tool to call.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "How many top sellers and new listings to return (default 10)."
        },
        "query": {
          "type": "string",
          "description": "Optional search phrase matched against listing names, descriptions and URLs, e.g. \"transcription\" or \"weather\"."
        },
        "category": {
          "enum": [
            "web_search",
            "email",
            "enrichment",
            "scraping",
            "llm",
            "image",
            "audio",
            "documents",
            "news",
            "weather",
            "market_data",
            "onchain",
            "domain_security",
            "other"
          ],
          "type": "string",
          "description": "Optional category, e.g. \"scraping\", \"web_search\", \"llm\", \"market_data\", \"onchain\". Omit for the whole marketplace plus a per-category table."
        }
      },
      "additionalProperties": false
    }
    arguments 36 lines
  • vendor_trust_profile 0.01 USDC paid never probed

    Vendor security review / third-party risk check: a first-pass security and privacy profile of a software vendor from its own public website, given a domain. Answers "is this vendor SOC 2 certified?" and "do they train AI on our data?": certifications it claims (SOC 2 Type I/II, ISO 27001/27701/42001, HIPAA, PCI DSS, FedRAMP…), whether it trains AI models on customer data (with the exact quote and page), subprocessor list, DPA, data residency, security features (SSO/SAML, SCIM, MFA, encryption, pen tests, bug bounty), security.txt contact, status page, links to trust center, privacy policy and terms, plus a 0-100 transparency score. Use for vendor risk assessments, procurement and security questionnaires. Certifications are vendor claims, not verified audits.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Vendor domain, e.g. \"notion.com\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • company_changes 0.01 USDC paid never probed

    Did they raise prices or change their terms? What changed on a company's pricing, terms of service, privacy policy and subprocessor pages, and when. Returns the change history (prices added/removed, free plan or trial added/removed, subprocessors added/removed, text added/removed) and the current prices. Stormap checks tracked pages about once a day; asking about a new company starts tracking it, so history builds from that day. Useful for competitor monitoring, vendor renewals and compliance.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Company domain, e.g. \"linear.app\"."
        },
        "since_days": {
          "type": "integer",
          "default": 365,
          "maximum": 3650,
          "minimum": 1,
          "description": "Only return changes from the last N days."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • agentic_commerce_readiness 0.01 USDC paid never probed

    Audit whether an online store is ready for AI shopping agents (ACP, UCP, Perplexity, Claude and others): AI bot access to product pages, Product structured data (price, currency, availability, GTIN/MPN, brand, ratings), return policy and shipping details, policy pages, product sitemap/feed, platform and Stripe detection, and agent protocol discovery files (/.well-known/ucp, /.well-known/acp.json, MCP server card). Covers agent checkout protocols such as ACP (used by ChatGPT Instant Checkout) and UCP (used by Google AI Mode). Returns a 0-100 score, readiness level and a prioritized fix list.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Store domain or a product page URL, e.g. \"allbirds.com\" or \"https://shop.example.com/products/blue-mug\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • company_profile 0.01 USDC paid never probed

    Company profile from a domain: a one-line summary, what the company does, founded, headquarters, industry, employee count, founders, parent company, public listing (ticker, exchange, SEC business address and industry), key pages (pricing, docs, contact, careers, status), social profiles, current prices with the date seen, tech stack, role contact emails, domain age and mail provider, and AI-readiness. From the company's own website plus Wikidata, SEC EDGAR, RDAP and DNS.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Company domain or homepage URL, e.g. \"stripe.com\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • check_before_paying 0.01 USDC paid never probed

    Should your agent pay this? Run before paying an x402 / pay-per-call endpoint, an unfamiliar seller or a wallet address. Returns a verdict (ok_to_pay, caution, dont_pay, no_payment_needed) with reasons, from: the endpoint's live payment terms (price, token, payment address), its listing in Coinbase's x402 marketplace (how many different wallets paid it in 30 days, listed payment address), whether the live payment address matches the listing, whether the token is real USDC, the price compared with typical prices for similar tools, and the seller domain's age, website and mail security. Read-only: never pays or signs anything.

    mcp-tool

    {
      "type": "object",
      "required": [
        "target"
      ],
      "properties": {
        "target": {
          "type": "string",
          "description": "Paid endpoint URL (e.g. \"https://api.example.com/v1/search\"), seller domain (e.g. \"example.com\") or wallet address (0x...)."
        },
        "amount_usd": {
          "type": "number",
          "description": "Optional: the amount in USD you are about to pay, to check it against what the endpoint asks for."
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • package_check 0.01 USDC paid never probed

    Before installing an npm or PyPI package: does it exist (AI-suggested names are sometimes made up, and attackers register them), has it been reported as malicious, which known vulnerabilities affect this version (with the fixed version), is it deprecated or yanked, how old is it, does it run code on install, how many downloads, and does its name imitate a popular package (typosquat). Verdict: ok_to_install, caution, dont_install or does_not_exist, with reasons. From OSV.dev, deps.dev, the npm registry and PyPI.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Package name, optionally with a version: \"lodash\", \"[email protected]\", \"@scope/pkg\", \"requests==2.31.0\"."
        },
        "version": {
          "type": "string",
          "description": "Optional version to check (default: latest)."
        },
        "ecosystem": {
          "enum": [
            "npm",
            "pypi"
          ],
          "type": "string",
          "description": "npm (default) or pypi."
        }
      },
      "additionalProperties": false
    }
    arguments 25 lines
  • why_is_it_moving 0.01 USDC paid never probed

    For a US stock ticker: the likely catalysts behind a move, from primary sources, in seconds. Ranks the last 48 hours (adjustable) of SEC filings: 8-K events decoded into plain English (deals, earnings, new debt, unregistered share sales, delisting notices, management changes), the press-release headline from Exhibit 99.1, offerings and shelf registrations (dilution), insider open-market buys and sells from Form 4 (who, shares, price, value), 5%+ stakes (13D/13G); plus whether the stock is halted or was halted today and why. Each item has its time, a link to the filing and why it ranks where it does; filing bursts say which filing to read first. An explicit answer status (filing_found, news_halt_no_filing_yet, unexplained_by_primary_sources) and a coverage block (window searched, when each source was last checked, latest filing date) let an agent tell "nothing filed" apart from "a source failed". Facts only: no price data and no buy/sell opinions.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ticker"
      ],
      "properties": {
        "hours": {
          "type": "integer",
          "maximum": 168,
          "minimum": 1,
          "description": "How far back to look, in hours (default 48)."
        },
        "ticker": {
          "type": "string",
          "description": "US stock ticker, e.g. \"AAPL\" or \"BRK.B\"."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • trading_halts 0.01 USDC paid never probed

    US stock trading halts right now and earlier today (Nasdaq, NYSE, NYSE American and other US markets), from Nasdaq's halt feed refreshed every minute. For each: symbol, market, the reason in plain English (news pending, volatility pause, additional information requested, regulatory concern...), halt time, and when quoting and trading resume, with a status (halted, resuming_soon, resumed). Filter by one or more tickers, or omit for all.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "symbols": {
          "type": "string",
          "description": "Optional: one or more tickers separated by commas, e.g. \"FFAI, AAPL\". Omit for all current halts."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • find_best_api 0.01 USDC paid never probed

    Describe what you need ("web search", "weather forecast", "verify an email", "pdf to text", "people enrichment") and get the top 1-5 pay-per-call (x402) APIs to use, from an hourly index of Coinbase's x402 marketplace (~38,000 endpoints). Ranked by evidence that other agents keep paying for them: calls per paying wallet over 30 days (so one-off sampling bots count little), how recently each was paid, relevance and price vs. typical. Top candidates are checked live (still asking for payment, at the listed price). Each result: endpoint URL, method, price, network, why it ranks there, and flags (mostly one-time payers, above typical price, not called recently, did not answer). Read-only; never pays.

    mcp-tool

    {
      "type": "object",
      "required": [
        "task"
      ],
      "properties": {
        "task": {
          "type": "string",
          "description": "What you need the API for, in a few words, e.g. \"web search\", \"transcribe audio\", \"company enrichment\"."
        },
        "limit": {
          "type": "integer",
          "maximum": 5,
          "minimum": 1,
          "description": "How many APIs to return (default 3)."
        },
        "check_live": {
          "type": "boolean",
          "description": "Check the top candidates live (default true). False is faster."
        },
        "max_price_usd": {
          "type": "number",
          "description": "Optional price cap per call in USD, e.g. 0.05."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • brainstorm_ideas 0.01 USDC paid never probed

    Brainstorm ideas for a topic, goal, problem or question, each scored 1-10 on three criteria that fit the kind of brainstorm (for business ideas: market size, ease to start, profit potential; for problem solving: impact, feasibility, cost to implement) with an overall score, sorted best first. depth 2 also grows 3 sub-ideas under each of the top 3. Returns a map_url that opens the result as an interactive bubble map on stormap.ai, where a person can keep growing, re-scoring and sharing it. Scores are quick model estimates for sorting, not research.

    mcp-tool

    {
      "type": "object",
      "required": [
        "topic"
      ],
      "properties": {
        "mode": {
          "enum": [
            "general",
            "breakdown",
            "business",
            "content",
            "product",
            "problem",
            "learn",
            "story"
          ],
          "type": "string",
          "description": "Kind of brainstorm; sets the scoring criteria (default general). breakdown splits the topic into exhaustive, non-overlapping parts with no scores."
        },
        "count": {
          "type": "integer",
          "maximum": 5,
          "minimum": 3,
          "description": "Ideas at the top level (default 5)."
        },
        "depth": {
          "type": "integer",
          "maximum": 2,
          "minimum": 1,
          "description": "1 (default) or 2 to also grow sub-ideas under the top 3."
        },
        "steer": {
          "type": "string",
          "description": "Optional constraint, e.g. \"cheap, no hardware\", \"for beginners\"."
        },
        "topic": {
          "type": "string",
          "description": "What to brainstorm, e.g. \"side hustles for engineers\", \"reduce factory scrap rate\", \"YouTube channel about home cooking\"."
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • email_domain_check 0.01 USDC paid never probed

    Is this email address or domain real and legitimate? For lead research, signup / fraud screening, outreach list cleaning and vendor checks. Returns a verdict (looks_legitimate, risky, invalid) with reasons, plus: email syntax, role address (sales@, info@), free provider or disposable/throwaway service, whether the domain accepts mail (MX, null MX), mail provider (Google Workspace, Microsoft 365...), SPF and DMARC policy, whether the website loads, and domain age from RDAP. Does not contact the mail server, so it cannot confirm a specific mailbox exists.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "Email address (e.g. \"[email protected]\") or a bare domain (e.g. \"stripe.com\")."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • read_url 0.01 USDC paid never probed

    Read a web page for an AI: fetch a public page and return its main content as clean, LLM-ready Markdown (navigation, footers, scripts and cookie banners removed) plus metadata: title, description, author, published/modified dates, canonical URL, language and word count. Reads server-rendered HTML (no JavaScript execution) and respects robots.txt.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public page URL, e.g. \"https://example.com/blog/post\"."
        },
        "max_chars": {
          "type": "integer",
          "default": 20000,
          "maximum": 100000,
          "minimum": 500,
          "description": "Maximum Markdown length to return."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • generate_ai_robots_txt reads open 42d ago

    Generate robots.txt rules for AI crawlers from a policy: "open" (allow all), "balanced" (allow search and user-triggered fetchers, block bulk training crawlers) or "block" (block all). Optional per-bot overrides, allowed/blocked paths, sitemap and crawl delay. No network access.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "policy": {
          "enum": [
            "open",
            "balanced",
            "block"
          ],
          "type": "string",
          "default": "balanced"
        },
        "site_url": {
          "type": "string"
        },
        "overrides": {
          "type": "object",
          "description": "e.g. {\"GPTBot\":\"allow\",\"CCBot\":\"block\"}",
          "additionalProperties": {
            "enum": [
              "allow",
              "block"
            ],
            "type": "string"
          }
        },
        "allow_paths": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "crawl_delay": {
          "type": "integer",
          "maximum": 60,
          "minimum": 1
        },
        "sitemap_url": {
          "type": "string"
        },
        "disallow_paths": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
  • search_guides reads unknown 45d ago

    Search Stormap's practical guides on building with AI agents (OpenClaw, Hermes, Claude, coding agents, browser automation, RAG, MCP, AI news). Returns titles, URLs, Markdown URLs and short descriptions.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "What to look for, e.g. \"install hermes desktop\" or \"stop coding agents overwriting files\"."
        },
        "category": {
          "type": "string",
          "description": "Optional category filter, e.g. \"OpenClaw Tutorials\", \"AI News\", \"AI Tools\", \"Automation\"."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • get_guide reads unknown 42d ago

    Return one Stormap guide as clean Markdown with front matter (title, URL, dates, tags). Accepts a slug ("how-to-install-hermes-desktop") or a stormap.ai post URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Guide slug or full https://stormap.ai/post/... URL."
        },
        "max_chars": {
          "type": "integer",
          "default": 60000,
          "maximum": 200000,
          "minimum": 1000
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • ai_visibility_score reads 0.01 USDC unknown 42d ago

    AI search / GEO / AEO audit: score how well AI assistants (ChatGPT, Claude, Perplexity, Gemini) can find, read and cite a public web page: 0-100 score, letter grade, pass/fail checks (AI answer-bot access in robots.txt, server-rendered content, title/meta, JSON-LD, canonical, llms.txt, sitemap) and a prioritized fix list. Blocking bulk training crawlers is treated as a policy choice and does not lower the score.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public page URL or domain, e.g. \"example.com\" or \"https://example.com/pricing\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • check_ai_crawler_access reads unknown 43d ago

    Check whether AI crawlers (GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, Claude-User, PerplexityBot, Google-Extended, CCBot) may access a public URL according to its robots.txt, and score the page's machine readability (status, title, meta description, canonical, JSON-LD, server-rendered text). Returns a 0-100 score and a list of findings.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Public page URL or domain, e.g. \"https://example.com/pricing\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • generate_llms_txt reads unknown 43d ago

    Generate an llms.txt file (llmstxt.org format) for a public website. Uses the site name, summary and pages you pass; anything missing is filled from the homepage and sitemap.xml. Returns the file text plus notes on how to improve it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "site_url"
      ],
      "properties": {
        "pages": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 100,
          "description": "Optional list of the most important page URLs. If omitted, sitemap.xml is used."
        },
        "summary": {
          "type": "string",
          "description": "One paragraph: what the site is, who it is for, what is most useful."
        },
        "site_url": {
          "type": "string",
          "description": "Site root, e.g. \"https://example.com\"."
        },
        "max_pages": {
          "type": "integer",
          "default": 25,
          "maximum": 60,
          "minimum": 5
        },
        "site_name": {
          "type": "string"
        }
      },
      "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.

  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 21a1c344440bb4b1.

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