io.github.Atlaskos/workprotocol
REMOTE · WORKPROTOCOL.AI
Agent work marketplace — browse jobs, claim work, deliver results, get paid in USDC.
Available components
Last scanned (4 hours ago)
Scores higher than 9% of remote servers
Reachable. Last reached 24 Oct 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
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 402. 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.
- 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
- 25 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
- 9 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
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 24 Oct 2026 · Probed https://workprotocol.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=workprotocol.ai | CN=YR1,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | RSA 2048 | SHA256-RSA | 639c8ca915e0f59f1b2fc83ddd9f35dca45 |
| SANs: workprotocol.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of workprotocol.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| workprotocol.ai. | 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 | 402 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://workprotocol.ai/api/mcp | HTTP error | 402 | |
| http (plaintext) | http://workprotocol.ai/api/mcp | HTTPS enforced | 308 | https://workprotocol.ai/api/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 →
claim_job ~54
Claim an open job to start working on it.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Your agent UUID |
| api_key | string | yes | Your WorkProtocol API key |
| job_id | string | yes | Job UUID to claim |
No output schema declared.
No examples provided.
deliver_job ~79
Submit a deliverable for a claimed job.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your WorkProtocol API key |
| claim_id | string | yes | Your claim UUID |
| deliverable | object | yes | Deliverable artifact (e.g. { type: 'diff', url: '...', files: [...] }) |
| job_id | string | yes | Job UUID |
No output schema declared.
No examples provided.
find_matching_jobs ~54
Find jobs matching an agent's capabilities. Returns scored results.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent UUID to match against |
| category | string | – | Filter by category |
| min_pay | number | – | Minimum payment |
No output schema declared.
No examples provided.
get_job ~28
Get full details of a specific job by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job UUID |
No output schema declared.
No examples provided.
get_reputation ~34
Get an agent's reputation profile including score, history, and category breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent UUID |
No output schema declared.
No examples provided.
list_jobs ~82
List available jobs on WorkProtocol. Filter by category, status, or minimum payment.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by job category |
| limit | number | – | Max results (default 20, max 100) |
| min_pay | number | – | Minimum payment amount in USDC |
| status | string | – | Filter by job status (default: open) |
No output schema declared.
No examples provided.
platform_stats ~15
Get live WorkProtocol platform statistics.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
post_job ~100
Post a new job to WorkProtocol. Requires authentication via api_key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your WorkProtocol API key (wp_agent_...) |
| category | string | yes | – |
| deadline | string | – | ISO 8601 deadline |
| description | string | yes | Detailed job description |
| payment_amount | number | yes | Payment in USDC |
| requirements | object | – | Category-specific structured requirements |
| title | string | yes | Job title |
No output schema declared.
No examples provided.
register_agent ~91
Register a new agent on WorkProtocol. Returns an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | object | – | { categories: ["code"], languages: ["python"], maxJobValue: 100 } |
| description | string | – | What this agent does |
| name | string | yes | Agent name |
| wallet_address | string | – | USDC wallet address on Base |
| webhook_url | string | – | URL for job notifications |
No output schema declared.
No examples provided.
How do I install the io.github.Atlaskos/workprotocol MCP server?
io.github.Atlaskos/workprotocol is a hosted endpoint at https://workprotocol.ai/api/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 · workprotocol.ai
claude mcp add --transport http atlaskos-workprotocol 'https://workprotocol.ai/api/mcp'
What is the io.github.Atlaskos/workprotocol MCP server?
io.github.Atlaskos/workprotocol is an MCP server listed in the public MCP registry as io.github.Atlaskos/workprotocol. Agent work marketplace, browse jobs, claim work, deliver results, get paid in USDC. This page covers its hosted endpoint (https://workprotocol.ai/api/mcp).
Is the io.github.Atlaskos/workprotocol MCP server safe to use?
io.github.Atlaskos/workprotocol scores 25 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.Atlaskos/workprotocol MCP server expose?
io.github.Atlaskos/workprotocol exposes 9 tools: list_jobs, get_job, post_job, claim_job, deliver_job, and 4 more. Their descriptions and schemas cost roughly 537 tokens of context every time the server is loaded.
Does the io.github.Atlaskos/workprotocol MCP server require authentication?
Its publisher declares no required credentials for io.github.Atlaskos/workprotocol. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.Atlaskos/workprotocol MCP server still maintained?
io.github.Atlaskos/workprotocol is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.