SignalHarness.ai MCP Server

by signalharness Your server? Claim it

answering

SignalHarness.ai is answering right now. Last checked 14 min ago. It exposes 3 tools.

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

Uptime history 48 days of history · worst day 0%

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

693 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check SignalHarness.ai every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://signalharness.ai/api/agent/services/mcp

Settings → Connectors → Add custom connector, then paste this address

https://signalharness.ai/api/agent/services/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://signalharness.ai/api/agent/services/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://signalharness.ai/api/agent/services/mcp"
    }
  }
}

.vscode/mcp.json

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

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

invoke

invoke_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.

service

get_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.

services

list_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.

Endpoints

URL	Transport	State	Latency	Checked
https://signalharness.ai/api/agent/services/mcp	streamable-http	answering	578 ms	14 min ago

Alternatives to SignalHarness.ai

same job, measured the same way

Agent Web Reader

by charliemorrison

Pay-per-call data tools for AI agents: crypto signal, web reader, SEO audit. x402 USDC on Base.

3 tools answering

santyvv-data — market & on-chain data

by santyvv

Market and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402).

49 installs/wk 8 tools answering

Boo X402 MCP

by lucle87

Pay-per-call crypto data for AI agents. USDC on Base via x402. No API key.

55 installs/wk local only

Blockrun MCP

by blockrunai

Web search, deep research, prediction markets & crypto data for AI agents. Pay per call via x402.

1 558 installs/wk local only

CryptoPulse Data API

by saascloud

Pay-per-call crypto market intelligence for AI agents. USDC on Base via x402.

31 tools answering

Ventis

by ops119

Crypto data for AI agents: prices, Solana wallets, token risk, swap quotes. Pay per call via x402.

2 tools answering

Fastx402

by tusk80

60+ pay-per-call tools for agents (data, dates, QR, crypto, web), paid in USDC via x402.

97 installs/wk local only

RWA Data MCP Server

by daveabear

Pay-per-call crypto data for agents: metrics, claims, custom briefs. USDC via x402.

9 tools answering

SignalHarness.ai — questions

Answers built from our own checks of this server.

What can SignalHarness.ai do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_service, invoke_service, list_services. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is SignalHarness.ai working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 693 ms. The bar chart above shows every period we have measured.

How do I connect SignalHarness.ai?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does SignalHarness.ai need an API key?

No. SignalHarness.ai completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is SignalHarness.ai?

It answers our handshake in 693 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.