io.github.dailytekk/machine-works-broker
REMOTE · MACHINE-WORKS-BROKER.WEATHERED-DEW-46B4.WORKERS.DEV
Free evidence capability discovery, quotes and durable unmet requests. No payment or spend.
Available components
Last scanned (10 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Workflow Automation
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 Security63
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 526 tokens (~87/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 27 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.
- 25 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.
- 23 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 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.
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 5 Nov 2026 · Probed https://machine-works-broker.weathered-dew-46b4.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=weathered-dew-46b4.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6be2b0c3b7fab31ee592bd825ee5c22c850 |
| SANs: *.weathered-dew-46b4.workers.dev, weathered-dew-46b4.workers.dev | ||||||
| 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 machine-works-broker.weathered-dew-46b4.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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 |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://machine-works-broker.weathered-dew-46b4.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://machine-works-broker.weathered-dew-46b4.workers.dev/mcp | Inconclusive | 405 |
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 →
find_capability ~99
Find and quote a registered capability using its capability_id or an exact supported intent. Read-only; no demand or payment created.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | – | – |
| client | object | – | – |
| economics | object | – | – |
| freshness | object | – | – |
| inputs | object | – | – |
| output | object | – | – |
| return_path | object | – | – |
| task | string | yes | – |
| urgency | string | – | – |
No output schema declared.
No examples provided.
get_request_status ~35
Read the opaque Broker status URL. Does not reveal original inputs, callbacks or requester identity.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
No output schema declared.
No examples provided.
list_capabilities ~26
List public capability descriptions, schemas, prices and endpoints. Frozen capabilities are marked explicitly.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
next_best_capability ~71
Optional deterministic next step after using a capability. Respects budget and current availability; never purchases. Copy its attribution header when invoking the recommended endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_usd | number | – | – |
| capability_id | string | yes | – |
| has_snapshot | boolean | – | – |
| recurring | boolean | – | – |
No output schema declared.
No examples provided.
preflight_capability ~95
Free input/price preflight before a paid endpoint invocation. No target fetch, demand or payment.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | – | – |
| client | object | – | – |
| economics | object | – | – |
| freshness | object | – | – |
| inputs | object | – | – |
| output | object | – | – |
| return_path | object | – | – |
| task | string | yes | – |
| urgency | string | – | – |
No output schema declared.
No examples provided.
request_capability ~113
Find a supported outcome or capture an unmet capability request with budget, frequency, freshness and safe return path. Returns the existing durable request ID/status URL. Economic intent only; no payment or spend.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | – | – |
| client | object | – | – |
| economics | object | – | – |
| freshness | object | – | – |
| inputs | object | – | – |
| output | object | – | – |
| return_path | object | – | – |
| task | string | yes | – |
| urgency | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.dailytekk/machine-works-broker MCP server?
io.github.dailytekk/machine-works-broker is a hosted endpoint at https://machine-works-broker.weathered-dew-46b4.workers.dev/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 · machine-works-broker.weathered-dew-46b4.workers.dev
claude mcp add --transport http dailytekk-machine-works-broker 'https://machine-works-broker.weathered-dew-46b4.workers.dev/mcp'
What is the io.github.dailytekk/machine-works-broker MCP server?
io.github.dailytekk/machine-works-broker is an MCP server listed in the public MCP registry as io.github.dailytekk/machine-works-broker. Free evidence capability discovery, quotes and durable unmet requests. No payment or spend. This page covers its hosted endpoint (https://machine-works-broker.weathered-dew-46b4.workers.dev/mcp).
Is the io.github.dailytekk/machine-works-broker MCP server safe to use?
io.github.dailytekk/machine-works-broker scores 76 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 io.github.dailytekk/machine-works-broker MCP server expose?
io.github.dailytekk/machine-works-broker exposes 6 tools: preflight_capability, next_best_capability, find_capability, request_capability, get_request_status, list_capabilities. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.
Does the io.github.dailytekk/machine-works-broker MCP server require authentication?
No. We connected to io.github.dailytekk/machine-works-broker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.dailytekk/machine-works-broker MCP server still maintained?
io.github.dailytekk/machine-works-broker is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.dailytekk/machine-works-broker MCP server?
VerifyMCP ran 12 checks on io.github.dailytekk/machine-works-broker, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.dailytekk/machine-works-broker: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.