modelcontextprotocol / modelcontextprotocol/ext-apps

Add your HVTrust badge to the README?

Open Beginner friendly
#711 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.9k
Forks
387
Avg merge
3h 21m
Merged PRs (30d)
6

Description

Hi MCP Apps maintainers 👋

I maintain HVTracker (hvtracker.net) — an independent, open trust registry for AI agents and MCP servers. Projects are scored on public, verifiable signals only: release/package provenance and signed commits, OpenSSF Scorecard, download/maintenance evidence, and supply-chain checks. Every project gets a transparent HVTrust score + letter grade. There's no pay-to-rank, and the methodology is fully public.

MCP Apps is already listed, and here's where it currently stands:

HVTrust 73.3 · Grade B — ranked #80 of 417 tracked projects
Full evidence breakdown: https://hvtracker.net/agents/mcp-apps/

If you'd like to surface that on your README, here's the embed — it auto-updates as your score changes, so it stays accurate over time:

[![HVTrust](https://hvtracker.net/badge/mcp-apps.svg)](https://hvtracker.net/agents/mcp-apps/)

Prefer a letter grade or a 30-day trend arrow instead of the score? Just swap the image URL for https://hvtracker.net/badge/mcp-apps-grade.svg or https://hvtracker.net/badge/mcp-apps-trend.svg.

A few projects already embed theirs — e.g. Haystack, Composio, and LightRAG.

If you think a signal is off, we correct on evidence — no account needed: https://hvtracker.net/correct/

No pressure at all: if this isn't useful to you, please just close the issue and I won't follow up. Thanks for building MCP Apps! 🙏

Contributor guide

Open the contributing guide

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.

Research direction

Open the repository README and check where project badges are currently displayed. If the maintainers approve the request, add the supplied HVTrust badge link, then render or preview the README to confirm the badge and destination link display correctly.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.