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

strictscore

https://strictscore.com

Registry code: 73c9cd6337ec8f41

api record

StrictScore rates 700+ crypto assets with a STRICT score from 0 to 100: the sector-weighted mean of six fundamentals pillars (Sustainability, Transparency, Revenue, Innovation, Community, Tokenomics). Call search_coins first to turn a name or ticker into a slug; get_coin_analysis and compare_coins take slugs, get_rankings filters by sector (see list_sectors) and score. Scores come from dated analyses: lastAnalyzed is the analysis date, as_of the day the result was served. A null score means no analysis, or a score the key plan hides. Limits: read-only; 30 requests a minute per IP, and 120 a…

endpoint
https://strictscore.com/api/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 strictscore live?
Yes — it answered the hub's last check (checked 20h ago). It answered 100% of checks over the last 30 days.
Is strictscore free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does strictscore have?
8 tools: get_coin_analysis, compare_coins, list_sectors, get_market_movers, get_market_health, get_daily_pick, get_rankings, search_coins.
Is strictscore 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
166ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 2 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 8 tools
8 auth-required 8 of 8 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.

  • get_coin_analysis auth-required never probed

    Returns the full StrictScore analysis of one asset: STRICT score and six pillar ratings, risk score and factors, upside and probability, hype narratives, overview, thesis, strengths, risks, catalysts, price scenarios, last analyzed date and the page URL. Use it after search_coins when the user wants depth on one asset. Not for several assets side by side (use compare_coins) or a quick lookup (search_coins is lighter). Example arguments: {"slug": "ethereum", "locale": "en"}.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "minLength": 1,
          "description": "StrictScore slug as returned by search_coins, for example \"bitcoin\" or \"ethereum\"."
        },
        "locale": {
          "enum": [
            "en",
            "fr",
            "de",
            "es",
            "pt",
            "ko",
            "ja",
            "id",
            "tr",
            "vi"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the written analysis (overview, thesis, risks). Scores and numbers do not change."
        }
      }
    }
    arguments 31 lines
  • compare_coins auth-required never probed

    Returns the full StrictScore analyses of up to 5 assets in one call, in request order, with null for a slug that has no analysis (if none of the slugs has one, an error naming them). Use it to compare assets side by side. Not for a single asset (use get_coin_analysis) or for finding slugs (use search_coins). Example arguments: {"slugs": ["bitcoin", "ethereum", "solana"]}.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slugs"
      ],
      "properties": {
        "slugs": {
          "type": "array",
          "items": {
            "type": "string",
            "minLength": 1
          },
          "maxItems": 5,
          "minItems": 1,
          "description": "1 to 5 slugs. StrictScore slug as returned by search_coins, for example \"bitcoin\" or \"ethereum\"."
        },
        "locale": {
          "enum": [
            "en",
            "fr",
            "de",
            "es",
            "pt",
            "ko",
            "ja",
            "id",
            "tr",
            "vi"
          ],
          "type": "string",
          "default": "en",
          "description": "Language of the written analysis (overview, thesis, risks). Scores and numbers do not change."
        }
      }
    }
    arguments 36 lines
  • list_sectors auth-required 20h ago

    Returns the sector names StrictScore uses. Call it before get_rankings when the user names a sector, and pass the value unchanged. Takes no arguments: {}.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_market_movers auth-required never probed

    Returns the 10 biggest 24h gainers and 10 biggest 24h losers among StrictScore-covered assets, with scores and page URLs. Use it for "what moved today". Not for score-based screening (use get_rankings) or overall market conditions (use get_market_health). Takes no arguments: {}.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_market_health auth-required 20h ago

    Returns the StrictScore Market Health Score (0-100), danger index, regime label (capitulation, risk_off, neutral, risk_on, froth), the five component scores, a one-line verdict, the snapshot time and degraded-data flags. Use it for market-wide conditions. Not for a single asset (use get_coin_analysis). Check degraded.any before relying on the score. Takes no arguments: {}.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_daily_pick auth-required 20h ago

    Returns the StrictScore daily pick (the asset selected for a date among those at or above the STRICT floor of 60) with its selection reasons, price at selection, latest price and performance since the pick. Use it when asked for the daily pick. Without a date it returns the latest pick, only if published within 36 hours. It is a research selection, not advice. Example arguments: {"date": "2026-11-05"}.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Pick date as YYYY-MM-DD. Omit for the latest pick."
        }
      }
    }
    arguments 11 lines
  • get_rankings auth-required 47h ago

    Lists assets ranked by STRICT score (default), market cap, price, 24h change, volume, upside or name, optionally filtered by sector and score range, one page at a time. Use it to find the strongest or weakest assets in a sector. Not for looking up one named coin (use search_coins) or for a full analysis (use get_coin_analysis). Example arguments: {"sector": "Layer 2", "minScore": 60, "sortBy": "strictScore", "limit": 10}.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "page": {
          "type": "integer",
          "default": 1,
          "maximum": 9007199254740991,
          "minimum": 1,
          "description": "Page number, starting at 1."
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1,
          "description": "Rows per page (1-50)."
        },
        "sector": {
          "type": "string",
          "description": "Sector name exactly as returned by list_sectors. Omit for all sectors."
        },
        "sortBy": {
          "enum": [
            "rank",
            "marketCap",
            "strictScore",
            "price",
            "priceChange24h",
            "volume24h",
            "name",
            "maxUpside"
          ],
          "type": "string",
          "default": "strictScore",
          "description": "Field to sort by."
        },
        "maxScore": {
          "type": "number",
          "maximum": 100,
          "minimum": 0,
          "description": "Only assets with a STRICT score of at most this value (0-100)."
        },
        "minScore": {
          "type": "number",
          "maximum": 100,
          "minimum": 0,
          "description": "Only assets with a STRICT score of at least this value (0-100)."
        },
        "sortOrder": {
          "enum": [
            "asc",
            "desc"
          ],
          "type": "string",
          "default": "desc",
          "description": "Sort direction."
        }
      }
    }
    arguments 60 lines
  • search_coins auth-required never probed

    Finds StrictScore-covered crypto assets by name or ticker and returns each match with its slug, STRICT score, market data and page URL, largest market cap first. Call this first to get the slug the other tools need. Not for browsing by score or sector (use get_rankings). Example arguments: {"query": "eth", "limit": 5}.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum matches to return (1-20)."
        },
        "query": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Coin name or ticker, for example \"bitcoin\" or \"SOL\". Partial names work."
        }
      }
    }
    arguments 22 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 73c9cd6337ec8f41.

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