WORKMINE
REMOTE · WORKMINE-MCP.ONRENDER.COM
x402 pay-per-call APIs over MCP, settled in USDC on Base for autonomous agents and developers.
Available components
Last scanned (2 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 19 Oct 2026.
Category Finance and Payments
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 429, 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 503. 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.
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.
- 13 Oct 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.33 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 33. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 10 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 17 to 27. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Oct 26 64
First indexed and scored.
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 19 Oct 2026 · Probed https://workmine-mcp.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| 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 workmine-mcp.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | 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 | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://workmine-mcp.onrender.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://workmine-mcp.onrender.com/mcp | Inconclusive | 429 |
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_workmine_tool ~104
Find a relevant WORKMINE paid API from a natural-language task without purchasing it. Returns the selected tool, price and URL; actual execution requires a separate x402 USDC payment. Use workmine_catalog instead to browse all tools, or workmine_payment_instructions after selecting a tool.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | Natural-language task the buyer needs completed, for example: 'repair malformed JSON', 'extract PDF text', or 'launch an x402 seller API'. |
Structured output declared, but exposes no named fields.
No examples provided.
workmine_catalog ~69
Browse the complete WORKMINE catalog for free: paid API names, exact USDC-denominated prices, HTTP methods and URLs. Use this when comparing available tools; use find_workmine_tool when you already have a natural-language task. This catalog call itself does not execute or purchase a paid API.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
workmine_launch_kit_offer ~95
Quote the premium WORKMINE x402 Launch Kit without charging anything. Use this when an API developer or autonomous agent wants to monetize an HTTP service with x402 on Base. Returns the exact $19 USDC product URL, required request fields, deliverables and payment flow. This MCP call is free and read-only; payment occurs only if the buyer later calls the returned HTTP endpoint and signs its x402 challenge.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
workmine_paid_ping ~70
Execute WORKMINE's native MCP x402 payment test for $0.001 USDC on Base. First call returns PaymentRequired; an x402-aware MCP client can retry with payment metadata and settle directly to WORKMINE.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | – | Optional caller nonce echoed after successful payment. |
No output schema declared.
No examples provided.
workmine_paid_ping_offer ~67
Free quote for WORKMINE Paid Ping, the minimum-cost $0.001 USDC x402 purchase. Use this when an autonomous agent wants to verify that it can complete an x402 payment before buying a larger tool. This MCP call is free and does not charge anything.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
workmine_payment_instructions ~108
Return x402 payment and endpoint instructions for a selected WORKMINE tool without executing the paid call. Pass a tool slug returned by find_workmine_tool or workmine_catalog. The buyer then calls the endpoint, reads its HTTP 402 challenge, signs the exact Base USDC payment and retries.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | Exact WORKMINE product slug returned by find_workmine_tool or workmine_catalog, for example x402_launch_kit, repair_json, or pdf_extract. |
Structured output declared, but exposes no named fields.
No examples provided.
workmine_readiness_audit_offer ~109
Quote the WORKMINE x402 Readiness Audit without charging anything. Use this first for sellers who already have an x402 manifest and want a low-cost preflight check before marketplace registration. The audit costs $0.05 USDC on Base and checks identity, HTTPS resources, x402 v2 metadata, Base/USDC, payTo format, machine-readable discovery and origin consistency. This MCP call is free; payment occurs only when the buyer calls the returned HTTP endpoint.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
workmine_start_here ~53
Free WORKMINE entry point for new buyers. Use this when the buyer wants to try WORKMINE or is unsure what to purchase. It recommends the lowest-friction relevant paid action and never charges by itself.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the WORKMINE MCP server?
WORKMINE is a hosted endpoint at https://workmine-mcp.onrender.com/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 · workmine-mcp.onrender.com
claude mcp add --transport http tamerlan0606-workmine 'https://workmine-mcp.onrender.com/mcp'
What is the WORKMINE MCP server?
WORKMINE is an MCP server listed in the public MCP registry as io.github.Tamerlan0606/workmine. x402 pay-per-call APIs over MCP, settled in USDC on Base for autonomous agents and developers. This page covers its hosted endpoint (https://workmine-mcp.onrender.com/mcp).
Is the WORKMINE MCP server safe to use?
WORKMINE 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 WORKMINE MCP server expose?
WORKMINE exposes 8 tools: workmine_catalog, find_workmine_tool, workmine_start_here, workmine_paid_ping, workmine_paid_ping_offer, and 3 more. Their descriptions and schemas cost roughly 675 tokens of context every time the server is loaded.
Does the WORKMINE MCP server require authentication?
Its publisher declares no required credentials for WORKMINE. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the WORKMINE MCP server still maintained?
WORKMINE is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.