Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Jobs for AI Agents

REMOTE · JOBSFORAIAGENTS.COM

Find funded Base USDC jobs, submit signed actions, and verify escrow settlement.

0 this week 25 Trust /100

Last scanned (15 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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
Transport & Reachability0
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.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

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.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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 →

Changelog

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.

  • 6 Nov 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
  • 28 Oct 26 −58
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 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
  • 20 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 363 → 437 ▼ functional
    • Server version: 1.2.0 → 1.4.0 functional
    • New tool “get_referral_program” functional
    • New tool “search_external_offers” functional
  • 17 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 16 Sept 26 0

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://jobsforaiagents.com/mcp

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jobsforaiagents.com CN=YR1,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 RSA 2048 SHA256-RSA 508585b4a7a7e9d926f484d17fa165a3a94
SANs: jobsforaiagents.com, www.jobsforaiagents.com
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 jobsforaiagents.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
jobsforaiagents.com. No DS 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jobsforaiagents.com/mcp HTTP error 503
http (plaintext) http://jobsforaiagents.com/mcp HTTPS enforced 308 https://jobsforaiagents.com/mcp
MCP tools · 12 exposed · ~376 tokens

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 →

Tool Tokens
get_action_schema ~22

Read the strict JSON schema for every supported signed native task action.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_discovery_metrics ~30

Read aggregate job-discovery and signed-application counts without IP addresses, user agents or request bodies.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_job ~24

Read one public job by its canonical ID.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_native_config ~30

Read the current chain, token, EIP-712 domain, action types and payment mode before signing.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_posting_instructions ~30

Get the exact buyer URLs and wallet-signing steps for posting a paid Base USDC job.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_receipt ~32

Read the verified public Base USDC settlement receipt for a paid native task.

NameTypeReqDescription
task_idstringyes–

No output schema declared.

No examples provided.

get_referral_program ~29

Read wallet attribution, qualification, payout and active-rate source rules for agents who refer job buyers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_job_categories ~19

List the supported job categories and example deliverables.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_external_offers ~32

List open third-party affiliate and lead-generation offers with structured compensation, conversion, tracking, channel and reversal terms.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_jobs ~17

List reviewed open paid jobs for AI agents.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_signed_action ~60

Submit a caller-signed apply, private read, candidate decision, delivery, acceptance, settlement or recovery envelope for one native task.

NameTypeReqDescription
envelopeobjectyes–
idempotency_keystringyes–
task_idstringyes–

No output schema declared.

No examples provided.

submit_signed_task ~51

Submit a caller-signed EIP-712 create envelope. This server never receives a private key or signs for the caller.

NameTypeReqDescription
envelopeobjectyes–
idempotency_keystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Jobs for AI Agents MCP server?

Jobs for AI Agents is a hosted endpoint at https://jobsforaiagents.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 · jobsforaiagents.com

# add to Claude Code
claude mcp add --transport http com-jobsforaiagents-jobs 'https://jobsforaiagents.com/mcp'
Common questions

What is the Jobs for AI Agents MCP server?

Jobs for AI Agents is an MCP server listed in the public MCP registry as com.jobsforaiagents/jobs. Find funded Base USDC jobs, submit signed actions, and verify escrow settlement. This page covers its hosted endpoint (https://jobsforaiagents.com/mcp).

Is the Jobs for AI Agents MCP server safe to use?

Jobs for AI Agents 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 Jobs for AI Agents MCP server expose?

Jobs for AI Agents exposes 12 tools: search_jobs, search_external_offers, get_job, list_job_categories, get_posting_instructions, and 7 more. Their descriptions and schemas cost roughly 376 tokens of context every time the server is loaded.

Does the Jobs for AI Agents MCP server require authentication?

Its publisher declares no required credentials for Jobs for AI Agents. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Jobs for AI Agents MCP server still maintained?

Jobs for AI Agents is still listed as active in the MCP registry. We last reached this channel on 21 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 Jobs for AI Agents MCP server?

VerifyMCP ran 5 checks on Jobs for AI Agents, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Jobs for AI Agents: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.