Manufact's leaderboard has already scored MCP servers on public report pages: 3,066 of the site's 3,524 sitemap URLs are leaderboard pages, and the index lists "1,459 verified MCP servers" plus a Community tab of 3,064. Every report has "Improve", "Share" and "Fix prompt" buttons, but there is no badge to embed, no README snippet, no way for a server's owner to claim the page and no way to follow score changes. The people who own those servers are exactly who Manufact sells to, and today a report is a dead end for them.
First action
Ship a static badge endpoint for every report and add a "Get your badge" box under the score.
How to measure it
Report-page sign-ups (claims plus Fix with Manufact)
- Now
- –
- Target
- 300 claimed servers and 150 sign-ups
- By
- 90 days
Steps
Build the badge
A cached SVG per report with score and grade, plus Markdown and HTML snippets.
Founding Software Engineer (Product / MCP) 2 days
Add the box
"Get your badge" and "Claim this server" under the score on every report.
Founding Software Engineer (Product / MCP) 1 day
Design verification
Prove ownership with a well-known file or a token in server metadata; no claims without it.
Senior Infrastructure Engineer 3 days
Score-change emails
Weekly email to claimed owners when a check or grade changes, linking to the fix.
Founding Software Engineer (Product / MCP) 3 days
Seed the top grades
Send A and A+ servers their badge with a short note and a PR-ready snippet.
Developer Advocate & Partnerships 1 week
Route claims
Claims go to the CRM with score gaps; SDR follows up within a day.
Sales Development Representative 2 days
Measure
Badge views, referral clicks, claims, sign-ups and paid conversions.
Founders (CEO) weekly
Why it works
Add two things to every report page. 1) A badge: a live SVG ("MCP quality 96/100 · A+", scored by Manufact) with copy-paste Markdown for READMEs and docs, linking back to the report. 2) "Claim this server": the owner verifies the server (for example with a well-known file or a tool-metadata token), signs up, and gets a weekly email when their score or a check changes, with a one-click "Fix with Manufact" path to Cloud Inspector, publishing checks and hosting. Send claims to the new SDR as inbound with a buying signal: the score gaps are the opener. Start by emailing the top-graded servers their badge, since A grades are what owners want to show off.
Badges are how developer tools spread (build status, coverage, package version): each one puts Manufact's name and a link in front of every visitor to that repo, and builds links back to the leaderboard. Claiming turns an anonymous public score into an account with a reason to come back every week, and lower-scored owners get a direct path to the paid checks and hosting that fix the problem.
Ready to use
ChecklistLeaderboard badge and claim launch list
[ ] /leaderboard/<slug>/badge.svg (score, grade, "scored by Manufact"), cached [ ] Markdown snippet: [](https://manufact.com/leaderboard/<slug>) [ ] "Get your badge" box under the score [ ] "Claim this server" with ownership proof [ ] Weekly score-change email for claimed owners [ ] "Fix with Manufact" link to Cloud Inspector and publishing checks [ ] Claims into CRM with the three weakest checks [ ] Tracking: badge views, referral clicks, claims, sign-ups
Risks and how to handle them
Owners object to a public score or a low grade
Let claimed owners request a rescore and see exact fixes; show the date of the last review.
False claims on popular servers
Require technical proof of control before a claim is accepted.
Evidence
- Your websiteLeaderboard (checked November 9, 2026): title "MCP Quality Checker & Leaderboard", H1 "How good is your MCP?"; "1,459 verified MCP servers, ranked by quality score", a Community tab of 3,064 and a chart of "968 scored MCPs"; a "Score my MCP" form that takes an MCP URL. The page has no badge, embed, README snippet, claim or notify option.Source
- Your websiteServer report pages (sample checked November 9, 2026): titled "<Server> MCP Server: 96/100 Quality | Manufact", scoring six areas (server metadata, discoverability, protocol, tools, MCP Apps, tool documentation quality) with "Improve", "Share" and "Fix prompt" buttons and a "Score your MCP" link; no badge, embed code, claim option or way for the server's owner to follow changes.Source
- Your websiteSitemap (3,524 URLs, read November 9, 2026): 3,066 under /leaderboard, 73 blog posts, seven /platform pages, and single pages for /templates, /compare, /startups, /enterprise, /vibe, /builder, /inspector and /stats; no per-competitor comparison pages and no per-template pages.Source
- HiringSales Development Representative (San Francisco or remote US): handle inbound leads and convert them into qualified demos, follow up warm prospects in the CRM, focus on leads with buying signals "instead of cold blasting", later open new markets and test new acquisition channels.Source