Productivity · Remote MCP server
Kaal Corpus: Verifiable Claim Layer
Cite the claim, not the paper: 5,033 assertions, each hash-verifiable against its source PDF.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.wulfkaal/corpus- Version
- 1.0.1
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- MCP Bundle (.mcpb)
- Published
- 2026-07-28
- Updated
- 2026-07-28
- Publisher
- wulfkaal (GitHub)
- Listed under
- PDF MCP servers
- Website
- wulfkaal.github.io/
- Repository
- github.com/wulfkaal/wulfkaal.github.io
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://corpus.openstanding.org/mcp | None |
| Streamable HTTP | https://openstanding.org/corpus/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| MCP Bundle (.mcpb) | https://github.com/wulfkaal/wulfkaal.github.io/releases/download/mcpb-v1.0.0/kaal-corpus.mcpbSHA-256 checksum stated | 1.0.0 | stdio |
How to connect Kaal Corpus: Verifiable Claim Layer
Kaal Corpus: Verifiable Claim Layer is a remote MCP server: there is nothing to install. Its endpoints are https://corpus.openstanding.org/mcp and https://openstanding.org/corpus/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from an MCP Bundle: a single downloadable archive holding a local server and a manifest that describes it: https://github.com/wulfkaal/wulfkaal.github.io/releases/download/mcpb-v1.0.0/kaal-corpus.mcpb version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs a client that installs MCP Bundles; the file is opened in, or added to, that client.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| JuscribeRead and work your Juscribe board: tickets, subtasks, blockers, projects and iterations. | Local · stdio |
| JustEmailsEmail hosting from your AI: read and send mail, add domains, check DNS and manage mailboxes. | Remote · HTTP |
| JustFill PDF Form AutomationDetect, review and fill existing PDF forms from JSON or Excel; reuse saved templates. | Remote & Local · HTTP, stdio |
| K-Work TrustKorean business record validation and workflow safety gates for AI agents. | Remote · HTTP |
| KaganAI-powered Kanban TUI for autonomous development workflows with agent orchestration. | Local · stdio |
| KaikuIssue tracker and wiki for teams and their agents: find, file and update issues, write pages. | Remote · HTTP |
| KairosMicrosoft Planner MCP: create tasks and buckets, list plans and tasks, complete tasks. | Local · stdio |
| Kairos ConnectConnect AI agents to your Kairos workspace — manage goals, tasks, docs, whiteboards, and forms. | Remote · HTTP |