Callosium
Callosium is an MCP server published by callosium, 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 Callosium support the current MCP specification (2026-07-28)?
Not yet confirmed. Callosium 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 Callosium a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Callosium (as of 2026-08-20).
How do I connect to Callosium?
Callosium is available via the package npm:callosium, the official MCP Registry under io.github.callosium/callosium, the source repository at https://github.com/callosium/callosium. Authentication: unknown. Transports: stdio.
Does Callosium support MCP revision 2025-11-25?
Yes. Callosium supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Callosium support MCP revision 2026-07-28?
No. Callosium was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Callosium's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
One shared memory for every AI you use, in plain Markdown files you own.
Which MCP spec revisions does Callosium support?
Callosium 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 Callosium?
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 Callosium
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
- 8
- Forks
- 0
- Last pushed
- (59 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- Apache-2.0
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: ai-memory, ai-memory-layer, ai-memory-management, ai-memory-system, ai-memory-vault, knowledge-base, knowledge-distillation, knowledge-management, knowledgebase — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.1.18- Last published
- First published
- Releases
- 19
- License (package)
- Apache-2.0
- Maintainers
- 1
- Direct dependencies
- 5
- Unpacked size
- 8.4 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).
- Official MCP Registry record for io.github.callosium/callosium at version 0.1.18 - lists package npm:callosium and repository https://github.com/callosium/callosium - accessed
- npm registry metadata for callosium at published version 0.1.18, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- 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