Kaal Corpus: Verifiable Claim Layer
MCPB · KAAL-CORPUS.MCPB · 3 COMPONENTS
Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF
Available components
Last scanned (8 hours ago)
Scores higher than 76% of MCPB servers
Category Education and Research
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).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 99 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every 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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 −2
- Stability: pass → 0.83 functional
- 14 Oct 26 +1
- Stability: 0.97 → pass security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 93. That category is still filling its 30-day observation window: 26 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 5 Nov 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 |
| Reason | No attestation published |
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.
How do I install the Kaal Corpus: Verifiable Claim Layer MCP server?
Kaal Corpus: Verifiable Claim Layer ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · kaal-corpus.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
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 46 out of 100 on VerifyMCP. 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.