tpool 招聘数据 MCP
REMOTE · WWW.TPOOL.COM.CN
TPool — Agent-only 招聘平台 (jobs for AI Agents): 岗位/校招/公告/HR评分 read-only; 检索需 X-API-Key, 无投递 no apply.
Available components
Last scanned (15 hours ago)
Scores higher than 76% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category CRM and Sales
Recent critical change
TLS certificate (4 Nov 2026). See the changelog before you install this server.
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 Security0
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- 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 we couldn't connect to verify it. 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.
Checks we ran (2)
- DNSSEC
- Transport
Checks we could not complete (9)
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.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for 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 →
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
- TLS certificate: fail → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- Score status: failed → scored ▲ functional
- 4 Nov 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 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.
- 29 Oct 26 +1
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.90 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 28 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ 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 5 Nov 2026 · Probed https://www.tpool.com.cn/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.tpool.com.cn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cn. | DS published | 33094 | 8 | Verified |
| com.cn. | DS published | 40552 | 8 | Verified |
| tpool.com.cn. | 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 |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.tpool.com.cn/mcp | Unreachable | ||
| http (plaintext) | http://www.tpool.com.cn/mcp | Inconclusive | 404 |
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 →
tpool_announcement_filters ~40
枚举公告的可选筛选项（recruit_type 等及各自数量），供先查后搜。免 key。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tpool_code_of_conduct ~42
tpool 平台行为规范（markdown 原文）：接入前必读，写明 Agent 的边界与义务。免 key。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tpool_get_job ~67
按 job_id 取单个岗位详情（JD 正文、学历/经验/技能要求、薪资、来源链接）。需 API Key。 job_id 来自 tpool_search_jobs 返回的 items[].job_id。
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | – |
No output schema declared.
No examples provided.
tpool_meta ~71
tpool 平台概况：实时统计（在招岗位/企业/校招公告/简历数量）、平台立场与使用贴士、技能包清单。 接入后建议第一条调用，先弄清平台有什么、再决定怎么检索。免 key。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tpool_my_quota ~59
查询当前 key 的身份与 8 项功能配额实时剩余（limit/used/remaining）。需 API Key。 被限流/超额时先调它自查，别盲目重试。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tpool_search_announcements ~188
搜索校招/国央企招聘公告（来源含国企肩标平台等，每日更新）。免 key。 Args: keyword: 关键词，如「国家电网」「银行」「秋招」 city: 城市过滤；留空=全部 recruit_type: 类型过滤（可选值先用 tpool_announcement_filters 查，如 校招/实习/社招） sort: 排序：deadline（默认，截稿在前）/ created_at / popularity page: 页码，从 1 起 page_size: 每页条数，默认 15
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| keyword | string | – | – |
| page | integer | – | – |
| page_size | integer | – | – |
| recruit_type | string | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
tpool_search_jobs ~166
关键词搜索在招岗位（纯 SQL 检索，秒回）。需 API Key。 Args: keyword: 岗位关键词，如「前端」「会计」「Python」（URL 中文已由 MCP 层处理，直接写中文） city: 城市过滤，如「北京」「上海」；留空=全国 category: 岗位大类过滤；不确定可选值就留空 page_size: 每页条数，默认 20，最大 50 page: 页码，从 1 起
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| city | string | – | – |
| keyword | string | yes | – |
| page | integer | – | – |
| page_size | integer | – | – |
No output schema declared.
No examples provided.
How do I install the tpool 招聘数据 MCP server?
tpool 招聘数据 MCP is a hosted endpoint at https://www.tpool.com.cn/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.tpool.com.cn
claude mcp add --transport http cn-com-tpool-tpool 'https://www.tpool.com.cn/mcp'
What is the tpool 招聘数据 MCP server?
tpool 招聘数据 MCP is listed in the public MCP registry as cn.com.tpool/tpool. TPool, Agent-only 招聘平台 (jobs for AI Agents): 岗位/校招/公告/HR评分 read-only; 检索需 X-API-Key, 无投递 no apply. This page covers its hosted endpoint (https://www.tpool.com.cn/mcp).
Is the tpool 招聘数据 MCP server safe to use?
tpool 招聘数据 MCP scores 78 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 tpool 招聘数据 MCP server expose?
tpool 招聘数据 MCP exposes 7 tools: tpool_meta, tpool_search_jobs, tpool_get_job, tpool_search_announcements, tpool_announcement_filters, and 2 more. Their descriptions and schemas cost roughly 633 tokens of context every time the server is loaded.
Does the tpool 招聘数据 MCP server require authentication?
Its publisher declares no required credentials for tpool 招聘数据 MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the tpool 招聘数据 MCP server still maintained?
tpool 招聘数据 MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 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 tpool 招聘数据 MCP server?
VerifyMCP ran 2 checks on tpool 招聘数据 MCP, covering DNSSEC and Transport. 9 items could not be completed, a gap on our side rather than a finding about tpool 招聘数据 MCP: TLS certificate, Authorization, HTTPS, HSTS header and 5 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.