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

steiner-hat-gesagt

https://steinerhatgesagt.org

Registry code: 57dd56ee69374c4f

api record

Full-text database of Rudolf Steiner's collected works (Gesamtausgabe, GA), in the original German.

Use search to find what Steiner said or wrote about a topic and read to see the context around a hit.

endpoint
https://steinerhatgesagt.org/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 steiner-hat-gesagt live?
Yes — it answered the hub's last check (checked 7h ago). It answered 100% of checks over the last 30 days.
Is steiner-hat-gesagt free to use?
Yes — the hub reached it with no key and no payment.
What tools does steiner-hat-gesagt have?
5 tools: count_matches, search, read, get_work, list_works.
Is steiner-hat-gesagt 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
140ms

last good check

priced tools
0

of 5 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 5 tools
1 open 4 never probed 1 of 5 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_works open 7h ago

    Catalogue of all volumes in the Gesamtausgabe with title, section and whether the full text is available. Filter by title words, section and the year lectures were held. The reply text begins with the fixed phrase "Steiner hat gesagt:".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "year": {
      "type": "integer",
      "description": "Volumes with lectures held in this year"
    },
    "limit": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1
    },
    "title": {
      "type": "string",
      "description": "Words that must appear in the title (German)"
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "section": {
      "type": "string",
      "description": "e.g. Schriften, Vorträge, Landwirtschaft, Medizin"
    },
    "has_text": {
      "type": "boolean",
      "description": "Only volumes with (true) or without (false) full text"
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • count_matches unknown 7h ago

    Counts how many passages (and chapters/lectures) match a German full-text query, grouped by year, by volume or by place. Useful for questions such as when Steiner spoke most about a topic. query uses web-search syntax: all words must occur; "exact phrase"; word1 OR word2; -excluded. The reply text begins with the fixed phrase "Steiner hat gesagt:".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "ga": {
      "type": "string",
      "description": "Limit to one volume, e.g. \"GA 327\""
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "German search words, e.g.  Ahriman  or  \"soziale Dreigliederung\""
    },
    "date_to": {
      "type": "string",
      "description": "Only lectures on or before this date"
    },
    "group_by": {
      "enum": [
        "year",
        "volume",
        "place"
      ],
      "type": "string",
      "description": "Grouping (default year)"
    },
    "date_from": {
      "type": "string",
      "description": "Only lectures on or after this date (YYYY, YYYY-MM or YYYY-MM-DD)"
    }
  },
  "additionalProperties": false
}
    arguments 36 lines
  • search unknown never probed

    Full-text search across Rudolf Steiner's collected works (German). Returns passages with GA number, title, pages, chapter heading and lecture date, best matches first. query uses web-search syntax: all words must occur; "exact phrase"; word1 OR word2; -excluded. Words are stemmed (German). The reply text begins with the fixed phrase "Steiner hat gesagt:".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "ga": {
      "type": "string",
      "description": "Limit to one volume, e.g. \"GA 327\" or \"327\""
    },
    "limit": {
      "type": "integer",
      "maximum": 30,
      "minimum": 1,
      "description": "Number of results (default 10)"
    },
    "query": {
      "type": "string",
      "minLength": 1,
      "description": "German search words, e.g.  Kuhhorn Mist  or  \"ätherischer Leib\""
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "description": "Skip the first N results (paging)"
    },
    "date_to": {
      "type": "string",
      "description": "Only lectures on or before this date"
    },
    "date_from": {
      "type": "string",
      "description": "Only lectures on or after this date (YYYY, YYYY-MM or YYYY-MM-DD)"
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
  • read unknown never probed

    Reads continuous text from a volume: a whole chapter, a page range, or the passages around a given passage number. Returns up to about 12,000 characters with page numbers; longer selections end with the passage number to continue from. The reply text begins with the fixed phrase "Steiner hat gesagt:".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ga"
  ],
  "properties": {
    "ga": {
      "type": "string",
      "description": "Volume, e.g. \"GA 327\""
    },
    "chapter": {
      "type": "integer",
      "description": "Chapter number within the volume"
    },
    "context": {
      "type": "integer",
      "maximum": 10,
      "minimum": 0,
      "description": "With passage: how many passages before it to include (default 2)"
    },
    "page_to": {
      "type": "integer"
    },
    "passage": {
      "type": "integer",
      "description": "Read from this passage (running number within the volume)"
    },
    "page_from": {
      "type": "integer"
    },
    "continue_from": {
      "type": "integer",
      "description": "Passage number to continue from"
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
  • get_work unknown 7h ago

    Details for one volume plus its table of contents (chapters/lectures with number, heading, date, place and pages). The reply text begins with the fixed phrase "Steiner hat gesagt:".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ga"
  ],
  "properties": {
    "ga": {
      "type": "string",
      "description": "e.g. \"GA 327\""
    }
  },
  "additionalProperties": false
}
    arguments 14 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 57dd56ee69374c4f.

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

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.