Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
NPM Package Ws Has 241560546 Weekly Downloads But SDK is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
5
tools declared
remote
at its publisher
—
calls last 7d
What it does
Stateful WebSocket session registry with per-connection Shannon entropy delta tracking for schema di
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http npm-package-ws-has-241560546-weekly-downloads-mcp https://npm-package-ws-has-241560546-w-production.up.railway.app/mcp
# 2 — ask your agent for something these tools do
# nexus_npm_package_ws_has_241560546_weekly_down_open_websocket_session, nexus_npm_package_ws_has_241560546_weekly_down_send_typed_ws_frame, nexus_npm_package_ws_has_241560546_weekly_down_drain_ws_frame_buffer and 2 more
NPM Package Ws Has 241560546 Weekly Downloads But SDK costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NMAll 7 servers
nexus-mcp-infra7 servers
6 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http npm-package-ws-has-241560546-weekly-downloads-mcp https://npm-package-ws-has-241560546-w-production.up.railway.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Establishes a persistent WebSocket connection to a target URL and registers it in the stateful session registry. Returns a session_id for all subsequent operations. Use when an agent needs to initiate a long-lived connection before sending or receiving frames. Do NOT use to reconnect an already-open session -- call close_websocket_session first, or use the session_id of an existing session.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target_url | string | yes | Full WebSocket URL to connect to (must start with ws:// or wss://). |
| connect_timeout_seconds | number | no | Maximum seconds to wait for the WebSocket handshake to complete. |
Sends a single text or binary frame over an open session and returns the frame's Shannon entropy delta relative to the session baseline. Use for request-response patterns or publishing commands to a WebSocket server. Do NOT use to send a sequence of frames in bulk -- call this tool once per frame. Fails if session_id does not exist or connection is not in OPEN state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | 32-character session id (uuid4 hex, no dashes) returned by open_websocket_session. |
| payload | string | yes | Frame payload. For binary frames, encode as hex and set frame_type to 'binary'. |
| frame_type | string | no | Either 'text' or 'binary'. Determines wire encoding. |
Returns up to max_frames buffered inbound frames received since the last drain (or session open), each annotated with its Shannon entropy delta and schema validation result. Use to poll for incoming messages without holding a blocking connection. Do NOT use as a real-time streaming mechanism -- it returns only frames already buffered.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | 32-character session id of the open session to drain frames from. |
| max_frames | number | no | Maximum number of buffered frames to return in a single call. |
Returns real-time telemetry for a session: connection state, frame counts, cumulative and rolling Shannon entropy statistics, schema violation rate, and uptime. Use to diagnose whether a stream is diverging from its expected schema or to verify a session is still alive before sending. Do NOT use as the primary liveness check in a tight loop.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | 32-character session id of the session to inspect. |
Sends a WebSocket close frame with the specified status code, waits for the server close handshake, and removes the session from the registry. Returns a final telemetry snapshot. Use when a session is no longer needed. Do NOT use to temporarily pause a session -- the session_id is permanently deallocated after this call and cannot be reused.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session_id | string | yes | 32-character session id of the session to close. |
| status_code | number | no | WebSocket close status code per RFC 6455 (1000-4999). Defaults to 1000. |
| reason | string | no | Optional UTF-8 close reason string, max 123 bytes per RFC 6455. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install NPM Package Ws Has 241560546 Weekly Downloads But SDK or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest61e178d3e2d049b48020a1542f478d1dd8adcbb581c6e6a0576510e0c57750df
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| nexus_npm_package_ws_has_241560546_weekly_down_open_websocket_session | no tags | |
| nexus_npm_package_ws_has_241560546_weekly_down_send_typed_ws_frame | no tags | |
| nexus_npm_package_ws_has_241560546_weekly_down_drain_ws_frame_buffer | no tags | |
| nexus_npm_package_ws_has_241560546_weekly_down_inspect_ws_session_telemetry | no tags | |
| nexus_npm_package_ws_has_241560546_weekly_down_close_websocket_session | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest61e178d3e2d049b4
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish NPM Package Ws Has 241560546 Weekly Downloads But SDK can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.