mcp-registry/io.github.ruvendors5-ops/content-intelligence-api · v2.4.0
Also listed as glama/ruvendors5-ops/content-intelligence-mcp-server
As of 2026-10-20 11:22 UTC, the Ruvendors5 Ops Content Intelligence Api MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
9 MCP tools: extract, analyze, research, compare, monitor, brief. Pay-per-call x402 or subscribe.
Claude Code
claude mcp add --transport http ruvendors5-ops-content-intelligence-api- https://content-intelligence-mcp.wajih-hyder55.workers.dev
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"ruvendors5-ops-content-intelligence-api-": {
"type": "http",
"url": "https://content-intelligence-mcp.wajih-hyder55.workers.dev"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.ruvendors5-ops%2Fcontent-intelligence-api/fixes
{
"name": "analyze_text",
"description": "Analyze text for summary, sentiment, entities, topics, and classification. Pay per call (0.003 USDC) or use subscription.",
"inputSchema": {
"type": "object",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"description": "The text to analyze (up to 50k chars)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "compare_articles",
"description": "Compare two sources (URLs or text) for similarities, differences, coverage, and bias. Pay per call (0.01 USDC) or use subscription.",
"inputSchema": {
"type": "object",
"required": [
"source_a",
"source_b"
],
"properties": {
"aspect": {
"type": "string",
"description": "Optional focus aspect (e.g., 'security', 'performance')"
},
"source_a": {
"type": "string",
"description": "First source URL or text content"
},
"source_b": {
"type": "string",
"description": "Second source URL or text content"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.ruvendors5-ops/content-intelligence-api"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.ruvendors5-ops/content-intelligence-api"}) over MCP.
daily_brief ~219 tokenssentiment_over_time ~204 tokenscompetitor_intel ~170 tokensmonitor_page ~164 tokenscompare_articles ~143 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.ruvendors5-ops%2Fcontent-intelligence-api?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.ruvendors5-ops%2Fcontent-intelligence-api?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ruvendors5-ops%2Fcontent-intelligence-api.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.ruvendors5-ops%2Fcontent-intelligence-api.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.ruvendors5-ops%2Fcontent-intelligence-api?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:35f4d8e3eb15c4f0…, first seen 2026-10-17, included at leaf 496 of 32,598. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable data servers · most reliable knowledge servers · most reliable productivity servers · most reliable web servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 11:22 UTC, the Ruvendors5 Ops Content Intelligence Api MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Ruvendors5 Ops Content Intelligence Api MCP server advertises 9 tools, including analyze_text, compare_articles, competitor_intel, daily_brief, extract_content.
Point your MCP client at this streamable-http endpoint: https://content-intelligence-mcp.wajih-hyder55.workers.dev
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.