Skip to content
External endpointresponds

Kaal Corpus

Search 124 law papers on DAOs, AI governance, and regulation; verify PDFs by hash

Endpoint URL
https://openstanding.org/corpus/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
404 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.wulfkaal/corpus

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Kaal Corpus
Version
1.28.1
Capability keys
experimental, prompts, resources, tools
Tool names
search_papers, get_paper, papers_by_year, corpus_overview, search_posts, verify_document, how_to_cite, search_claims, get_claim, claims_on_topic, search_positions, get_position, positions_on_topic, claim_layer_overview, search_research_claims, get_research_claim, list_research_observations, get_research_observation
Instructions excerpt

The scholarly corpus of Prof. Wulf A. Kaal (Professor of Law, University of St. Thomas): two decades of work on decentralized governance, DAOs, AI agent coordination, reputation systems, dynamic regulation, digital assets and securities law. Use search_papers to find work by topic, get_paper for a single work's full metadata and citation, search_posts for shorter blog analysis, and verify_document to confirm a PDF you hold matches the author's published sha256. The corpus is also published at claim resolution: search_claims finds individual assertions, get_claim resolves one by id, claims_on_topic returns a topic slice, and claim_layer_overview reports coverage. Claim tools return the supporting quote and the source PDF hash, so any statement can be checked against the original document. Public dated commentary is a separate layer: search_positions finds owner-authorized response positions, get_position resolves one record, and positions_on_topic returns an explicit topic-tag slice. A

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 325ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 289ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 398ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 404ms