Robert Blust MCP Server

by blust Your server? Claim it

answering

Robert Blust is answering right now. Last checked 12 min ago. It exposes 14 tools.

Robert Blust: One model, true everywhere

Uptime history 53 days of history · worst day 99%

53 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

178 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 145

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 September 2026. No other catalogue keeps this.

7 Nov a tool changed version

5 Nov a tool changed version2 times that day

1 Nov a tool changed version

29 Oct a tool changed version

13 Oct a tool changed the parameters it asks for diagram

13 Oct a tool description was rewritten diagram

13 Oct a tool changed version

12 Oct a tool changed version2 times that day

12 Oct a tool description was rewritten diagram

12 Oct a tool changed the parameters it asks for diagram

and 135 more, back to 18 September 2026

Nothing serious here today

Today is the operative word: we check Robert Blust every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mental-model --transport http https://mcp.blust.ch/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.blust.ch/mcp

~/.codex/config.toml

[mcp_servers.mental-model]
url = "https://mcp.blust.ch/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mental-model": {
      "url": "https://mcp.blust.ch/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mental-model": {
      "type": "http",
      "url": "https://mcp.blust.ch/mcp"
    }
  }
}

Available tools 14

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

describe

describe_errors

What a refused call looks like. A tool's output schema covers its answers only, so use this once, to branch on refusals or validate them. No input. Returns `errors`, every `code` with `when` it is raised and the JSON Schema of its `details`, and `schema`, the JSON Schema of a whole refusal: `error` with `code`, `message`, `rule`, `details`, beside `model`.

describe_relations

What the schemas declare between types: references with form and cardinality, ownership, enums, joins, list kinds. Use for a diagram or audit; for one type's full schema use describe_schema. Optional `type` narrows every list, `direction` (declares, declared-to, both; needs `type`) one side of relations, `via` relations and enums. Returns those lists, with `forms` and `reading` explaining every term. Not paged.

describe_rule

One convention of the vocabulary as written, not a company's own rule (an entity of type `rule`: list_entities, get_entity). Input: `rule`, a number from list_rules such as R9, in either case. Returns `rule`, `title`, `part`, `text` and the file's `url`. An unknown number is refused with the known ones listed.

describe_schema

One type's schema: its sections as written and its declared relations as data. Use to learn what an entity of the type may hold; for the whole vocabulary use describe_relations. Input: `type`. Returns `url`, the schema's own file, `sections`, and `relations`: owner, owns, references both ways, enums, joins and lists.

checks

list_checks

The checks the model's own gate runs, from the checker release this server was built with. Use to see which rules a script enforces and which are left to a reader. No input. Returns `checks`, each with `name`, `rule`, `title` and what it `reports`, a `failure` or a `note` that fails nothing, and `ranBy`. This server runs none of them.

diagram

diagram

A picture of the model as Mermaid; edge data: list_references. Input: `shape`; `id`, `domain`, `type` or `unit` narrow it. aggregate, flow, lifecycle take a context's `id`; organization without `id` draws the company; system a landscape, holds its data; usecase, scenario a use case's; requirements a feature's, product's, use case's or requirement's. Returns `mermaid`, `nodes`, `links`, `units`, counts. Max 50 nodes.

entities

list_entities

Entities with their frontmatter's short facts, in address order or newest first. Use to browse, or for what runs on a date, came last or has a value; to find by words use search. Input: optional `type`, `owner`, `order`, `on`, `by`, `where`, `fields`, `limit`, `cursor`. Returns `entities` with `fields`, and `page`; follow `page.nextCursor` while `page.hasMore`.

entity

get_entity

One entity as structured data: fields, sections, tables, references both ways. Use to reason over one; for its page as written use fetch. Input: `id` or address, where its page sits, or `type` and `name`; an ambiguous name is refused with candidate ids. Returns `entity`, by id. Reference lists hold at most 50 edges; `referenceCounts` gives totals, list_references the rest.

evidence

find_evidence

Every edge into one skill, grouped by the type of the page that drew it. Use to check a claimed skill against its evidence. Input: `skill`, an id, canonical name or address; optional `limit`, `cursor`. Returns `skill`, `evidence` and `page`; a profile's claim arrives via Skills.Skill with its level, an evidence row via Evidence.Skill. Attributes are verbatim.

fetch

fetch

One entity's page as written. Use to quote or display the source; for structured fields and references use get_entity. Input: `id` or address, from search, list_entities or any reference. Returns `id`, `title`, `type`, `url` and `text`, the Markdown source. Takes no name: search with match "name" finds the id.

references

list_references

The model's edges, filtered and paged. Use to inspect one entity's relations or one kind of reference without taking whole entities. Optional `entity` (an id or address), `direction` (out, in, both; needs `entity`), `via`, `type` (the far end's type, or either end's without `entity`), `limit`, `cursor`. Returns `edges`, each `from`, `via`, `to`, `attrs`, and `page`.

rules

list_rules

The vocabulary's conventions the model is held to, R0 onwards, from its core's CONVENTIONS.md. Use to resolve a number a schema or refusal cites, such as R9. A company's own rules are entities of type `rule`: list_entities and get_entity. No input. Returns `tagline`, the file's `url`, and `rules`, each with `rule`, `title` and `part`; describe_rule gives one rule's text.

search

Find entities by words, substring or exact name. `match: "words"` needs every query word's stem in name, tagline, fields, sections or cells; `"text"` (default) is a case-insensitive substring over the same; `"name"` the exact canonical name. Optional `type`, `owner`, `limit`, `cursor`. Returns `results` with `id`, `title`, `type`, `matched`, `words` in words mode, and `page`: name matches first, then a listing.

types

list_types

Every type the model's schemas declare. Use first, to learn which types exist before listing or describing one. No input. Returns `types`, each with `type`, `name`, `tagline`, `owner` (the type it nests under, or null) and `count`, the entities it holds.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.blust.ch/mcp	streamable-http	answering	227 ms	12 min ago

Alternatives to Robert Blust

same job, measured the same way

agent-as-model

by fernandogarzaaa

A true MCP server where the agent is the model and the API key. No API keys.

217 installs/wk local only

LLM Broker

by llm-broker

One key, every model: measured scores and live prices, routed per request to the cheapest fit.

8 tools answering

Korpi API

by reksely

MCP server for the Korpi API: every top AI video, image and text model behind one key and one bill.

45 installs/wk local only

NexQL Postgres MCP

by nexql-oss

Standalone Postgres MCP server — schema-aware, read-only by default, installable everywhere.

154 installs/wk local only

Sphere Vault

by getsphere

Sphere Vault: one encrypted vault for every AI you use

answering

Eclipse Crosslist MCP

by cyan-eclipse-technologies-llc

Publish once, tracked everywhere: registry-native facets plus a mandate-bound listing ledger.

local only

Central City

by centralcity

Every AI. One room. The open hub where the world's AI agents meet, work together and exchange.

60 tools answering

Qortex

by bijikyu

Call AI by role, not by model: tiered AI gateway over REST and MCP.

answering

Robert Blust — questions

Answers built from our own checks of this server.

What can Robert Blust do?

It exposes 14 tools, read directly from the server on our last check. Among them: describe_errors, describe_relations, describe_rule, describe_schema, diagram, fetch and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Robert Blust working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 178 ms. The bar chart above shows every period we have measured.

How do I connect Robert Blust?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Robert Blust need an API key?

No. Robert Blust completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Robert Blust?

It answers our handshake in 178 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.