Optional pre-connect TrustScore signal for MCP servers?

未关闭
#13,345 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 8 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript

调研方向

No files, tests, or implementation entry points are named. First clarify whether Continue wants this feature and what behavior the opt-in check and threshold should have; then locate the MCP server setup flow and its tests. Done would mean an agreed scope and verified behavior for showing the score and certificate, with the check off by default.

由索引模型根据 Issue 内容生成。

描述

continue lets users wire in MCP servers as tools, which raises a before-you-connect question: can we show how trustworthy a given MCP server is first?

there's a public TrustScore for ~19.7K MCP servers/agents today. an optional check could surface a server's score (+ cert) when it's added, and let the user gate on a threshold. it's a lookup against our small MIT service / public index (trustmodel), no core change.

off by default, opt-in, metadata only.

is a pre-connect trust signal for MCP servers something continue would want to surface? glad to send a reference. https://trustmodel.ai/verify

主要语言
TypeScript
星标
36.5k
派生
5.6k
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

continuedev/continue 的其他 Issue

查看 continuedev/continue 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。