MCP server health, State of MCP census
Content Intelligence API
io.github.ruvendors5-ops/content-intelligence-api
9 MCP tools: extract, analyze, research, compare, monitor, brief. Pay-per-call x402 or subscribe.
Checks
The exact rows akashi check io.github.ruvendors5-ops/content-intelligence-api prints, from the 2026-07-02 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | warn | probe error: http2: response body closed |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 9 tools: extract_content, analyze_text, research_topic, compare_articles, extract_structured, sentiment_over_time, competitor_intel, monitor_page, ... |
| at least one live entrypoint | pass | 1 alive |
Evidence
Packages
No packages declared.
Remote endpoints
- https://content-intelligence-mcp.wajih-hyder55.workers.dev
streamable-http · reachable· HTTP 200· initialize_ok
9 tools: extract_content, analyze_text, research_topic, compare_articles, extract_structured, sentiment_over_time, competitor_intel, monitor_page, ...
server.json
validagainst its declared schema
One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).
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 io.github.ruvendors5-ops/content-intelligence-apiInstall 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 io.github.ruvendors5-ops/content-intelligence-api --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.