Skip to content
Back to the index

scream-void

pipeworx.ioInfrastructure

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

Scream Void is an MCP server exposing a single tool for submitting text with optional intensity settings. It provides a JSON-RPC endpoint, schemas, code samples, and a live playground for developers integrating the tool with AI agents.

Inferred · not functionally tested

WebAPICloud-managed
scream-void preview
Visit pipeworx.io

Overview

6 features

Purpose: Submitting text-based expressions to an MCP-compatible tool endpoint for agent workflows.

Inferred · not functionally tested

Audience: developers building AI agent integrations

Inferred · not functionally tested

Functions: agents

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

scream-void sits in PulseGate's Frameworks & runtimes category. Inferred · not functionally tested: It focuses on submitting text-based expressions to an MCP-compatible tool endpoint for agent workflows. Inferred · not functionally tested: It is built as a B2B product for developers building AI agent integrations. Basis unknown · not verified: It runs on the web and API.

It is developed by Pipeworx. Inferred · not functionally tested: Key capabilities include MCP server, JSON-RPC endpoint, and scream submission. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • MCP server
  • JSON-RPC endpoint
  • Scream submission
  • Intensity options
  • Tool schema
  • Code samples

Topics: Inferred · not functionally tested

Tags
mcp-serverjson-rpc-endpointai-agent-tool
AI capabilities
Text
Inference: Cloud API

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCPAPI
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 00:02 UTC
    Scream Void seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about scream-void

What does scream-void do?
Inferred · not functionally tested: Scream-void focuses on submitting text-based expressions to an MCP-compatible tool endpoint for agent workflows. It is catalogued under Frameworks & runtimes on PulseGate.
Who is scream-void for?
Inferred · not functionally tested: scream-void is a B2B product built for developers building AI agent integrations.
What platforms does scream-void run on?
Basis unknown · not verified: scream-void runs on the web and API.
Is scream-void still maintained?
Unverified. scream-void has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What are alternatives to scream-void?
Similar projects tracked by PulseGate include slack_connect, ship-on-friday, and send-that-email.slack_connectship-on-fridaysend-that-email
Who develops scream-void?
scream-void is developed by Pipeworx.
Does scream-void have an API or integrations?
Inferred · not functionally tested: Yes — scream-void exposes an MCP server and a public API.

Also in Frameworks & runtimes

Same category — not a similarity match