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

modelread

https://modelread.vercel.app

Registry code: bf0a85f72cc923d6

api record

Use modelread whenever the user asks whether a Hugging Face / open-weights model will run on a GPU, Mac, phone, multi-GPU node or cloud instance; how many tokens/sec to expect; which GGUF/MLX/AWQ/FP8 quant fits in VRAM; how much context fits; what to run on a given machine; or needs a llama.cpp / vLLM / MLX / Ollama launch command (also before downloading, quantizing or serving a model).

modelread: will a Hugging Face model run on given hardware, how fast, which quant, with what command. Numbers come from real repo file sizes, GGUF/safetensors tensor headers and configs (nothing is…

endpoint
https://modelread.vercel.app/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 modelread live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is modelread free to use?
Yes — the hub reached it with no key and no payment.
What tools does modelread have?
6 tools: compare_hardware, ask, find_models, estimate_fit, search_models, list_hardware.
Is modelread 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
773ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 3 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.

  • search_models open 4h ago

    Search the model index without estimating (fast): ids, task, library, params, downloads, likes, license, created date. task: chat|coding|vision|embedding|... ; query: substring of the repo id (e.g. 'qwen3', 'gemma-4'); max_params_billion filters by size.

    mcp-tool

    {
      "type": "object",
      "title": "search_modelsArguments",
      "properties": {
        "task": {
          "type": "string",
          "title": "Task",
          "default": "chat"
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 20
        },
        "query": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Query",
          "default": null
        },
        "max_params_billion": {
          "anyOf": [
            {
              "type": "number"
            },
            {
              "type": "null"
            }
          ],
          "title": "Max Params Billion",
          "default": null
        }
      }
    }
    arguments 40 lines
  • list_hardware open 4h ago

    List hardware presets (330+: GPUs of every vendor and segment, multi-GPU nodes, Apple, Jetson/APUs, phones, tablets, SBCs, VPS tiers). filter: words matched against id/name/vendor/segment, e.g. 'h100', 'amd datacenter', 'phone samsung', 'vps'. Returns id, name, kind, memory, bandwidth, backend.

    mcp-tool

    {
      "type": "object",
      "title": "list_hardwareArguments",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 40
        },
        "filter": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Filter",
          "default": null
        }
      }
    }
    arguments 23 lines
  • compare_hardware unknown 31h ago

    Run one repo against several devices and return the best candidate per device (verdict, quant, decode band, max context, launch command), sorted best first. Use for 'which of my machines should run X' or 'is a 4090 or an M4 Max better for X'. hardware: comma-separated list of presets / free text (max 8).

    mcp-tool

    {
      "type": "object",
      "title": "compare_hardwareArguments",
      "required": [
        "repo",
        "hardware"
      ],
      "properties": {
        "ctx": {
          "type": "integer",
          "title": "Ctx",
          "default": 8192
        },
        "repo": {
          "type": "string",
          "title": "Repo"
        },
        "hardware": {
          "type": "string",
          "title": "Hardware"
        }
      }
    }
    arguments 23 lines
  • ask unknown 2d ago

    Free-form question about running Hugging Face models locally or self-hosted (runtimes, quant choice, KV cache, why something OOMs, MoE offload); returns markdown plus the parsed query and notes.

    mcp-tool

    {
      "type": "object",
      "title": "askArguments",
      "required": [
        "question"
      ],
      "properties": {
        "question": {
          "type": "string",
          "title": "Question"
        }
      }
    }
    arguments 13 lines
  • find_models unknown never probed

    Recommend models for a task on given hardware, written as a natural question, e.g. 'best coding model for an RTX 4090 + 64GB RAM at 32k context', 'Japanese chat on a Galaxy S25 Ultra', 'serve 8 users on 2x RTX 3090'. Ranks indexed Hub models (~20k, refreshed nightly) by fit, task benchmark percentile (provenance-tagged, vendor vs independent), speed and adoption; each result carries a full fit estimate. Tasks understood: chat, coding, agentic, vision, ocr, math, reasoning, multilingual, function-calling, embedding, reranking, speech-to-text, tts, image-generation, video-generation.

    mcp-tool

    {
      "type": "object",
      "title": "find_modelsArguments",
      "required": [
        "question"
      ],
      "properties": {
        "question": {
          "type": "string",
          "title": "Question"
        }
      }
    }
    arguments 13 lines
  • estimate_fit unknown 4h ago

    Will this Hugging Face repo run on this hardware? Checks the repo and its quantized derivatives (GGUF/MLX/AWQ...) and returns, per candidate: verdict (fits | fits-tight | offload | no | unknown), memory placement (VRAM / RAM / SSD), longest context that fits, decode and prefill tok/s bands with basis, concurrent-serving aggregate, runtime support (llama.cpp / vLLM / MLX registries) and an exact launch command. repo: 'org/name' (base model or a GGUF repo). hardware: preset id, '<N>x-<id>', free text, or 'gpu=..,ram=..,bw=..'. ctx in tokens.

    mcp-tool

    {
      "type": "object",
      "title": "estimate_fitArguments",
      "required": [
        "repo",
        "hardware"
      ],
      "properties": {
        "ctx": {
          "type": "integer",
          "title": "Ctx",
          "default": 8192
        },
        "repo": {
          "type": "string",
          "title": "Repo"
        },
        "ram_gb": {
          "anyOf": [
            {
              "type": "number"
            },
            {
              "type": "null"
            }
          ],
          "title": "Ram Gb",
          "default": null
        },
        "hardware": {
          "type": "string",
          "title": "Hardware"
        },
        "include_vision": {
          "type": "boolean",
          "title": "Include Vision",
          "default": false
        },
        "kv_cache_dtype": {
          "type": "string",
          "title": "Kv Cache Dtype",
          "default": "f16"
        },
        "check_quantized_derivatives": {
          "type": "boolean",
          "title": "Check Quantized Derivatives",
          "default": true
        }
      }
    }
    arguments 50 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 bf0a85f72cc923d6.

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