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

webacy-risk-score

https://api.webacy.com

Registry code: 6cb50bbbc596ed1e

api record

Webacy blockchain risk-analysis tools. Several tools take a token address, so pick by asset type:

- Stablecoins, RWAs, or pegged tokens (e.g. USDC, USDT, PYUSD, DAI, USDe, tokenized treasuries/money-market funds like BUIDL, or commodity tokens like PAXG): use get_rwa_token_risk for depeg / peg-stability analysis. Browse them with list_rwa_tokens.

endpoint
https://api.webacy.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 webacy-risk-score live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is webacy-risk-score free to use?
Yes — the hub reached it with no key and no payment.
What tools does webacy-risk-score have?
7 tools: list_rwa_tokens, get_address_risk, get_token_risk, get_vault_risk, get_rwa_token_risk, get_holder_analysis, list_vaults.
Is webacy-risk-score 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
325ms

last good check

priced tools
0

of 7 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 7 tools
7 never probed 0 of 7 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.

  • list_rwa_tokens unknown 1h ago

    List RWA and pegged tokens (stablecoins) with depeg risk data. Use `segment` to ask for one category only: "stablecoin" (fiat-pegged) or "rwa" (tokenized treasuries / funds / commodities); `peg_type` narrows by peg mechanism (direct, collateralized, algorithmic, derivative-hedged, yield-bearing) — e.g. segment=stablecoin + peg_type=collateralized = crypto-backed stablecoins. Every item carries its computed `segment` plus the RFC-027 dimensions it is derived from (`asset_class` = fiat / fixed-income / commodity, `is_rwa`, `subclass`), plus `peg_behavior` (fiat-stable, nav-stable, floats-with-underlying, unpegged, stable-unspecified) and `mechanics` (structural traits such as custodial-issuer, wrapper, bridged); do not pass a dimension value to `segment`. Returns paginated items with ecosystem aggregates (tier counts, denomination breakdown). Each item also carries the Webacy A+→F v3 composite letter grade / rating (`grade`), the same grade shown on dd.xyz, or null when the token is not in the graded dataset. The response also carries a top-level `grades_available` boolean — false when the grading pipeline was unavailable for the request (grades are null for that reason, not because the tokens are ungraded) — and a top-level `schema_version` string identifying the graded response shape.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "q": {
      "type": "string",
      "description": "Search by symbol, name, or address"
    },
    "page": {
      "type": "number",
      "description": "Page number (1-indexed, default 1)"
    },
    "sort": {
      "type": "string",
      "description": "Sort field: score, symbol, chain, tier, abs_dev_clean, market_cap_usd, volume_24h_usd, ts"
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Filter by token labels: standard, yield, rwa, gold, bridged, vault"
    },
    "tier": {
      "type": "string",
      "description": "Risk tier: critical, warning, watch, ok, premium"
    },
    "chain": {
      "type": "string",
      "description": "Blockchain network"
    },
    "order": {
      "type": "string",
      "description": "Sort order: asc, desc"
    },
    "segment": {
      "type": "string",
      "description": "Segment: stablecoin, rwa (stablecoin = fiat-pegged; rwa = tokenized treasuries/funds/commodities). A derived category, NOT the RFC-027 `asset_class` dimension each returned item carries — an item's `asset_class` reads fiat / fixed-income / commodity and is not valid here."
    },
    "min_mcap": {
      "type": "number",
      "minimum": 0,
      "description": "Minimum market cap in USD"
    },
    "peg_type": {
      "type": "string",
      "description": "Peg mechanism: direct, collateralized, algorithmic, derivative-hedged, yield-bearing"
    },
    "liquidity": {
      "type": "string",
      "description": "Liquidity tier: high, medium, low, very_low"
    },
    "max_score": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Maximum risk score (0-100)"
    },
    "min_score": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Minimum risk score (0-100)"
    },
    "page_size": {
      "type": "number",
      "description": "Items per page (max 100, default 20)"
    },
    "denomination": {
      "type": "string",
      "description": "Filter by denomination code (e.g., USD, EUR, XAU)"
    }
  },
  "additionalProperties": false
}
    arguments 75 lines
  • get_address_risk unknown never probed

    Analyze the risk profile of a blockchain address (wallet or contract). Returns risk score, risk factors, and detailed security analysis. If the address is a stablecoin, RWA, or other pegged token (e.g. USDC, USDT, PYUSD, DAI), prefer get_rwa_token_risk, which adds depeg / peg-stability analysis.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address",
    "chain"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "description": "Blockchain network: eth, sol, arb, pol, opt, base, bsc, ton, sui, stellar, btc, sei, robinhood, hedera, tron"
    },
    "address": {
      "type": "string",
      "description": "The blockchain address to analyze"
    },
    "modules": {
      "type": "array",
      "items": {
        "enum": [
          "governance_analysis",
          "token_security",
          "contract_analysis",
          "source_code_analysis",
          "market_data",
          "holder_analysis",
          "liquidity_analysis",
          "fraud_detection",
          "sanctions_compliance",
          "mixer_detection",
          "address_behavior",
          "transaction_analysis",
          "reputation_analysis",
          "solana_specific",
          "evm_specific",
          "ton_specific",
          "sui_specific",
          "basic_info",
          "security_essentials",
          "fund_flow_screening",
          "developer_migration",
          "vault_analysis",
          "depeg_analysis"
        ],
        "type": "string"
      },
      "description": "Specific risk analysis modules to run (e.g. token_security, market_data, holder_analysis)"
    },
    "show_low_risk": {
      "type": "boolean",
      "description": "Include low-risk factors in the response"
    },
    "detailed_response": {
      "type": "boolean",
      "description": "Include detailed risk factor breakdowns"
    }
  },
  "additionalProperties": false
}
    arguments 59 lines
  • get_token_risk unknown never probed

    Analyze the risk profile of a general token contract. Returns token security flags, market data, and economic risk indicators. For stablecoins, RWAs, or other pegged tokens (e.g. USDC, USDT, PYUSD, DAI), prefer get_rwa_token_risk, which adds depeg / peg-stability analysis.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address",
    "chain"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "description": "Blockchain network: eth, sol, arb, pol, opt, base, bsc, ton, sui, stellar, btc, sei, robinhood, hedera, tron"
    },
    "address": {
      "type": "string",
      "description": "The token contract address to analyze"
    },
    "modules": {
      "type": "array",
      "items": {
        "enum": [
          "governance_analysis",
          "token_security",
          "contract_analysis",
          "source_code_analysis",
          "market_data",
          "holder_analysis",
          "liquidity_analysis",
          "fraud_detection",
          "sanctions_compliance",
          "mixer_detection",
          "address_behavior",
          "transaction_analysis",
          "reputation_analysis",
          "solana_specific",
          "evm_specific",
          "ton_specific",
          "sui_specific",
          "basic_info",
          "security_essentials",
          "fund_flow_screening",
          "developer_migration",
          "vault_analysis",
          "depeg_analysis"
        ],
        "type": "string"
      },
      "description": "Specific risk analysis modules to run (e.g. token_security, market_data)"
    },
    "metrics_date": {
      "type": "string",
      "pattern": "^\\d{2}-\\d{2}-\\d{4}$",
      "description": "Date for historical metrics in DD-MM-YYYY format (CoinGecko format)"
    }
  },
  "additionalProperties": false
}
    arguments 56 lines
  • get_vault_risk unknown never probed

    Get detailed risk analysis for an ERC-4626 vault. Returns risk score, risk tier, risk decomposition across 7 categories (structure, governance, liquidity, code quality, asset, performance, protocol), looping data, Morpho markets, and Webacy findings. Also returns the Webacy A+→F letter grade / rating (`grade`), when available.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address",
    "chain"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "description": "Blockchain network: eth, arb, base, opt, pol, bsc, avax, gnosis, sol, stellar"
    },
    "address": {
      "type": "string",
      "description": "The vault contract address (e.g., 0x1234...)"
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • get_rwa_token_risk unknown never probed

    Depeg / peg-stability risk analysis for a stablecoin, RWA, or pegged token — e.g. USDC, USDT, PYUSD, DAI, USDe, tokenized treasuries or money-market funds (BUIDL), or commodity tokens (PAXG). PREFER THIS over get_token_risk whenever the asset is a stablecoin, RWA, or otherwise pegged. Returns risk score, depeg snapshot, score decomposition, depeg history, and risk tier. Also returns the Webacy A+→F v3 composite letter grade / rating (`grade`), the same grade shown on dd.xyz, when the token is in the graded dataset.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "description": "Blockchain network (required if address exists on multiple chains)"
    },
    "hours": {
      "type": "number",
      "description": "Hours of depeg history to return (default 24, max 168)"
    },
    "address": {
      "type": "string",
      "description": "The token contract address"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • get_holder_analysis unknown 1h ago

    Analyze the holder distribution and concentration of a token. Returns top holders, holder counts, and distribution metrics.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "address"
  ],
  "properties": {
    "chain": {
      "type": "string",
      "default": "sol",
      "description": "Blockchain network: sol, eth, bsc, pol, arb, opt, robinhood, sei, base, stellar, sui, hedera, tron"
    },
    "address": {
      "type": "string",
      "description": "The token contract address to analyze"
    },
    "refresh_cache": {
      "type": "boolean",
      "description": "Force refresh cached holder data"
    },
    "disable_refetch": {
      "type": "boolean",
      "description": "Skip re-fetching data and use existing data only"
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • list_vaults unknown 1h ago

    List ERC-4626 vaults with risk scores, filtering, and sorting. Returns paginated vault items with ecosystem aggregates (tier counts, TVL, highest risk, largest TVL). Each item also carries the Webacy A+→F v3 composite letter grade / rating (`grade`), the same grade shown on dd.xyz, or null when the vault could not be graded. For "safest" queries use sort="safest" (only DD safe_to_list vaults, lowest risk first); for "highest yield" / "best APY" use sort="highest_yield" (highest APY first, unknown-APY excluded). Both aliases report eligible-only counts in `pagination.total` / `eligible_count` / `eligible_tvl_usd` (NOT in `aggregates.*`, which stays ecosystem-wide) and add a `note` — never call a caution/review_required/do_not_list vault "safe".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "q": {
      "type": "string",
      "description": "Search by symbol, name, or address"
    },
    "page": {
      "type": "number",
      "description": "Page number (1-indexed, default 1)"
    },
    "sort": {
      "type": "string",
      "description": "Sort. Ranking aliases: safest (only DD safe_to_list vaults, lowest risk first), highest_yield (highest APY first, unknown-APY excluded). Raw sorts: score_desc, score_asc, tvl_desc, tvl_asc, apy_desc, looping_desc, utilization_desc, utilization_asc, name_asc, lockup_asc, protocol_asc, incentive_apr_desc, durability_desc"
    },
    "tier": {
      "type": "string",
      "description": "Filter by risk tier: low, medium, high, critical, unknown"
    },
    "chain": {
      "type": "string",
      "description": "Filter by chain: eth, arb, base, opt, pol, bsc, avax, gnosis, sol, stellar"
    },
    "min_tvl": {
      "type": "number",
      "description": "Minimum TVL in USD"
    },
    "protocol": {
      "type": "string",
      "description": "Filter by protocol: morpho, aave, compound, euler, spark, fluid, beefy, yearn, lagoon, centrifuge, gauntlet, kamino"
    },
    "max_score": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Maximum risk score (0-100)"
    },
    "min_score": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Minimum risk score (0-100)"
    },
    "page_size": {
      "type": "number",
      "description": "Items per page (max 50, default 20)"
    },
    "underlying": {
      "type": "string",
      "description": "Filter by underlying asset symbol (e.g., USDC)"
    }
  },
  "additionalProperties": false
}
    arguments 55 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 6cb50bbbc596ed1e.

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