← Back to browse

MCP 2000

Generative drum machine and sampler in the browser

Added April 6, 2026 · Last analysed April 10, 2026 · via Hacker News · also on Product Hunt · 67% unique tagline

StackScope is a free public catalogue of indie launches. We find launches on Product Hunt, Hacker News and similar feeds, then crawl each site to detect its tech stack and score it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 10 April 2026; the live site may have changed since.

MCP 2000 is early-stage. Worth fixing first: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Hacker News on April 6, 2026. The site is hosted on Vercel, with a domain registered 1 week before launch. We've detected 4 technologies on this site, covering developer tools, DNS providers, hosting, and security. The stack includes HSTS, Vercel, and Vercel DNS.

It's running the same core stack as 2,959 other launches.

If you own this site, refresh the snapshot and see the full fix list any time →

3.0
StackScope Score
Poor
88/100 Launch Readiness
Launch ready
0/3 Legal
Missing
0/2 Crawl files
Missing
Vibe Score 0 · No AI signals
How much the site looks AI-generated. Informational pattern-match signal, not a verdict. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (4)

Infrastructure
DNS Vercel DNS
Hosting Vercel (2)
Security HSTS (2)
Build & Framework
Developer tools Vite

Infrastructure

Network
AS16509 · US
DNS
Vercel DNS
Authoritative nameserver
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
Domain Age
3 months
Registered Mar 2026 · Name.com, Inc.

Email Security

SPF Not published. Your domain can be spoofed in phishing emails.
?
DKIM Not detected at common selectors. Your provider may use a custom one.
DMARC Not published. Receivers fall back to permissive defaults.
?
MTA-STS Not deployed. Mail to your domain can be downgraded to plaintext en route.
?
TLS-RPT Not configured. You won't hear about silent SMTP TLS handshake failures.

Readiness Breakdown How?

Custom title and meta description
Open Graph tags (title, image, description)
Twitter card meta tags
Responsive viewport meta tag
Favicon present
Semantic HTML (nav, main, article)
- Canonical URL declared

AI Stance

No AI stance declared
llms.txt published
No AI bots blocked in robots.txt
? No directive declared
? None advertised

Well-Known Files

robots.txt
sitemap.xml
security.txt
llms.txt
ads.txt
humans.txt
? Privacy Policy not detected
? Terms of Service not detected
Detection works best on English language sites.

Security Headers (1/6)

Permissions-Policy experimental (check browser support)
X-XSS-Protection deprecated (use Content-Security-Policy)

Performance

56ms response time
Faster than 99% of sites

Build

1 JS files
1 CSS files
0 Third-party domains

Brand Colours

Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.