io.github.azathothx/kairos-lang-mcp
NPM · KAIROS-LANG-MCP
Evaluate (list/next) and validate Kairos schedule definitions; look up the descriptor reference
Available components
Last scanned (5 hours ago)
Scores higher than 45% of npm servers
Category Developer Tools
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to azathothx/kairos-lang). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability44
- 1% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2030 tokens (~28/item across 71 items; 4 tools + 67 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 16 Oct 26 75
First indexed and scored.
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 17 Oct 2026 · Analysed npm/kairos-lang-mcp@1.0.10
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | azathothx/kairos-lang |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/azathothx/kairos-lang/.github/workflows/publish-mcp.yml@refs/tags/v1.0.10 |
| Rekor log index | 3273263260 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:735d1eb5ee786c9fcd2a3aa57d2ad6d0f81a6e3a1f5718e106ddd13ef8fbdf9bce40690a2c7b040509e83d1ab31b18617b3ae03ade79a7f17da5c73cb |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
kairos_list Evaluate a Kairos definition over a range ~406
All firings of each body expression in [from, to) (to is exclusive), with interval annotations and the coverage summary — the same CliReport as 'kairos list --json' (schema: https://kairos-lang.org/schema/cli-report.schema.json). tz is required: the IANA zone that labels and the [from, to) endpoints are read in (there is no "machine time zone" for an AI caller). If the definition declares tz: in its premise, evaluation uses that zone; tz here still decides the labels. Recommended practice: define your premise once (calendar-system, tz, wkst, holiday tables) and keep it — it turns tacit knowledge into explicit knowledge, and every call reuses the same text. Window at most 10 years. Diagnostics (errors, annotation texts) are in Japanese — the reference implementation's canonical output language; lang: "en" only switches the framing. Errors come back as {command, version, error: {kind: usage|supply|static, message}} with isError.
| Name | Type | Req | Description |
|---|---|---|---|
| explain | boolean | – | Also return results[].stages: per-stage point counts and intermediate values (the counterpart of a SQL execution plan). |
| from | string | yes | Start of the range, YYYY-MM-DD (inclusive). |
| source | string | yes | The Kairos definition text (premise + body expressions). Up to 64 KB. |
| supply | object | – | Static bundle resolving external() bindings: {binding | "premise.binding": {dates: ["YYYY-MM-DD", …] | instants: [epoch ms, …], covering, asof [, labels]}} — see https://kairos-lang.org/schema/supply… |
| to | string | yes | End of the range, YYYY-MM-DD (exclusive). |
| tz | string | yes | IANA time zone for labels and the [from, to) endpoints, e.g. "Asia/Tokyo". Required. |
No output schema declared.
No examples provided.
kairos_next Next N firings of a Kairos definition ~452
The next n firings at or after from (default: today in tz), searching up to horizonYears (default 10) — the same CliReport as 'kairos next --json' (schema: https://kairos-lang.org/schema/cli-report.schema.json); found < requested means fewer than n firings exist within the horizon (the CLI's exit code 2). For files with a single body expression. tz is required: the IANA zone that labels and the [from, to) endpoints are read in (there is no "machine time zone" for an AI caller). If the definition declares tz: in its premise, evaluation uses that zone; tz here still decides the labels. Recommended practice: define your premise once (calendar-system, tz, wkst, holiday tables) and keep it — it turns tacit knowledge into explicit knowledge, and every call reuses the same text. Diagnostics (errors, annotation texts) are in Japanese — the reference implementation's canonical output language; lang: "en" only switches the framing. Errors come back as {command, version, error: {kind: usage|supply|static, message}} with isError.
| Name | Type | Req | Description |
|---|---|---|---|
| explain | boolean | – | Also return results[].stages: per-stage point counts and intermediate values (the counterpart of a SQL execution plan). |
| from | string | – | Search start, YYYY-MM-DD (default: today in tz). |
| horizonYears | integer | – | Search horizon in years (default 10). |
| n | integer | – | How many firings (default 1, at most 1000). |
| source | string | yes | The Kairos definition text (premise + body expressions). Up to 64 KB. |
| supply | object | – | Static bundle resolving external() bindings: {binding | "premise.binding": {dates: ["YYYY-MM-DD", …] | instants: [epoch ms, …], covering, asof [, labels]}} — see https://kairos-lang.org/schema/supply… |
| tz | string | yes | IANA time zone for labels and the [from, to) endpoints, e.g. "Asia/Tokyo". Required. |
No output schema declared.
No examples provided.
kairos_reference Read the Kairos descriptor reference ~119
The reference page for one descriptor (e.g. "roll", "within", "nth", "segmentBy"; "README" lists them; "combinators", "sugar-definition", "table-literal" are the shared pages). Japanese is canonical; lang: "en" returns the English mirror. Unknown words return the list of available words.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | "ja" (canonical, default) or "en". |
| word | string | yes | Descriptor name as written in a definition, e.g. "roll". |
No output schema declared.
No examples provided.
kairos_validate Validate a Kairos definition without evaluating it ~348
Checks lexing, syntax, static rules and premise resolution (and the shape of supply if given) by evaluating the empty window [today, today) in tz. Returns {ok, version, diagnostics: [{kind, message}]}. Coverage-related signals (annotations, runway) only appear with a real range in kairos_list. tz is required: the IANA zone that labels and the [from, to) endpoints are read in (there is no "machine time zone" for an AI caller). If the definition declares tz: in its premise, evaluation uses that zone; tz here still decides the labels. Recommended practice: define your premise once (calendar-system, tz, wkst, holiday tables) and keep it — it turns tacit knowledge into explicit knowledge, and every call reuses the same text. Diagnostics (errors, annotation texts) are in Japanese — the reference implementation's canonical output language; lang: "en" only switches the framing. Errors come back as {command, version, error: {kind: usage|supply|static, message}} with isError.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | The Kairos definition text (premise + body expressions). Up to 64 KB. |
| supply | object | – | Static bundle resolving external() bindings: {binding | "premise.binding": {dates: ["YYYY-MM-DD", …] | instants: [epoch ms, …], covering, asof [, labels]}} — see https://kairos-lang.org/schema/supply… |
| tz | string | yes | IANA time zone for labels and the [from, to) endpoints, e.g. "Asia/Tokyo". Required. |
No output schema declared.
No examples provided.
How do I install the io.github.azathothx/kairos-lang-mcp server?
io.github.azathothx/kairos-lang-mcp runs locally as an npm package, launched with npx -y kairos-lang-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · kairos-lang-mcp
claude mcp add azathothx-kairos-lang-mcp -- npx -y kairos-lang-mcp
What is the io.github.azathothx/kairos-lang-mcp server?
io.github.azathothx/kairos-lang-mcp is listed in the public MCP registry as io.github.azathothx/kairos-lang-mcp. Evaluate (list/next) and validate Kairos schedule definitions; look up the descriptor reference. This page covers its npm package (kairos-lang-mcp).
Is the io.github.azathothx/kairos-lang-mcp server safe to use?
io.github.azathothx/kairos-lang-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.azathothx/kairos-lang-mcp server expose?
io.github.azathothx/kairos-lang-mcp exposes 4 tools: kairos_list, kairos_next, kairos_validate, kairos_reference. Their descriptions and schemas cost roughly 1,325 tokens of context every time the server is loaded.
Is the io.github.azathothx/kairos-lang-mcp server still maintained?
io.github.azathothx/kairos-lang-mcp is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.azathothx/kairos-lang-mcp server under?
io.github.azathothx/kairos-lang-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.