Holdings
Holdings is an MCP server published by getholdings.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 Holdings support the current MCP specification (2026-07-28)?
Not yet confirmed. Holdings 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 Holdings a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for Holdings (as of 2026-08-20).
How do I connect to Holdings?
Holdings is available via a hosted remote endpoint at https://mcp.getholdings.com/mcp, the package npm:@getholdings/mcp, the official MCP Registry under com.getholdings/mcp, the source repository at https://github.com/holdings-io/workspace. Authentication: unknown. Transports: streamable-http.
Does Holdings support MCP revision 2025-11-25?
Yes. Holdings supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Holdings support MCP revision 2026-07-28?
No. Holdings was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Holdings's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Let your AI send invoices and take payment — card or ACH. Free.
Which MCP spec revisions does Holdings support?
Holdings 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 Holdings?
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 Holdings
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
The repository this server declares no longer resolves. That is a measurement, not
a failed lookup: https://github.com/holdings-io/workspace returned 404 when checked.
Package (npm) as of
- Latest version
0.3.0- Last published
- First published
- Releases
- 3
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 2
- Unpacked size
- 49 KB
- 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 com.getholdings/mcp at version 0.1.2 - lists remote endpoint https://mcp.getholdings.com/mcp and repository https://github.com/holdings-io/workspace - accessed
- npm registry metadata for @getholdings/mcp at published version 0.3.0, 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