MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

kage

Earlier Revision Publisher unverified Confidence: Good (0.85)

kage is an MCP server published by kage-core.com, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.

Does kage support the current MCP specification (2026-07-28)?

Not yet confirmed. kage is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.

Is kage a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for kage (as of 2026-08-20).

How do I connect to kage?

kage is available via the package npm:@kage-core/kage-graph-mcp, the official MCP Registry under com.kage-core/kage, the source repository at https://github.com/kage-core/kage. Authentication: unknown. Transports: stdio.

Does kage support MCP revision 2025-11-25?

Yes. kage supports MCP revision 2025-11-25 (checked 2026-08-20).

Does kage support MCP revision 2026-07-28?

No. kage was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).

When were kage's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

Verified memory for coding agents: claims cited against code, stale withheld, savings receipts.

Which MCP spec revisions does kage support?

kage has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Not supported Source

How widely adopted is kage?

Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.

Repository and package signals for kage

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Stars
32
Forks
1
Last pushed
(41 days ago)
Created
Open issues
8
Primary language
TypeScript
License (repository)
GPL-3.0
Continuous integration
Present
Tests
None detected
Security policy
None

Declared topics: agent-memory, ai-agents, claude-code, code-graph, codex, cursor, developer-tools, knowledge-graph, mcp, mcp-server — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
5.0.0
Last published
First published
Releases
80
License (package)
GPL-3.0-only
Maintainers
1
Direct dependencies
6
Unpacked size
2.5 MB
Registry signature
Signed
Build provenance
No attestation

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for com.kage-core/kage at version 2.3.0 - lists package npm:@kage-core/kage-graph-mcp and repository https://github.com/kage-core/kage - accessed
  2. npm registry metadata for @kage-core/kage-graph-mcp at published version 3.1.0, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
  3. Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed