SignalHarness.ai
REMOTE · SIGNALHARNESS.AI
330 production AI-agent services for data, validation, AI, crypto, and x402 pay-per-use.
Available components
Last scanned (3 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 17 Oct 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 397 tokens (~132/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 53 to 63. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +62
- Authorization: unverified → partial ▲ security
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.37 ▲ functional
- 1 Oct 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.30 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://signalharness.ai/api/agent/services/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=signalharness.ai | CN=YE2,O=Let's Encrypt,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6e99b6d7498a2613096cce8b805a22eca5e |
| SANs: signalharness.ai, www.signalharness.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of signalharness.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| signalharness.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://signalharness.ai/api/agent/services/mcp | Verified | 200 | |
| http (plaintext) | http://signalharness.ai/api/agent/services/mcp | HTTPS enforced | 301 | https://signalharness.ai/api/agent/services/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_service Get SignalHarness service ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service_id | string | yes | Exact canonical service ID from list_services; matching is case-sensitive and aliases are not accepted. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Stable machine error code when the service cannot be returned. |
| input_schema | object | – | JSON Schema the invoke_service input must satisfy. |
| output_schema | object | – | JSON Schema describing the service-specific success result. |
| service_id | string | – | Exact canonical service ID. |
No examples provided.
invoke_service Invoke SignalHarness service ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | – | Optional stable key for retrying the same logical job safely. Reuse it only for recovery of that same job and payment. |
| input | object | yes | Caller-supplied job data. It must satisfy the selected service input_schema returned by get_service. |
| request_id | string | – | Optional caller-generated request identifier for tracing this attempt. Never place secrets or payment credentials in it. |
| service_id | string | yes | Exact canonical ID of an enabled public service, obtained from list_services. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Stable machine error code for unpaid, invalid, failed, or unavailable requests. |
No examples provided.
list_services List SignalHarness services ~65
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Stable machine error code when catalog discovery fails. |
| schemaVersion | – | – | Catalog schema version when supplied by the runtime. |
| services | array | – | Enabled public services in canonical catalog order. Each item includes its exact service ID and available discovery and payment fields. |
No examples provided.
How do I install the SignalHarness.ai MCP server?
SignalHarness.ai is a hosted endpoint at https://signalharness.ai/api/agent/services/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · signalharness.ai
claude mcp add --transport http ai-signalharness-mcp 'https://signalharness.ai/api/agent/services/mcp'
What is the SignalHarness.ai MCP server?
SignalHarness.ai is an MCP server listed in the public MCP registry as ai.signalharness/mcp. 330 production AI-agent services for data, validation, AI, crypto, and x402 pay-per-use. This page covers its hosted endpoint (https://signalharness.ai/api/agent/services/mcp).
Is the SignalHarness.ai MCP server safe to use?
SignalHarness.ai scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SignalHarness.ai MCP server expose?
SignalHarness.ai exposes 3 tools: list_services, get_service, invoke_service. Their descriptions and schemas cost roughly 372 tokens of context every time the server is loaded.
Does the SignalHarness.ai MCP server require authentication?
No. We connected to SignalHarness.ai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SignalHarness.ai MCP server still maintained?
SignalHarness.ai is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.