Content Tools
isicca.com
Searches for articles, videos, and AI tools from a curated tech radar.
ENDPOINT 1
https://isicca.com/api/mcp
MCP server metadata
- Name
- blog-content-manager
- Version
- 2.3.0
Read-only access to isicca.com's published content: blog articles, curated videos, and the AI tech radar. All content is bilingual: localized fields (titles, summaries, article content, descriptions, justifications, video URLs) always carry both `en` and `fr`. Search results include `total` (matches before `limit`); raise `limit` if it exceeds the returned count. Write tools require connecting with the admin bearer token.
Known tools 3
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.blog-content-manager]
url = "https://isicca.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"blog-content-manager": {
"type": "http",
"url": "https://isicca.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: blog-content-manager
Remote MCP URL: https://isicca.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"blog-content-manager": {
"url": "https://isicca.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"blog-content-manager": {
"type": "http",
"url": "https://isicca.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "blog-content-manager",
"transport": "streamable-http",
"url": "https://isicca.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for isicca.com was fetched 2026-08-05T17:26:28.967Z and is being refreshed.
isicca.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.