Content Intelligence API
REMOTE · CONTENT-INTELLIGENCE-MCP.WAJIH-HYDER55.WORKERS.DEV · SCANNED SEP 20
9 MCP tools: extract, analyze, research, compare, monitor, brief. Pay-per-call x402 or subscribe.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 684 tokens (~76/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Content Intelligence API MCP server?
Content Intelligence API is a hosted endpoint at https://content-intelligence-mcp.wajih-hyder55.workers.dev/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · content-intelligence-mcp.wajih-hyder55.workers.dev
claude mcp add --transport http ruvendors5-ops-content-intelligence-api 'https://content-intelligence-mcp.wajih-hyder55.workers.dev/'
{
"mcpServers": {
"ruvendors5-ops-content-intelligence-api": {
"url": "https://content-intelligence-mcp.wajih-hyder55.workers.dev/"
}
}
} {
"servers": {
"ruvendors5-ops-content-intelligence-api": {
"type": "http",
"url": "https://content-intelligence-mcp.wajih-hyder55.workers.dev/"
}
}
} [mcp_servers.ruvendors5-ops-content-intelligence-api] url = "https://content-intelligence-mcp.wajih-hyder55.workers.dev/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ruvendors5-ops-content-intelligence-api": {
"type": "remote",
"url": "https://content-intelligence-mcp.wajih-hyder55.workers.dev/",
"enabled": true
}
}
} openclaw mcp add ruvendors5-ops-content-intelligence-api --url 'https://content-intelligence-mcp.wajih-hyder55.workers.dev/' --transport streamable-http
mcp_servers:
ruvendors5-ops-content-intelligence-api:
url: "https://content-intelligence-mcp.wajih-hyder55.workers.dev/" {
"McpServers": {
"ruvendors5-ops-content-intelligence-api": {
"Transport": "http",
"Url": "https://content-intelligence-mcp.wajih-hyder55.workers.dev/"
}
}
} assistant mcp add ruvendors5-ops-content-intelligence-api -t streamable-http -u 'https://content-intelligence-mcp.wajih-hyder55.workers.dev/'
{
"mcpServers": {
"ruvendors5-ops-content-intelligence-api": {
"type": "http",
"url": "https://content-intelligence-mcp.wajih-hyder55.workers.dev/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://content-intelligence-mcp.wajih-hyder55.workers.dev
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wajih-hyder55.workers.dev | CN=WE1,O=Google Trust Services,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9b1571882e3ec68b1314e61b059c3730 |
| SANs: wajih-hyder55.workers.dev, *.wajih-hyder55.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of content-intelligence-mcp.wajih-hyder55.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://content-intelligence-mcp.wajih-hyder55.workers.dev | Verified | 200 | |
| http (plaintext) | http://content-intelligence-mcp.wajih-hyder55.workers.dev | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_text ~54
Analyze text for summary, sentiment, entities, topics, and classification. Pay per call (0.003 USDC) or use subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to analyze (up to 50k chars) |
No output schema declared.
No examples provided.
compare_articles ~87
Compare two sources (URLs or text) for similarities, differences, coverage, and bias. Pay per call (0.01 USDC) or use subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | Optional focus aspect (e.g., 'security', 'performance') |
| source_a | string | yes | First source URL or text content |
| source_b | string | yes | Second source URL or text content |
No output schema declared.
No examples provided.
competitor_intel ~94
Competitive intelligence analysis comparing two companies/entities. Searches web, extracts content, and provides structured comparison. Pay per call (0.025 USDC) or use subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | – | Optional focus area (e.g., 'market share', 'innovation') |
| company_a | string | yes | First company name |
| company_b | string | yes | Second company name |
| industry | string | – | Optional industry context |
No output schema declared.
No examples provided.
daily_brief ~97
Generate a briefing from multiple URLs or topics. Supports executive, bullet, and detailed formats. Pay per call (0.015 USDC) or use subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | Optional focus area for the briefing |
| format | string | – | Briefing format style |
| topics | array | – | Array of topics to search and include in the brief |
| urls | array | – | Array of URLs to include in the brief |
No output schema declared.
No examples provided.
extract_content ~50
Extract clean readable content from a URL. Removes ads, clutter, navigation. Pay per call (0.005 USDC) or use subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to extract content from |
No output schema declared.
No examples provided.
extract_structured ~69
Extract structured JSON data from a URL. Define a schema or let AI infer the structure. Pay per call (0.008 USDC) or use subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| schema | object | – | Optional JSON schema definition for extraction fields |
| url | string | yes | The URL to extract structured data from |
No output schema declared.
No examples provided.
monitor_page ~93
Extract a page with a content hash for change detection. Use action 'watch' to register for ongoing monitoring. Pay per call (0.005 USDC) or use subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | 'check' returns content + hash; 'watch' registers for ongoing change detection |
| page_id | string | – | Optional custom ID for the monitored page |
| url | string | yes | The URL to monitor |
No output schema declared.
No examples provided.
research_topic ~58
Multi-source research synthesis on any topic. Searches the web and synthesizes findings with AI. Pay per call (0.02 USDC) or use subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | – |
| query | string | yes | Research query or topic |
No output schema declared.
No examples provided.
sentiment_over_time ~82
Analyze sentiment trends across multiple sources (URLs or texts). Compares and synthesizes sentiment. Pay per call (0.008 USDC) or use subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| texts | array | – | Array of text contents to analyze for sentiment |
| topic | string | – | Optional topic context for analysis |
| urls | array | – | Array of URLs to analyze for sentiment |
No output schema declared.
No examples provided.
What is the Content Intelligence API MCP server?
Content Intelligence API is an MCP server listed in the public MCP registry as io.github.ruvendors5-ops/content-intelligence-api. 9 MCP tools: extract, analyze, research, compare, monitor, brief. Pay-per-call x402 or subscribe. This page covers its hosted endpoint (https://content-intelligence-mcp.wajih-hyder55.workers.dev).
Is the Content Intelligence API MCP server safe to use?
Content Intelligence API scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Content Intelligence API MCP server expose?
Content Intelligence API exposes 9 tools: extract_content, analyze_text, research_topic, compare_articles, extract_structured, and 4 more. Their descriptions and schemas cost roughly 684 tokens of context every time the server is loaded.
Does the Content Intelligence API MCP server require authentication?
No. We connected to Content Intelligence API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Content Intelligence API MCP server still maintained?
Content Intelligence API is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.