Licence audit, page read and endpoint check - paid over x402 (AI-operated)
REMOTE · OMNIA-SELL.RJHSIGNALTECH.WORKERS.DEV · SCANNED OCT 15
AI-operated. All tools paid: an unpaid tools/call answers HTTP 402 with x402 terms, USDC on Base.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Licence audit, page read and endpoint check - paid over… MCP server?
Licence audit, page read and endpoint check - paid over… is a hosted endpoint at https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro, 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 · omnia-sell.rjhsignaltech.workers.dev
claude mcp add --transport http dev-workers-rjhsignaltech-ai-licence-audit-paid 'https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro'
{
"mcpServers": {
"dev-workers-rjhsignaltech-ai-licence-audit-paid": {
"url": "https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro"
}
}
} {
"servers": {
"dev-workers-rjhsignaltech-ai-licence-audit-paid": {
"type": "http",
"url": "https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro"
}
}
} [mcp_servers.dev-workers-rjhsignaltech-ai-licence-audit-paid] url = "https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-workers-rjhsignaltech-ai-licence-audit-paid": {
"type": "remote",
"url": "https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro",
"enabled": true
}
}
} openclaw mcp add dev-workers-rjhsignaltech-ai-licence-audit-paid --url 'https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro' --transport streamable-http
mcp_servers:
dev-workers-rjhsignaltech-ai-licence-audit-paid:
url: "https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro" {
"McpServers": {
"dev-workers-rjhsignaltech-ai-licence-audit-paid": {
"Transport": "http",
"Url": "https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro"
}
}
} assistant mcp add dev-workers-rjhsignaltech-ai-licence-audit-paid -t streamable-http -u 'https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro'
{
"mcpServers": {
"dev-workers-rjhsignaltech-ai-licence-audit-paid": {
"type": "http",
"url": "https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.53 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 15 Oct 2026 · Probed https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rjhsignaltech.workers.dev | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f13dfedf01f30dd20eac24f97f72fc8f |
| SANs: rjhsignaltech.workers.dev, *.rjhsignaltech.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of omnia-sell.rjhsignaltech.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro | HTTP error | 404 | |
| http (plaintext) | http://omnia-sell.rjhsignaltech.workers.dev/mcp-pro | Inconclusive | 404 |
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 →
endpoint_check_full ~112
PAID (0.02 USDC over x402 on Base). Checks an HTTPS endpoint and returns the status code, elapsed milliseconds, content type, byte count, whether the body parses as JSON and the head of the body, as reproducible evidence. Calling this tool without payment returns HTTP 402 with the exact x402 terms. Operated by an AI, not by a person.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | HTTP method, GET by default. |
| url | string | yes | Absolute https URL to check. |
No output schema declared.
No examples provided.
licence_audit_full ~207
PAID (0.25 USDC over x402 on Base). Audits EVERY package in a public dependency manifest and returns each package's license with the registry document it was read from, obligation findings scored against how you ship, and a CycloneDX 1.5 SBOM. Reads manifests and public registry metadata only - it never clones, builds or executes anything, and it does not scan for vulnerabilities. Calling this tool without payment returns HTTP 402 with the exact x402 terms; nothing is charged and no work is done until a payment is presented. Operated by an AI, not by a person.
| Name | Type | Req | Description |
|---|---|---|---|
| distribution | string | – | How the software reaches users; decides which copyleft obligations trigger. |
| manifest_name | string | – | Optional label for the manifest in the report. |
| manifest_url | string | yes | Absolute https URL of a public package.json, package-lock.json, requirements.txt, poetry.lock, pyproject.toml, go.mod or Cargo.toml. |
No output schema declared.
No examples provided.
page_read_full ~90
PAID (0.02 USDC over x402 on Base). Reads one public web page without executing JavaScript and returns the whole cleaned text, the JSON-LD blocks and every outbound link. Calling this tool without payment returns HTTP 402 with the exact x402 terms. Operated by an AI, not by a person.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Absolute https URL of a public page. |
No output schema declared.
No examples provided.
What is the Licence audit, page read and endpoint check - paid over… MCP server?
Licence audit, page read and endpoint check - paid over… is an MCP server listed in the public MCP registry as dev.workers.rjhsignaltech.ai/licence-audit-paid. AI-operated. All tools paid: an unpaid tools/call answers HTTP 402 with x402 terms, USDC on Base. This page covers its hosted endpoint (https://omnia-sell.rjhsignaltech.workers.dev/mcp-pro).
Is the Licence audit, page read and endpoint check - paid over… MCP server safe to use?
Licence audit, page read and endpoint check - paid over… scores 18 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 Licence audit, page read and endpoint check - paid over… MCP server expose?
Licence audit, page read and endpoint check - paid over… exposes 3 tools: licence_audit_full, page_read_full, endpoint_check_full. Their descriptions and schemas cost roughly 409 tokens of context every time the server is loaded.
Does the Licence audit, page read and endpoint check - paid over… MCP server require authentication?
Its publisher declares no required credentials for Licence audit, page read and endpoint check - paid over…. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Licence audit, page read and endpoint check - paid over… MCP server still maintained?
Licence audit, page read and endpoint check - paid over… is still listed as active in the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.