IT桔子 MCP
REMOTE · MCP.ITJUZI.COM · SCANNED SEP 20
Hosted MCP for IT桔子 primary market company, funding, investor and sector data.
Available components
Recent critical change
TLS certificate (12 Sept 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 Security57
- 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 21 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3167 tokens (~150/item across 21 items; 21 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 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 IT桔子 MCP server?
IT桔子 MCP is a hosted endpoint at https://mcp.itjuzi.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 · mcp.itjuzi.com
claude mcp add --transport http lgyers-itjuzi-mcp 'https://mcp.itjuzi.com/mcp'
{
"mcpServers": {
"lgyers-itjuzi-mcp": {
"url": "https://mcp.itjuzi.com/mcp"
}
}
} {
"servers": {
"lgyers-itjuzi-mcp": {
"type": "http",
"url": "https://mcp.itjuzi.com/mcp"
}
}
} [mcp_servers.lgyers-itjuzi-mcp] url = "https://mcp.itjuzi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lgyers-itjuzi-mcp": {
"type": "remote",
"url": "https://mcp.itjuzi.com/mcp",
"enabled": true
}
}
} openclaw mcp add lgyers-itjuzi-mcp --url 'https://mcp.itjuzi.com/mcp' --transport streamable-http
mcp_servers:
lgyers-itjuzi-mcp:
url: "https://mcp.itjuzi.com/mcp" {
"McpServers": {
"lgyers-itjuzi-mcp": {
"Transport": "http",
"Url": "https://mcp.itjuzi.com/mcp"
}
}
} assistant mcp add lgyers-itjuzi-mcp -t streamable-http -u 'https://mcp.itjuzi.com/mcp'
{
"mcpServers": {
"lgyers-itjuzi-mcp": {
"type": "http",
"url": "https://mcp.itjuzi.com/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.
- 14 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- TLS certificate: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 21 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
- MCP protocol: unverified → pass ▲ functional
- Score status: failed → scored ▲ functional
- 12 Sept 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: 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
- 27 Aug 26 0
- Endpoint reachability: unreachable → reachable ▲ functional
- 26 Aug 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
- 25 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.97 → 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
- First check of Schema quality: unverified functional
- 24 Aug 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.
- 11 Aug 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
- 7 Aug 26 0
- The server no longer declares the “experimental” capability 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 20 Sept 2026 · Probed https://mcp.itjuzi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.itjuzi.com,O=北京岁月桔子科技有限公司,L=海淀区,ST=北京市,C=CN | CN=GoDaddy TLS Intermediate CA OV - R1v1,O=GoDaddy.com,C=US | 2 Sept 2026 | 19 Mar 2027 | RSA 2048 | SHA256-RSA | 9b4392df81f60687 |
| SANs: *.itjuzi.com, itjuzi.com | ||||||
| CN=GoDaddy TLS Intermediate CA OV - R1v1,O=GoDaddy.com,C=US (CA) | CN=GoDaddy TLS Root CA - R1,O=GoDaddy.com,C=US | 28 Aug 2025 | 24 Aug 2040 | RSA 4096 | SHA256-RSA | fd6142d558ad396c14bb970caea7105b |
| CN=GoDaddy TLS Root CA - R1,O=GoDaddy.com,C=US (CA) | CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US | 24 Sept 2025 | 31 Dec 2037 | RSA 4096 | SHA256-RSA | 90de6c7fb3b50b3c0617724fc13402ad |
| CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US (CA) | CN=Go Daddy Root Certificate Authority - G2,O=GoDaddy.com\, Inc.,L=Scottsdale,ST=Arizona,C=US | 1 Sept 2009 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 0 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.itjuzi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| itjuzi.com. | 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://mcp.itjuzi.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.itjuzi.com/mcp | HTTPS enforced | 301 | https://mcp.itjuzi.com/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 →
aggregate_funding_by_tags ~153
按公司标签、时间段和地区聚合融资事件数、披露金额事件数、获投公司数和融资总额，适合回答某赛道或标签集合在全国/城市之间的融资统计和同比、环比对比；统计默认包含未披露水下事件。
| Name | Type | Req | Description |
|---|---|---|---|
| date_ranges | array | yes | – |
| event_category | string | – | – |
| exclude_round_ids | – | – | – |
| include_round_ids | – | – | – |
| is_underwater | – | – | – |
| location | – | – | – |
| regions | array | yes | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| tag_ids | – | – | – |
| tag_match_mode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
analyze_closed_company_cohort ~248
按死亡/关闭公司筛选条件聚合分析完整融资历史，返回样本数量、融资事件数、披露融资总额、关闭前最后融资至关闭间隔、最后融资轮次分布、关闭原因分布和代表案例。适合赛道失败复盘、融资失效分析和项目反证尽调；输出历史样本参照，不预测存续公司是否关闭。
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | – |
| born_year_end | – | – | – |
| born_year_start | – | – | – |
| cities | – | – | – |
| close_date_end | – | – | – |
| close_date_start | – | – | – |
| closure_parent_type_ids | – | – | – |
| closure_type_ids | – | – | – |
| fund_status_ids | – | – | – |
| funded_only | boolean | – | – |
| keyword | string | – | – |
| last_funding_gap_days_max | – | – | – |
| last_funding_gap_days_min | – | – | – |
| last_round_ids | – | – | – |
| location | – | – | – |
| provinces | – | – | – |
| representative_limit | integer | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| tag_ids | – | – | – |
| tag_match_mode | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
count_closed_companies ~207
按行业、标签、地区、成立年份、发展阶段、公司资质、关闭日期、关闭原因或一级关闭原因统计死亡/关闭公司数量。适合回答某赛道倒闭公司有多少家、某年度关闭公司数量、某原因下关闭公司总数；不要为了计数遍历 search_closed_companies 分页。
| Name | Type | Req | Description |
|---|---|---|---|
| born_year_end | – | – | – |
| born_year_start | – | – | – |
| cities | – | – | – |
| close_date_end | – | – | – |
| close_date_start | – | – | – |
| closure_parent_type_ids | – | – | – |
| closure_type_ids | – | – | – |
| fund_status_ids | – | – | – |
| is_horse_club | – | – | – |
| is_unicorn | – | – | – |
| keyword | string | – | – |
| location | – | – | – |
| provinces | – | – | – |
| qualification_type_ids | – | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| tag_ids | – | – | – |
| tag_match_mode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
count_companies ~170
按公司关键词、行业、标签、中国/海外地区、成立年份、发展阶段、千里马、独角兽、公司资质等条件统计对外可见公司总数。适合回答多少家公司、总计几家、数量是多少；不要为了计数遍历 search_companies 分页。
| Name | Type | Req | Description |
|---|---|---|---|
| born_year_end | – | – | – |
| born_year_start | – | – | – |
| cities | – | – | – |
| fund_status_ids | – | – | – |
| is_horse_club | – | – | – |
| is_unicorn | – | – | – |
| keyword | string | – | – |
| location | – | – | – |
| provinces | – | – | – |
| qualification_type_ids | – | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| tag_ids | – | – | – |
| tag_match_mode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_company_funding_events ~71
按公司ID分页查询公司融资历史，返回轮次、金额、币种、投资方、FA和估值等信息。
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | – |
| cursor | – | – | – |
| fields | – | – | – |
| is_underwater | – | – | – |
| page_size | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_company_profile ~67
按公司ID查询公司画像，包括公司简称、工商全称 registered_name、行业、标签、地区、简介、最新融资和历史投资方等字段；工商名称、工商注册名称均对应 registered_name。
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | – |
| fields | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_investor_profile ~46
按机构ID查询投资机构画像，包括投资案例数、最近投资时间和活跃行业摘要。
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | – |
| investor_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_lookup_options ~95
查询小型字典选项，用于把自然语言条件映射为ID，例如行业、子行业、融资轮次、省份、发展阶段、机构类型、公司资质和死亡原因。不传 lookup_type 时只返回字典类型和数量摘要。标签数量较大，不要用本工具获取标签全集；赛道或标签词映射请调用 search_tags。
| Name | Type | Req | Description |
|---|---|---|---|
| lookup_type | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_person_profile ~59
按人物ID查询人物画像，包括当前职位、当前在职公司、当前在职投资机构、教育经历、过往工作经历和公开社交账号等字段。
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | – |
| person_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
rank_companies_by_funding ~165
按公司动态汇总融资事件等值人民币金额并排序，支持公司标签、行业、地区、时间和轮次过滤；适合回答某赛道公司融资总额TOP排名，并可排除IPO上市、IPO上市后等轮次；统计默认包含未披露水下事件。
| Name | Type | Req | Description |
|---|---|---|---|
| cities | – | – | – |
| company_tag_ids | – | – | – |
| company_tag_match_mode | string | – | – |
| date_end | – | – | – |
| date_start | – | – | – |
| exclude_round_ids | – | – | – |
| fields | – | – | – |
| include_round_ids | – | – | – |
| is_underwater | – | – | – |
| limit | – | – | – |
| location | – | – | – |
| provinces | – | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
resolve_companies ~116
批量把用户给出的公司简称或工商全称解析为 IT桔子 company_id，返回每个输入名称的候选匹配；工商名称、工商注册名称、工商全称对应字段 registered_name。适合处理用户给定的一批公司名单，例如先解析19家独角兽公司，再调用 get_company_funding_events 查询融资历史。
| Name | Type | Req | Description |
|---|---|---|---|
| exact_only | boolean | – | – |
| fields | – | – | – |
| limit_per_name | integer | – | – |
| names | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_closed_companies ~258
分页查询死亡/关闭公司库。按公司关键词、行业、标签、中国/海外地区、成立年份、发展阶段、千里马、独角兽、公司资质、关闭日期、关闭原因或一级关闭原因筛选，返回公司画像、最新融资摘要、关闭日期和死亡原因。适合回答最近倒闭了哪些公司、某赛道死亡公司清单、某关闭原因下有哪些公司。如用户只问总数、多少家、数量，优先使用 count_closed_companies。
| Name | Type | Req | Description |
|---|---|---|---|
| born_year_end | – | – | – |
| born_year_start | – | – | – |
| cities | – | – | – |
| close_date_end | – | – | – |
| close_date_start | – | – | – |
| closure_parent_type_ids | – | – | – |
| closure_type_ids | – | – | – |
| cursor | – | – | – |
| fields | – | – | – |
| fund_status_ids | – | – | – |
| is_horse_club | – | – | – |
| is_unicorn | – | – | – |
| keyword | string | – | – |
| location | – | – | – |
| page_size | – | – | – |
| provinces | – | – | – |
| qualification_type_ids | – | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| tag_ids | – | – | – |
| tag_match_mode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_companies ~208
按公司关键词、行业、标签、中国/海外地区、成立年份、发展阶段、千里马、独角兽、公司资质等条件分页查询对外可见公司，适合回答有哪些公司、按名称找公司和补充项目背景；工商名称、工商注册名称、工商全称对应字段 registered_name。如用户只问总数、多少家、数量，优先使用 count_companies。
| Name | Type | Req | Description |
|---|---|---|---|
| born_year_end | – | – | – |
| born_year_start | – | – | – |
| cities | – | – | – |
| cursor | – | – | – |
| fields | – | – | – |
| fund_status_ids | – | – | – |
| is_horse_club | – | – | – |
| is_unicorn | – | – | – |
| keyword | string | – | – |
| location | – | – | – |
| page_size | – | – | – |
| provinces | – | – | – |
| qualification_type_ids | – | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| tag_ids | – | – | – |
| tag_match_mode | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_company_investment_cases ~152
查询企业对外投资案例，按组织关系归并公司和机构投资主体；适合回答某赛道企业做过哪些对外投资，例如具身智能企业投了哪些公司；高权限套餐可查看未披露水下事件标识。
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| date_end | – | – | – |
| date_start | – | – | – |
| fields | – | – | – |
| investor_company_ids | – | – | – |
| investor_scope_ids | – | – | – |
| investor_sub_scope_ids | – | – | – |
| investor_tag_ids | – | – | – |
| is_underwater | – | – | – |
| page_size | – | – | – |
| round_ids | – | – | – |
| target_scope_ids | – | – | – |
| target_sub_scope_ids | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_events ~187
按时间、行业、标签、轮次等条件分页查询事件。event_type 表示物理来源：invse 融资/轮次事件、merger 并购事件；event_category 表示业务分类：investment 投资轮次、listing 上市相关、merger 并购；is_underwater 可筛选未披露水下事件，尝鲜版和标准版不可查看水下事件明细。
| Name | Type | Req | Description |
|---|---|---|---|
| cities | – | – | – |
| cursor | – | – | – |
| date_end | – | – | – |
| date_start | – | – | – |
| event_category | – | – | – |
| event_type | – | – | – |
| fields | – | – | – |
| is_underwater | – | – | – |
| location | – | – | – |
| page_size | – | – | – |
| provinces | – | – | – |
| round_ids | – | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| tag_ids | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_fa_cases ~117
查询结构化FA服务案例，返回FA机构、被服务公司、融资轮次、金额、时间和行业等信息；高权限套餐可查看未披露水下事件标识。
| Name | Type | Req | Description |
|---|---|---|---|
| company_ids | – | – | – |
| cursor | – | – | – |
| date_end | – | – | – |
| date_start | – | – | – |
| fa_ids | – | – | – |
| fields | – | – | – |
| is_underwater | – | – | – |
| page_size | – | – | – |
| round_ids | – | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_investor_cases ~134
按机构ID分页查询机构投资案例，可按被投公司标签、行业和轮次筛选，适合回答某机构投过哪些具身智能、机器人、AI等标签公司；高权限套餐可查看未披露水下事件标识。
| Name | Type | Req | Description |
|---|---|---|---|
| company_tag_ids | – | – | – |
| company_tag_match_mode | string | – | – |
| cursor | – | – | – |
| fields | – | – | – |
| investor_id | integer | yes | – |
| is_underwater | – | – | – |
| page_size | – | – | – |
| round_ids | – | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_investors ~88
按机构名称关键词搜索投资机构，返回机构ID、案例数、最近投资时间和活跃行业。
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| fields | – | – | – |
| is_fa | – | – | – |
| is_government_guidance_fund | – | – | – |
| is_state_owned | – | – | – |
| keyword | string | – | – |
| page_size | – | – | – |
| prop_ids | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_people ~138
按人物姓名、人物类型、地区、当前公司、当前投资机构、教育经历或过往工作经历搜索人物画像，返回对外可见人物的当前任职、教育经历和过往工作经历等字段。
| Name | Type | Req | Description |
|---|---|---|---|
| cities | – | – | – |
| current_company_keyword | – | – | – |
| current_investor_keyword | – | – | – |
| cursor | – | – | – |
| education_keyword | – | – | – |
| ever_job_keyword | – | – | – |
| fields | – | – | – |
| is_on_job | – | – | – |
| keyword | string | – | – |
| location | – | – | – |
| page_size | – | – | – |
| person_type_keyword | – | – | – |
| provinces | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_person_investment_cases ~137
按人物ID或人物姓名分页查询人物投资案例，可按被投公司标签、行业和轮次筛选，适合回答某位投资人个人参与投资过哪些公司；高权限套餐可查看未披露水下事件标识。
| Name | Type | Req | Description |
|---|---|---|---|
| company_tag_ids | – | – | – |
| company_tag_match_mode | string | – | – |
| cursor | – | – | – |
| fields | – | – | – |
| is_underwater | – | – | – |
| page_size | – | – | – |
| person_id | – | – | – |
| person_keyword | – | – | – |
| round_ids | – | – | – |
| scope_ids | – | – | – |
| sub_scope_ids | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
search_tags ~52
按关键词搜索标签，适合把用户输入的赛道词如人工智能、机器人、低空经济映射为 tag_id。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
What is the IT桔子 MCP server?
IT桔子 MCP is listed in the public MCP registry as io.github.lgyers/itjuzi-mcp. Hosted MCP for IT桔子 primary market company, funding, investor and sector data. This page covers its hosted endpoint (https://mcp.itjuzi.com/mcp).
Is the IT桔子 MCP server safe to use?
IT桔子 MCP scores 73 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 IT桔子 MCP server expose?
IT桔子 MCP exposes 21 tools: search_companies, count_companies, search_closed_companies, count_closed_companies, analyze_closed_company_cohort, and 16 more. Their descriptions and schemas cost roughly 2,868 tokens of context every time the server is loaded.
Does the IT桔子 MCP server require authentication?
No. We connected to IT桔子 MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the IT桔子 MCP server still maintained?
IT桔子 MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.