Tengence Search MCP
NPM · @TENGENCE/SEARCH-MCP
Thin MCP wrapper for the Tengence Search SaaS: push data and search via official APIs.
Available components
Last scanned (2 hours ago)
Scores higher than 45% of npm servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 33 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 625 tokens (~156/item across 4 items; 4 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 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 4 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
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.
- 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 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 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.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed npm/@tengence/search-mcp@0.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
data_push ~127
向通智搜索数据集推送数据（单条对象或批量数组，同一入口）。自动幂等注册并校验已初始化。每条必须含唯一 id：不存在则新增、已存在则更新、仅含 id 无其他字段则删除该条（删除不可逆）、字段值为 null 则移除该字段、新字段自动新增。
| Name | Type | Req | Description |
|---|---|---|---|
| chunkSize | integer | – | 批量分块大小，默认 100 |
| records | – | yes | 单条记录对象，或记录对象数组（数组内每条必须含 id） |
No output schema declared.
No examples provided.
ping ~126
服务状态与配置诊断（只读、无副作用）。返回版本、注册状态（懒加载注册）、初始化状态（search_init 是否已执行）、clientId（掩码）、配置概览（各端点与 Key 是否配置，掩码显示）、state.json 路径。probe=true 时额外对三个下游（注册/推送/搜索）做连通性探测。推送或搜索失败时先用 ping 定位。
| Name | Type | Req | Description |
|---|---|---|---|
| probe | boolean | – | 是否做下游连通性探测，默认 false |
No output schema declared.
No examples provided.
search ~215
调用通智搜索搜索接口。自动幂等注册并校验已初始化。query 必填；支持分页（page/size，size≤100）、排序（sortFields）、高亮（highlightFields）、聚合（aggregations）、指定检索字段（searchFields）、返回字段（includeFields）、过滤（filters，多条件 AND，操作符 eq/ne/gt/gte/lt/lte/in/not_in/exists/not_exists）。
| Name | Type | Req | Description |
|---|---|---|---|
| aggregations | array | – | 聚合 |
| filters | array | – | 过滤条件，多条件 AND |
| highlightFields | array | – | 高亮字段 |
| includeFields | array | – | 仅返回指定字段 |
| page | integer | – | 页码，默认 1 |
| query | string | yes | 搜索关键词（必填） |
| searchFields | array | – | 指定检索字段 |
| size | integer | – | 每页条数，默认 20，最大 100 |
| sortFields | array | – | 排序字段 |
No output schema declared.
No examples provided.
search_init ~157
初始化搜索应用（幂等，可重复调用）：自动注册客户端（若未注册）→ 服务端组合创建「数据集 + 搜索应用」并绑定（免费套餐）→ 返回数据集 API Key 与搜索应用 API Key（掩码显示），双 Key 落盘本地 state.json（0600）。首次注册成功时额外返回控制台登录信息（登录地址/账号/初始密码/一次性 token，明文仅交付一次并落盘本地）；免费版配额用满时 push/search 会基于该登录信息提示登录扩容。首次使用 data_push / search 前必须先调用本工具。重复调用直接返回现有资源，不重复创建。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Tengence Search MCP server?
Tengence Search MCP runs locally as an npm package, launched with npx -y @tengence/search-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @tengence/search-mcp
claude mcp add com-tengence-search -- npx -y @tengence/search-mcp
What is the Tengence Search MCP server?
Tengence Search MCP is listed in the public MCP registry as com.tengence/search. Thin MCP wrapper for the Tengence Search SaaS: push data and search via official APIs. This page covers its npm package (@tengence/search-mcp).
Is the Tengence Search MCP server safe to use?
Tengence Search MCP scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Tengence Search MCP server expose?
Tengence Search MCP exposes 4 tools: search_init, data_push, search, ping. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.
Is the Tengence Search MCP server still maintained?
Tengence Search MCP 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.
What licence is the Tengence Search MCP server under?
Tengence Search MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.