MCP server health, State of MCP census
SparkForge — 20+ Utility APIs with x402 Micropayments
sh.sparkforge/sparkforge
20+ pay-per-use APIs: image gen, crypto data, email verify, SSL check, web scraping, and more.
- remote_404
Checks
The exact rows akashi check sh.sparkforge/sparkforge prints, from the 2026-08-03 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | pass | exists |
| repo freshness | warn | no push in 154d |
| remote reachable | fail | 404 (endpoint gone) |
| at least one live entrypoint | pass | 1 alive |
| license present | warn | none detected |
Spec 2026-07-28 readiness
No runtime readiness verdict: this server has no keylessly reachable conformant MCP endpoint (package-only, auth-gated, or down at census time), so its behavior against the 2026-07-28 revision cannot be measured without credentials. Absence of evidence is recorded as absence, never guessed. Ecosystem numbers: the readiness report.
Evidence
Packages
No packages declared.
Remote endpoints
- https://sparkforge.sh/mcp
streamable-http · not_found· HTTP 404
server.json
validagainst its declared schema
One of 19804 servers in the 2026-08-03 State of MCP census: 15974 healthy (80.7%), 2792 degraded (14.1%), 851 dead (4.3%), 187 unknown (0.9%).
Verify it yourself
This page is a static read of one dated probe. Run the same check locally, any time, with no key:
$ akashi check sh.sparkforge/sparkforgeInstall Akashi - single Go binary, zero keys, MIT licensed.
Is this your server?
Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check sh.sparkforge/sparkforge --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.