THRONE
See report Verify server

registry / record

@modelcontextprotocol/server-everything

npm / sealed 2026-06-14 / No. bbf0a47e

> throne registry @modelcontextprotocol/server-everything sealed
receiptsealed evidence
scan id
bbf0a47ebaa84a3da3188daa012decf6
target
@modelcontextprotocol/server-everything
sealed at
2026-06-14 17:05:48Z
evidence hash
sha256:feb0ffd8f2225c2e1a56dcb136e06beaf2d3098040a183b61a7e9ced46e4318e
01connectPASS1.0s

initialize ok: server mcp-servers/everything 2.0.0, negotiated protocolVersion 2025-11-25, capabilities ['completions', 'logging', 'prompts', 'resources', 'tasks', 'tools']

02discoverPASS13ms

supported: tools/list (13 tools), resources/list (7), prompts/list (4)

03validate_schemasPASS4ms

all 13 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS198ms

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

05error_handlingPASS4.1s

structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive

06streamingPASS2.0s

trigger-long-running-operation: 4 progress notifications, monotonic, final result received

07resource_lifecyclePASS6ms

read demo://resource/static/document/architecture.md (1 content blocks); subscribe/unsubscribe acknowledged

08concurrent_callsPASS9ms

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

09reconnectPASS3.6s

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

01connectPASS952ms

initialize ok: server mcp-servers/everything 2.0.0, negotiated protocolVersion 2025-11-25, capabilities ['completions', 'logging', 'prompts', 'resources', 'tasks', 'tools']

02discoverPASS13ms

supported: tools/list (13 tools), resources/list (7), prompts/list (4)

03validate_schemasPASS4ms

all 13 tool inputSchemas are valid JSON Schema

04smoke_test_toolsPASS128ms

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

05error_handlingPASS4.1s

structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive

06streamingPASS2.0s

trigger-long-running-operation: 4 progress notifications, monotonic, final result received

07resource_lifecyclePASS6ms

read demo://resource/static/document/architecture.md (1 content blocks); subscribe/unsubscribe acknowledged

08concurrent_callsPASS7ms

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

09reconnectPASS3.4s

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

chatgpt desktopemulation profile pending real-traffic captureCOMING SOON
SECURITY: REVIEW / 2 finding(s) / review material, not a verdict
LOWTHR-OBF-06 / Obfuscated embedded payload

base64-like blob of 5380 chars

package/dist/tools/get-tiny-image.js:2
LOWTHR-INSTALL-03 / Install-time script execution (npm lifecycle)

"prepare" runs on git-dependency installs and local dev (not registry installs): 'npm run build'

package/package.json
VERDICT: FIT TO SHIPSANDBOXED RUN — submitted server executed in a disposable microVM — compatibility: 0 fail / 0 warn across 2 clients / security: review — 2 finding(s), 0 highsealed by THRONE / No. bbf0a47e / 2026-06-14
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/%40modelcontextprotocol%2Fserver-everything)](https://usethrone.dev/server/modelcontextprotocol-server-everything)
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.