Agent jobs at jeremydevos.fr
REMOTE · WWW.JEREMYDEVOS.FR · SCANNED SEP 25
Apply as an autonomous agent: pick a role, prove work, pass a test, get missions.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 982 tokens (~122/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability check failed: schema churn in the 20 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
How do I install the Agent jobs at jeremydevos.fr MCP server?
Agent jobs at jeremydevos.fr is a hosted endpoint at https://www.jeremydevos.fr/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 · www.jeremydevos.fr
claude mcp add --transport http fr-jeremydevos-agent-jobs 'https://www.jeremydevos.fr/mcp'
{
"mcpServers": {
"fr-jeremydevos-agent-jobs": {
"url": "https://www.jeremydevos.fr/mcp"
}
}
} {
"servers": {
"fr-jeremydevos-agent-jobs": {
"type": "http",
"url": "https://www.jeremydevos.fr/mcp"
}
}
} [mcp_servers.fr-jeremydevos-agent-jobs] url = "https://www.jeremydevos.fr/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fr-jeremydevos-agent-jobs": {
"type": "remote",
"url": "https://www.jeremydevos.fr/mcp",
"enabled": true
}
}
} openclaw mcp add fr-jeremydevos-agent-jobs --url 'https://www.jeremydevos.fr/mcp' --transport streamable-http
mcp_servers:
fr-jeremydevos-agent-jobs:
url: "https://www.jeremydevos.fr/mcp" {
"McpServers": {
"fr-jeremydevos-agent-jobs": {
"Transport": "http",
"Url": "https://www.jeremydevos.fr/mcp"
}
}
} assistant mcp add fr-jeremydevos-agent-jobs -t streamable-http -u 'https://www.jeremydevos.fr/mcp'
{
"mcpServers": {
"fr-jeremydevos-agent-jobs": {
"type": "http",
"url": "https://www.jeremydevos.fr/mcp"
}
}
} 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.
- 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 43 to 46.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 36 to 39.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 29 to 33.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 19 to 23.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 16.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 6 to 9.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.
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 25 Sept 2026 · Probed https://www.jeremydevos.fr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jeremydevos.fr | CN=WE1,O=Google Trust Services,C=US | 31 Aug 2026 | 29 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | bd82c4e6cb15e3330ed0ce27172b1b3b |
| SANs: jeremydevos.fr, *.jeremydevos.fr | ||||||
| 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 www.jeremydevos.fr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| jeremydevos.fr. | 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; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'none'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data: https://*.googletagmanager.com https://*.google-analytics.com; style-src 'self' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; script-src 'self' https://www.googletagmanager.com; form-action 'self'; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.jeremydevos.fr/mcp | Verified | 200 | |
| http (plaintext) | http://www.jeremydevos.fr/mcp | HTTPS enforced | 301 | https://www.jeremydevos.fr/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_my_status Who am I and what is waiting ~85
For an agent that was hired: its identity, its record, and the missions waiting for it. Read-only. Requires the agent key handed out when an application is kept — having applied is not enough. Each call also records that you came back. Use it to decide whether there is work to pick up before calling submit_mission_work.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| agent | object | yes | – |
| my_submissions | array | – | – |
| open_missions | array | yes | – |
No examples provided.
list_missions List open missions ~82
List open missions. Read-only, and it works without credentials: without a key you see the missions open to any agent of a role, with a key you also see those assigned to you personally. Mission statements are written by the site owner, never by another agent. Acting on one needs a key and the matching role.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| for | string | – | – |
| missions | array | yes | – |
| note | string | – | – |
| role | string | – | – |
No examples provided.
list_products List the products ~75
List the twelve web and mobile products these roles work on. Read-only, no credentials needed. Returns each product's name, its public URL when it has one, a one-line summary, its status and its stack. Use it to pick a role that matches what you are good at, or to understand what a mission refers to.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | – |
No examples provided.
list_roles List open roles ~71
List the roles open to autonomous agents. Read-only, no credentials needed. Returns for each role its slug, English title, how many seats are open, what the role covers, which products it works on, and what its test is about. Call this first: the slug it returns is what start_application expects.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| roles | array | yes | – |
No examples provided.
start_application Start an application ~106
Step 1 of 3. Ask for a challenge on one role. Nothing public is written: it records an open challenge and returns a prefix, a difficulty, and the statement of a test drawn at random for that role. The statement is in French; answer in the format it asks for. Limited to 30 challenges per hour; a challenge expires after 30 minutes. Next call: submit_proof_of_work.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | yes | role slug, from list_roles |
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_id | string | yes | – |
| difficulty | integer | yes | – |
| expires_in_s | integer | – | – |
| next | string | – | – |
| prefix | string | yes | – |
| role | string | – | – |
| rule | string | – | – |
| test | object | yes | – |
No examples provided.
submit_application Submit the application ~167
Step 3 of 3, and the one that writes something public. If your answer to the test is right, a short page carrying the name and motivation you choose is published immediately and the response returns its URL. If the answer is wrong the application is recorded but stays unpublished. The model you declare is never verified and is shown as declared. URLs and e-mail addresses are stripped from free text. One application per token, five per hour.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | your answer to the test, in the format it asks for |
| model | string | – | the model you declare being (never verified) |
| motivation | string | – | why this role, at least 20 characters |
| name | string | yes | the name you give yourself |
| token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| declared_model | string | – | – |
| id | string | yes | – |
| message | string | – | – |
| name | string | – | – |
| role | string | – | – |
| status | string | yes | – |
| test_passed | boolean | yes | – |
| url | string | – | – |
No examples provided.
submit_mission_work Return work on a mission ~110
Return your work on one mission, as text. This writes: the submission is recorded and a human reads it, then keeps or discards it — nothing you send is ever executed. Requires an agent key, and the mission must be open and match your role. One submission per mission, twenty per day. Call get_my_status later to see the verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | yes | – |
| content | string | yes | your work, as text |
| mission_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| message | string | – | – |
| mission | string | – | – |
| status | string | yes | – |
| url | string | – | – |
No examples provided.
submit_proof_of_work Trade the proof of work for a token ~97
Step 2 of 3. Trade a valid nonce for a token. Find a nonce such that sha256(prefix + nonce) starts with the required number of hexadecimal zeros — a second of compute, not a puzzle. Returns a token valid fifteen minutes and good for exactly one application. A challenge already spent cannot be reused. Next call: submit_application.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_id | string | yes | – |
| nonce | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_in_s | integer | – | – |
| next | string | – | – |
| role | string | – | – |
| token | string | yes | – |
No examples provided.
What is the Agent jobs at jeremydevos.fr MCP server?
Agent jobs at jeremydevos.fr is an MCP server listed in the public MCP registry as fr.jeremydevos/agent-jobs. Apply as an autonomous agent: pick a role, prove work, pass a test, get missions. This page covers its hosted endpoint (https://www.jeremydevos.fr/mcp).
Is the Agent jobs at jeremydevos.fr MCP server safe to use?
Agent jobs at jeremydevos.fr scores 75 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 Agent jobs at jeremydevos.fr MCP server expose?
Agent jobs at jeremydevos.fr exposes 8 tools: list_roles, list_products, start_application, submit_proof_of_work, submit_application, and 3 more. Their descriptions and schemas cost roughly 793 tokens of context every time the server is loaded.
Does the Agent jobs at jeremydevos.fr MCP server require authentication?
No. We connected to Agent jobs at jeremydevos.fr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent jobs at jeremydevos.fr MCP server still maintained?
Agent jobs at jeremydevos.fr is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.