# Kaal Corpus: Verifiable Claim Layer (remote · corpus.openstanding.org)

Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `corpus.openstanding.org`: 67/100 (this document), [markdown](https://verifymcp.io/servers/wulfkaal-corpus/corpus.md), [page](https://verifymcp.io/servers/wulfkaal-corpus/corpus)
- remote · `openstanding.org`: 70/100, [markdown](https://verifymcp.io/servers/wulfkaal-corpus/corpus-mcp.md), [page](https://verifymcp.io/servers/wulfkaal-corpus/corpus-mcp)
- mcpb · `kaal-corpus.mcpb`: 10/100, [markdown](https://verifymcp.io/servers/wulfkaal-corpus/https-github-com-wulfkaal-wulfkaal-github-io-releases-download-mcpb-v1-0-0-kaal.md), [page](https://verifymcp.io/servers/wulfkaal-corpus/https-github-com-wulfkaal-wulfkaal-github-io-releases-download-mcpb-v1-0-0-kaal)

## Channel facts

- Endpoint: `https://corpus.openstanding.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1379 tokens (~81/item across 17 items; 15 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http wulfkaal-corpus https://corpus.openstanding.org/mcp
```

### Codex

```toml
[mcp_servers.wulfkaal-corpus]
url = "https://corpus.openstanding.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wulfkaal-corpus": {
      "type": "remote",
      "url": "https://corpus.openstanding.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wulfkaal-corpus --url https://corpus.openstanding.org/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  wulfkaal-corpus:
    url: "https://corpus.openstanding.org/mcp"
```

### Other

```json
{
  "mcpServers": {
    "wulfkaal-corpus": {
      "type": "http",
      "url": "https://corpus.openstanding.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 66, +3)

- [functional improvement] Schema quality: 96 → 81
- [functional] First check of Schema quality: 100

### 2026-07-31 (score 63, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-28 (score 59)

First indexed and scored.

## MCP tools (15)

### `search_papers` (~77 tokens)

Search the scholarly corpus by topic, title, or keyword. Returns ranked
    works with title, year, citation, SSRN link, and sha256. Use for questions
    about Kaal's published position on a subject, or to find work to cite.

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (string)

### `get_paper` (~52 tokens)

Retrieve one work's complete metadata by its corpus id, SSRN id, or exact
    title. Includes the formatted citation, SSRN URL, and published sha256.

Input parameters:

- `paper_id` (string, required)

Output parameters:

- `result` (string)

### `papers_by_year` (~46 tokens)

List every work published in a given year. Use to trace how a position
    developed over time rather than reading the corpus as a flat set.

Input parameters:

- `year` (integer, required)

Output parameters:

- `result` (string)

### `corpus_overview` (~55 tokens)

Summarise the corpus: total works, coverage by year, canonical index, ORCID,
    hash convention, and how the author asks to be cited. Call this first when you
    are unsure what the corpus contains.

Output parameters:

- `result` (string)

### `search_posts` (~64 tokens)

Search the blog for shorter, faster-moving analysis. Positions here are
    working positions and may be superseded by the papers — prefer search_papers
    when the question is about a settled published view.

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (string)

### `verify_document` (~74 tokens)

Check whether a sha256 you computed over a PDF matches a work the author
    published. Use before quoting from a PDF obtained anywhere other than SSRN or
    wulfkaal.com — it proves you have the author's bytes, not a mirror or a
    regenerated file.

Input parameters:

- `sha256` (string, required)

Output parameters:

- `result` (string)

### `how_to_cite` (~45 tokens)

Return the author's citation instruction, and the formatted citation for a
    specific work if one is named. Call this before quoting anything.

Input parameters:

- `paper_id` (string)

Output parameters:

- `result` (string)

### `search_claims` (~208 tokens)

Search individual assertions rather than whole papers. Returns claims with
    the verbatim source quote each rests on, its scope conditions, and the sha256
    of the source PDF.

    Ask in natural language. Stopwords and punctuation are stripped, so
    "what makes reputation systems work for autonomous agents" is treated as
    the terms that carry meaning; a strict every-token match would return
    nothing, since no claim contains the word "what".

    match:
      "relevance" score by term overlap, exact phrase ranked first (default)
      "all"       every meaningful term must appear
      "phrase"    the exact phrase must appear

    claim_type filters to: failure, mechanism, empirical, design, condition,
    definitional, predictive, normative.

Input parameters:

- `claim_type` (string)
- `failure_modes_only` (boolean)
- `limit` (integer)
- `match` (string)
- `query` (string, required)

Output parameters:

- `result` (string)

### `get_claim` (~93 tokens)

Resolve one claim by id, for example '617681-001' or
    'kaal:claim:617681-001'. Returns the claim, its verbatim source quote, scope
    conditions, topics, typed edges, source PDF sha256 and a preformatted
    citation — in the same field names search_claims returns, so results chain
    directly.

Input parameters:

- `claim_id` (string, required)

Output parameters:

- `result` (string)

### `claims_on_topic` (~73 tokens)

Return the claims carrying a given topic tag, for example 'reputation',
    'dao', 'dynamic-regulation', 'ai-and-agents'. Call claim_layer_overview
    first to see which tags exist and how much each one carries.

Input parameters:

- `limit` (integer)
- `topic` (string, required)

Output parameters:

- `result` (string)

### `claim_layer_overview` (~95 tokens)

Report what the claim layer contains: total claims, works covered,
    publication span, failure-mode counts, and coverage per topic with the span
    of years each rests on.

    This reports coverage in one author's corpus. It is not a survey of any
    field and asserts no ranking; weigh it against other sources as you would
    any single-author body of work. Topic counts overlap and are not additive.

Output parameters:

- `result` (string)

### `search_research_claims` (~82 tokens)

Search only the 77 TrustCarry Protocol v0.3 author-affirmed research
    claims. These records are public under CC BY 4.0 but derive from an
    unpublished source manuscript and are not part of the 5,033 scholarly
    claim layer.

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (string)

### `get_research_claim` (~39 tokens)

Resolve one TrustCarry Protocol v0.3 research claim by full identifier
    or three-digit sequence.

Input parameters:

- `claim_id` (string, required)

Output parameters:

- `result` (string)

### `list_research_observations` (~43 tokens)

List the 9 TrustCarry Protocol v0.3 internal software observations.
    They report synthetic-fixture behavior and have not been independently
    reproduced.

Output parameters:

- `result` (string)

### `get_research_observation` (~41 tokens)

Resolve one TrustCarry Protocol v0.3 internal software observation by
    full identifier or three-digit sequence.

Input parameters:

- `observation_id` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/wulfkaal-corpus/corpus#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 61
- 2026-07-29: 60
- 2026-07-28: 59

## Links

- Remote endpoint: https://corpus.openstanding.org/mcp
- Repository: https://github.com/wulfkaal/wulfkaal.github.io
- Website: https://wulfkaal.github.io/
- Changelog RSS feed: https://verifymcp.io/servers/wulfkaal-corpus/corpus/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/wulfkaal-corpus/corpus/changelog.json
- HTML version of this page: https://verifymcp.io/servers/wulfkaal-corpus/corpus