Skip to content
External endpointresponds

AI Dev Jobs

Specialized job board for AI/ML engineers. Search curated roles.

Endpoint URL
https://aidevboard.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:58 AM UTC
Check
MCP initialize · 8s limit
Latency
114 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.aidevboard/jobs

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
aidevjobs
Version
1.0.0
Capability keys
tools
Tool names
search_jobs, get_job, list_companies, get_company, get_stats, match_jobs, get_salary_data, get_similar_jobs, get_trending_companies, list_tags, analyze_application_readiness, compile_job_specific_resume, approve_compiled_application, apply_to_job, record_my_application_outcome, list_my_interview_outcomes, respond_to_interview_outcome, list_products, quote_product, start_checkout
Instructions excerpt

Specialized job board for AI/ML engineers. Search and matching are free. Candidates may use analyze_application_readiness without identity for a transient gap analysis, or call compile_job_specific_resume without identity for a non-persisted $0 preview based only on candidate-verified evidence. A verified candidate key is required to save an immutable draft. After a saved compilation, the agent must stop, display the complete artifact verbatim, and ask the candidate_review approval question. Saved drafts are non-submitting; only after the email-verified human candidate explicitly approves that exact artifact and job may the agent call approve_compiled_application, then apply_to_job with the short-lived single-use authorization. Candidates may use record_my_application_outcome to create a $0 self-reported screening-progression receipt; it is not employer verification or an acceptance-rate claim. Employer-reported interviews require independent candidate confirmation through list_my_inte

Reported Aug 17, 2026, 04:58 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 383ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 199ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 152ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 114ms