SignalHarness.ai

ai.signalharnessPublished by signalharness.aiOfficial publisherv1.0.0Updated Nov 1, 2026

330 production AI-agent services for data, validation, AI, crypto, and x402 pay-per-use.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

SignalHarness.ai is a remote MCP endpoint offering a catalog of production AI-agent services for data, validation, AI, crypto and pay-per-use access.

What you can do
Access a catalog of production AI-agent services spanning data, validation, AI and crypto use cases, as described by the provider. Use pay-per-use services billed through x402, a payment scheme named in the description. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to reach a hosted collection of ready-made agent services rather than building integrations yourself, particularly for data, validation, AI or crypto tasks.
Requirements
A remote MCP client connecting over streamable HTTP to the provider's endpoint. No authentication, environment variables or headers are declared in the manifest, and no local package is needed.
Before you install
The description mentions x402 pay-per-use, so some services may charge money per call; confirm pricing before use. No authentication is declared, so how access and billing are tied to a user is unclear. The manifest lists no tools, so capabilities cannot be verified in advance.

Installation

In SourceWeft

  1. Open SignalHarness.ai in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.signalharness%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "signalharness-ai": {
      "type": "http",
      "url": "https://signalharness.ai/api/agent/services/mcp"
    }
  }
}

Tools

3

list_services

List SignalHarness services

Discover the currently enabled public SignalHarness service catalog before choosing a service. This free, read-only call takes no arguments and returns a compact service array with canonical IDs, descriptions, prices, and supported payment metadata. Results follow the canonical catalog order; compare services by their exact service_id.

Takes no parameters.

get_service

Get SignalHarness service

Inspect one enabled public SignalHarness service before invoking it. Use an exact service_id returned by list_services. This free, read-only call returns the canonical description, input and output schemas, price, endpoint, and supported payment metadata when available; an unknown or disabled ID returns a normalized not-found error.

Parametersservice_idrequired

invoke_service

Invoke SignalHarness service

Run exactly one enabled public SignalHarness service with caller-supplied input. Call get_service first and validate input against its input_schema. An unpaid call returns the canonical x402 V2 PAYMENT-REQUIRED challenge plus the equivalent x402 V1 JSON challenge; a client can then retry once with payment in params._meta["x402/payment"]. The server never retries automatically. A paid call may settle the advertised charge and perform external work, then returns service-specific structured JSON or a normalized error.

Parametersinputrequiredrequest_idservice_idrequiredidempotency_key

Version history

1
  1. v1.0.0LatestSep 21, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.