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.

@エール | Aile Jobs

REMOTE · API.AILE-AI.JP

日本の掲載中・公開正社員求人の検索、求人詳細、職種別年収相場を提供する読み取り専用MCPサーバー

Available components

+1 this week 87 Trust /100

Last scanned (19 minutes ago)

Scores higher than 94% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

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 Security74
Transport & Reachability100
Schema Quality & AI Usability88
  • 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
  • Tool/resource definitions use about 445 tokens (~111/item across 4 items; 3 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
  • Supports UI / widget rendering.Pass
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.

  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

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 5 Nov 2026 · Probed https://api.aile-ai.jp/api/public/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.aile-ai.jp CN=YE2,O=Let's Encrypt,C=US 7 Sept 2026 6 Dec 2026 ECDSA 256 ECDSA-SHA384 524d0a9c13010b1376b2a96df3f7cc7e452
SANs: api.aile-ai.jp
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.aile-ai.jp. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
jp. present 33631 8 Verified
aile-ai.jp. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.aile-ai.jp/api/public/mcp Verified 200
http (plaintext) http://api.aile-ai.jp/api/public/mcp HTTPS enforced 308 https://api.aile-ai.jp/api/public/mcp
MCP tools · 3 exposed · ~415 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
job_detail ~89

公開求人キー(job_search の結果 URL 末尾のキー、または https://aile-ai.jp/jobs/<key> のキー)から求人詳細(求人説明・必要資格・選考フロー・勤務地・年収)を返す(読み取り専用)。

NameTypeReqDescription
public_keystringyes公開求人キー(4〜8 桁の英数字)

No output schema declared.

No examples provided.

job_search ~227

掲載中の公開求人を検索する(読み取り専用)。正準職種・都道府県・希望年収下限(円)・リモート可否で絞り込み、求人タイトル・会社名・正準職種・給与レンジ・勤務地・公開求人キー・公開 URL のリストを返す。返却された職種は salary_market にそのまま指定できる。

NameTypeReqDescription
limitinteger–返却件数の上限(1〜20、既定 10)
occupationstring–求人の正準職種名(任意、完全一致)
prefecturestring–勤務地の都道府県標準表記(任意、完全一致。例: 東京都)
remoteboolean–リモート可の求人に限定するか(任意、既定 false)
salary_mininteger–希望年収下限(円、任意。例: 4000000)

No output schema declared.

No examples provided.

salary_market ~99

職種 × 都道府県の年収相場(掲載中求人の求人数・提示年収の下限 / 中央値 / 上限、万円)を返す(読み取り専用)。

NameTypeReqDescription
occupationstringyes求人の正準職種名(完全一致)
prefecturestring–勤務地の都道府県名(任意。例: 大阪府)

No output schema declared.

No examples provided.

Install

How do I install the @エール | Aile Jobs MCP server?

@エール | Aile Jobs is a hosted endpoint at https://api.aile-ai.jp/api/public/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 · api.aile-ai.jp

# add to Claude Code
claude mcp add --transport http jp-aile-ai-aile-jobs 'https://api.aile-ai.jp/api/public/mcp'
Common questions

What is the @エール | Aile Jobs MCP server?

@エール | Aile Jobs is an MCP server listed in the public MCP registry as jp.aile-ai/aile-jobs. 日本の掲載中・公開正社員求人の検索、求人詳細、職種別年収相場を提供する読み取り専用MCPサーバー. This page covers its hosted endpoint (https://api.aile-ai.jp/api/public/mcp).

Is the @エール | Aile Jobs MCP server safe to use?

@エール | Aile Jobs scores 87 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 @エール | Aile Jobs MCP server expose?

@エール | Aile Jobs exposes 3 tools: job_search, job_detail, salary_market. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.

Does the @エール | Aile Jobs MCP server require authentication?

No. We connected to @エール | Aile Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the @エール | Aile Jobs MCP server still maintained?

@エール | Aile Jobs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.