THRONE
See report Verify server

registry / record

chroma-mcp

uvx / sealed 2026-06-12 / No. fd07f042

> throne registry chroma-mcp sealed
receiptsealed evidence
scan id
fd07f04270ff48e5a4318006f47ae514
target
uvx chroma-mcp
sealed at
2026-06-12 18:30:26Z
evidence hash
sha256:4b0a7aa00cc5013389f84f86ca2172927134ce74d422095eba2f5dc99ea20c10
01connectPASS1.2s

initialize ok: server chroma 1.6.0, negotiated protocolVersion 2024-11-05, capabilities ['experimental', 'prompts', 'resources', 'tools']

02discoverPASS12ms

supported: tools/list (13 tools), resources/list (0), prompts/list (0)

03validate_schemasPASS33ms

all 13 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS70ms

called 10 of 10 tools (cap 10): 7 ok, 3 returned tool-level errors (expected for synthesized args)

05error_handlingWARN6.3s

survived probes but no structured error response — wrong_type_args: accepted (returned result); unknown_method: no response (silent), connection alive; invalid_id: unexpected: {'_unparseable': 'Successfully initialized Chroma client'}

06streamingPASS1ms

no streaming-capable tool declared by this server; not applicable (pass-na)

07resource_lifecyclePASS5ms

server declares resources but lists none; read skipped (pass-na)

08concurrent_callsPASS40ms

ladder 1/2/4/8 overlapping chroma_list_collections calls: max_observed_stable_concurrency=8; all ids answered exactly once at every level

09reconnectPASS3.2s

transport closed and relaunched; re-handshake ok (protocolVersion 2024-11-05, first session was 2024-11-05)

01connectPASS962ms

initialize ok: server chroma 1.6.0, negotiated protocolVersion 2024-11-05, capabilities ['experimental', 'prompts', 'resources', 'tools']

02discoverPASS21ms

supported: tools/list (13 tools), resources/list (0), prompts/list (0)

03validate_schemasPASS31ms

all 13 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS106ms

called 10 of 10 tools (cap 10): 7 ok, 3 returned tool-level errors (expected for synthesized args)

05error_handlingWARN6.4s

survived probes but no structured error response — wrong_type_args: accepted (returned result); unknown_method: no response (silent), connection alive; invalid_id: unexpected: {'_unparseable': 'Successfully initialized Chroma client'}

06streamingPASS1ms

no streaming-capable tool declared by this server; not applicable (pass-na)

07resource_lifecyclePASS36ms

server declares resources but lists none; read skipped (pass-na)

08concurrent_callsPASS53ms

ladder 1/2/4/8 overlapping chroma_list_collections calls: max_observed_stable_concurrency=8; all ids answered exactly once at every level

09reconnectPASS3.3s

transport closed and relaunched; re-handshake ok (protocolVersion 2024-11-05, first session was 2024-11-05)

chatgpt desktopemulation profile pending real-traffic captureCOMING SOON
SECURITY: CLEAN / no findings
VERDICT: FIT TO SHIPSANDBOXED RUN — submitted server executed in a disposable microVM — compatibility: 0 fail / 2 warn across 2 clients / security: clean, 0 findingssealed by THRONE / No. fd07f042 / 2026-06-12
THRONE: FIT TO SHIPwear the crown

paste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.

[![THRONE: FIT TO SHIP](https://api.usethrone.dev/api/badge/uvx%20chroma-mcp)](https://usethrone.dev/server/chroma-mcp)
executed in a disposable microVM, created for this scan and destroyed after it. nothing outlives a run.

maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.

this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.