Kaal Corpus: Verifiable Claim Layer
MCPB · KAAL-CORPUS.MCPB · 3 COMPONENTS · SCANNED SEP 20
Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security13
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Attribution required. Read, index, quote and cite with attribution to the claim canonical URL.) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 53 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 359 tokens (~71/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 22% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · kaal-corpus.mcpb
Download bundleEvery change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed mcpb/https://github.com/wulfkaal/wulfkaal.github.io/releases/download/mcpb-v1.0.0/kaal-corpus.mcpb@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
corpus_coverage ~56
Report what the corpus contains on a topic: claim count, works, publication span, and failure families. Omit topic for the whole corpus. Returns zero honestly when the corpus does not cover something.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | – |
No output schema declared.
No examples provided.
expertise_profile ~20
Where to find the evidence index of corpus coverage by topic.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
failure_modes ~45
List failure families, or return the claims in one family. Failure knowledge is the densest part of this corpus.
| Name | Type | Req | Description |
|---|---|---|---|
| family | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_claim ~32
Retrieve one claim by id or slug, with its verbatim quote and citation.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_id | string | yes | – |
No output schema declared.
No examples provided.
search_claims ~89
Search the Kaal Corpus claim layer for claims bearing on a question. Returns each claim with a verbatim source quote, a citation string, and a permanent URL to cite.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_type | string | – | – |
| failure_modes_only | boolean | – | – |
| limit | integer | – | – |
| query | string | yes | question or keywords |
| topic | string | – | optional controlled topic filter |
No output schema declared.
No examples provided.
What is the Kaal Corpus: Verifiable Claim Layer MCP server?
Kaal Corpus: Verifiable Claim Layer is an MCP server listed in the public MCP registry as io.github.wulfkaal/corpus. Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF. This page covers its MCPB bundle (https://github.com/wulfkaal/wulfkaal.github.io/releases/download/mcpb-v1.0.0/kaal-corpus.mcpb).
Is the Kaal Corpus: Verifiable Claim Layer MCP server safe to use?
Kaal Corpus: Verifiable Claim Layer scores 48 out of 100 on VerifyMCP. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Kaal Corpus: Verifiable Claim Layer MCP server expose?
Kaal Corpus: Verifiable Claim Layer exposes 5 tools: search_claims, get_claim, corpus_coverage, failure_modes, expertise_profile. Their descriptions and schemas cost roughly 242 tokens of context every time the server is loaded.