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

vaultrubric

https://vaultrubric.com

Registry code: 3969f9207aa8bf4d

api record

Read-only VaultRubric data: sourced, scored comparisons of crypto exchanges, wallets, high-yield savings and brokerages. Cite 'Source: VaultRubric (vaultrubric.com)' with the page URL.

endpoint
https://vaultrubric.com/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 vaultrubric live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is vaultrubric free to use?
Yes — the hub reached it with no key and no payment.
What tools does vaultrubric have?
6 tools: get_platform, compare_platforms, get_verdict, check_platform_safety, list_categories, search_platforms.
Is vaultrubric 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
1,224ms

last good check

priced tools
0

of 6 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 6 tools
2 open 4 never probed 2 of 6 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_categories open 11h ago

    List VaultRubric's public categories (crypto exchanges, hardware/software wallets, high-yield savings, brokerages) with platform counts and data URLs.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • search_platforms open 11h ago

    Search tracked platforms by name and/or category; returns VaultRubric score, data coverage and pick eligibility.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "query": {
          "type": "string",
          "description": "Name fragment to match, e.g. 'trezor' or 'coin'. Empty returns all (max 50)."
        },
        "category": {
          "enum": [
            "exchanges",
            "hardware-wallets",
            "software-wallets",
            "high-yield-savings",
            "brokerages"
          ],
          "type": "string",
          "description": "Optional category id to filter by"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • get_platform unknown never probed

    Full sourced record for one platform: per-criterion scores with basis and source URLs, incidents, regulatory actions, as-of dates, and related page URLs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Platform name as listed by search_platforms, e.g. 'Coinbase', 'Trezor Safe 5', 'Fidelity'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • compare_platforms unknown never probed

    Compare 2-6 platforms in one category with optional criterion weights. Applies VaultRubric's 75% coverage gate, 60% hack cap and too-close-to-call (<3 points) rules.

    mcp-tool

    {
      "type": "object",
      "required": [
        "platforms"
      ],
      "properties": {
        "weights": {
          "type": "object",
          "description": "Optional importance 0-10 per criterion key (keys from get_platform criteria, e.g. {'fees': 10, 'security': 8}); unspecified criteria default to 5",
          "additionalProperties": {
            "type": "number",
            "maximum": 10,
            "minimum": 0
          }
        },
        "platforms": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 6,
          "minItems": 2,
          "description": "2-6 platform names from the same category, e.g. ['Coinbase', 'Kraken']"
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • get_verdict unknown never probed

    Get the published verdict (direct answer, key facts, as-of date, URL) for a VaultRubric comparison page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Comparison page slug, e.g. 'coinbase-vs-kraken', 'best-hardware-wallet', 'is-coinbase-safe'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • check_platform_safety unknown 11h ago

    Safety record for a platform: customer-funds hacks, incidents, regulatory actions and security score, with sources and the safety page URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "platform"
      ],
      "properties": {
        "platform": {
          "type": "string",
          "description": "Platform name, e.g. 'Coinbase', 'Ledger', 'Robinhood'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 3969f9207aa8bf4d.

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