@tengence/search-mcp

Name: @tengence/search-mcp
Author: com.tengence

MCPcommunity

v0.1.5com.tengenceMITUpdated 10d agonpm GitHub

Thin MCP wrapper for the Tengence Search SaaS: push data and search via official APIs.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1kDownloads/wk

10d agoLast update

Reads these credentials

TENGENCE_SEARCH_API_KEYAPI keyoptional
Search API key (app-level, sk-) for the /v1/search endpoint. Optional: search_init auto-provisions and stores it locally (state.json).
TENGENCE_DATASET_API_KEYAPI keyoptional
Dataset API key (sk-) for the /v1/push/data endpoint.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authorcom.tengence

LicenseMIT

Version0.1.5

Sourcenpm+mcp-registry

npm@tengence/search-mcp

GitHubtengence-team/tengence-search-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface4 tools · none privileged

Security scan✓ Cleanv0.1.5 · 4d agoHow well does this scan work?

EvalsNone

IndexedOct 8, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged

Statically extracted from the published packagev0.1.5 · 4d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

search_init初始化搜索应用（幂等，可重复调用）：自动注册客户端（若未注册）→ 服务端组合创建「数据集 + 搜索应用」并绑定（免费套餐）→ 返回数据集 API Key 与搜索应用 API Key（掩码显示），双 Key 落盘本地 state.json（0600）。首次注册成功时额外返回控制台登录信息（登录地址/账号/初始密码/一次性 token，明文仅交付一次并落盘本地）；免费版配额用满时 push/search 会基于该登录信息提示登录扩容。首次使用 data_push / search 前必须先调用本工具。重复调用直接返回现有资源，不重复创建。

初始化搜索应用（幂等，可重复调用）：自动注册客户端（若未注册）→ 服务端组合创建「数据集 + 搜索应用」并绑定（免费套餐）→ 返回数据集 API Key 与搜索应用 API Key（掩码显示），双 Key 落盘本地 state.json（0600）。首次注册成功时额外返回控制台登录信息（登录地址/账号/初始密码/一次性 token，明文仅交付一次并落盘本地）；免费版配额用满时 push/search 会基于该登录信息提示登录扩容。首次使用 data_push / search 前必须先调用本工具。重复调用直接返回现有资源，不重复创建。

No input schema was published for this tool.

data_push向通智搜索数据集推送数据（单条对象或批量数组，同一入口）。自动幂等注册并校验已初始化。每条必须含唯一 id：不存在则新增、已存在则更新、仅含 id 无其他字段则删除该条（删除不可逆）、字段值为 null 则移除该字段、新字段自动新增。

向通智搜索数据集推送数据（单条对象或批量数组，同一入口）。自动幂等注册并校验已初始化。每条必须含唯一 id：不存在则新增、已存在则更新、仅含 id 无其他字段则删除该条（删除不可逆）、字段值为 null 则移除该字段、新字段自动新增。

No input schema was published for this tool.

search调用通智搜索搜索接口。自动幂等注册并校验已初始化。query 必填；支持分页（page/size，size≤100）、排序（sortFields）、高亮（highlightFields）、聚合（aggregations）、指定检索字段（searchFields）、返回字段（includeFields）、过滤（filters，多条件 AND，操作符 eq/ne/gt/gte/lt/lte/in/not_in/exists/not_exists）。

调用通智搜索搜索接口。自动幂等注册并校验已初始化。query 必填；支持分页（page/size，size≤100）、排序（sortFields）、高亮（highlightFields）、聚合（aggregations）、指定检索字段（searchFields）、返回字段（includeFields）、过滤（filters，多条件 AND，操作符 eq/ne/gt/gte/lt/lte/in/not_in/exists/not_exists）。

No input schema was published for this tool.

ping服务状态与配置诊断（只读、无副作用）。返回版本、注册状态（懒加载注册）、初始化状态（search_init 是否已执行）、clientId（掩码）、配置概览（各端点与 Key 是否配置，掩码显示）、state.json 路径。probe=true 时额外对三个下游（注册/推送/搜索）做连通性探测。推送或搜索失败时先用 ping 定位。

服务状态与配置诊断（只读、无副作用）。返回版本、注册状态（懒加载注册）、初始化状态（search_init 是否已执行）、clientId（掩码）、配置概览（各端点与 Key 是否配置，掩码显示）、state.json 路径。probe=true 时额外对三个下游（注册/推送/搜索）做连通性探测。推送或搜索失败时先用 ping 定位。

No input schema was published for this tool.

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Thin MCP wrapper for the Tengence Search SaaS: push data and search via official APIs.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-09 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
@tengence/search-sdk0.1.1
@modelcontextprotocol/sdk1.32.117 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.8
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.5
- cors2.8.6+2 not drawn
- hono4.13.13
- jose6.2.12
- express5.2.1+27 not drawn1 dependency
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.4
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.1+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 50
below the depth cap: 5

es-define-property ^1.0.1 — required by qs@6.16.0package cap reached
wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached

+43 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

@tengence/search-mcp

Tools

Tools exposed

Dependency tree

Declared but not resolved

Topics

Related in search & retrieval