Skip to content
Back to search

manufact-leaderboard

GitHub Action: rescan your MCP server on the Manufact leaderboard after each deploy and report its score

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mcp-use--manufact-leaderboard/badge.svg)](/listings/mcp-use--manufact-leaderboard)

HTML

<a href="/listings/mcp-use--manufact-leaderboard"><img src="/api/listings/mcp-use--manufact-leaderboard/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 53 lines
  1. # Manufact Leaderboard
  2. Rescan your MCP server on the [Manufact leaderboard](https://manufact.com/leaderboard) after every deploy, wait for the review, and get the new score in the run summary.
  3. The server must be verified by your workspace first: open its leaderboard page and choose **Verify**. Only the verifying workspace can rescan it.
  4. ## Usage
  5. Add a `MANUFACT_API_KEY` repository secret with an API key from that workspace, then add a step after your deploy:
  6. ```yaml
  7. - name: Manufact Leaderboard
  8. uses: mcp-use/manufact-leaderboard@v1
  9. with:
  10. api-key: ${{ secrets.MANUFACT_API_KEY }}
  11. url: https://mcp.example.com/mcp
  12. ```
  13. The step prints the score and a report link, and writes them to the job summary. A rescan that can't start, fails, or runs past the timeout leaves a warning and never fails your deploy, unless you set `fail-on-error: true`.
  14. ## Inputs
  15. | Input | Default | Description |
  16. | --- | --- | --- |
  17. | `api-key` | required | Manufact API key from the workspace that verified the server. |
  18. | `url` | required | The server's MCP endpoint URL, as listed on the leaderboard. |
  19. | `wait` | `true` | Wait for the rescan and report the score. `false` only starts it. |
  20. | `timeout-minutes` | `10` | How long to wait for the rescan. |
  21. | `fail-on-error` | `false` | Fail the step when the rescan can't start or fails. |
  22. | `api-url` | `https://api.manufact.com` | Manufact API base URL. |
  23. | `site-url` | `https://manufact.com` | Manufact website base URL, for the report link. |
  24. ## Outputs
  25. | Output | Description |
  26. | --- | --- |
  27. | `score` | Score out of 100 after the rescan. |
  28. | `status` | `completed`, `failed`, `running` (timed out) or `started` (`wait: false`). |
  29. | `slug` | The server's leaderboard slug. |
  30. | `report-url` | Link to the server's leaderboard report. |
  31. Use the score in a later step, for example to comment on a pull request:
  32. ```yaml
  33. - id: leaderboard
  34. uses: mcp-use/manufact-leaderboard@v1
  35. with:
  36. api-key: ${{ secrets.MANUFACT_API_KEY }}
  37. url: https://mcp.example.com/mcp
  38. - run: echo "Score ${{ steps.leaderboard.outputs.score }} - ${{ steps.leaderboard.outputs.report-url }}"
  39. ```
  40. The action uses `bash`, `curl` and `jq`, which GitHub-hosted runners include.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.