@slingshot-fyi/brand-kit on npm, listed in the MCP Registry as fyi.slingshot/brand-kit: the brand guides, the design tokens and an off-brand colour check, for any MCP client.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"slingshot-brand-kit-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
No successful checks in the window.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 18 h ago | mcp initialize | failed | 404 | 120 ms | http 404 |
| 7 d ago | mcp initialize | failed | 404 | 103 ms | http 404 |
| 14 d ago | mcp initialize | failed | 404 | 309 ms | http 404 |
| 20 d ago | mcp initialize | failed | 404 | 143 ms | http 404 |
| 24 d ago | mcp initialize | failed | 404 | 112 ms | http 404 |
| 26 d ago | mcp initialize | failed | 404 | 114 ms | http 404 |
| 27 d ago | mcp initialize | failed | 404 | 105 ms | http 404 |
| 28 d ago | mcp initialize | failed | 404 | 104 ms | http 404 |
Attributed to the source that supplied each field. Treated as claims, not facts.
No long description beyond the summary.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.