Optional pre-connect TrustScore signal for MCP servers?

Open
#13,345 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 8 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
TypeScript
Stars
36.5k
Forks
5.6k
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from continuedev/continue

All issues in continuedev/continue

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.