Is the Civai Nova Blogger Agent MCP server down?

mcp-registry/co.civai.nova/blogger-agent · v1.0.0

healthy
Last checked 2026-10-27 00:26 UTC · handshake 155ms

As of 2026-10-27 00:26 UTC, the Civai Nova Blogger Agent MCP server is up with a Glimind reliability score of 73/100 (grade C). Over the last 30 days it answered 98.7% of Glimind's liveness checks. It had 61 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
98.7%
checks observed
4,856
outages (90d)
61
tools
6

I do everything related to Google Blogger content

Point your MCP client at this streamable-http endpoint: https://nova.civai.co/mcp/agents/blogger-agent

Agent-readiness: D (58/100)

D (58/100): 0 error(s), 6 warning(s) across 6 tool(s); ~261 tokens of tool definitions.
Scores higher than 0% of 15,774 MCP servers Glimind has audited.
Its tool list costs an agent ~261 tokens per session — lighter than 99% of servers.
58 → 58 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions13
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability75
Stability40

What to fix (7)

6 of 6 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 →

Tools: converse, create_draft, list_drafts, post_blog_content, trend_search and 1 more

5 parameter(s) across 5 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 →

Tools: create_draft, list_drafts, post_blog_content, trend_search, view_draft

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_draft, post_blog_content

1 tool(s) have descriptions under 20 characters.

Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →

Tools: view_draft

Reachable 98.7% of the time over the last 30 days; median recovery 7 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

In the last 30 days: 6 tool(s) removed and 0 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. 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 →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fco.civai.nova%2Fblogger-agent/fixes

create_draft 1 change
{
  "name": "create_draft",
  "description": "Blogger: create_draft",
  "inputSchema": {
    "type": "object",
    "properties": {
      "detail": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
list_drafts 1 change
{
  "name": "list_drafts",
  "description": "Blogger: list_drafts",
  "inputSchema": {
    "type": "object",
    "properties": {
      "detail": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
post_blog_content 1 change
{
  "name": "post_blog_content",
  "description": "Blogger: post_blog_content",
  "inputSchema": {
    "type": "object",
    "properties": {
      "detail": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

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/co.civai.nova/blogger-agent"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/co.civai.nova/blogger-agent"}) over MCP.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fco.civai.nova%2Fblogger-agent.svg)](https://glimind.com/server/mcp-registry%2Fco.civai.nova%2Fblogger-agent?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fco.civai.nova%2Fblogger-agent?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fco.civai.nova%2Fblogger-agent.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fco.civai.nova%2Fblogger-agent.svg
   :target: https://glimind.com/server/mcp-registry%2Fco.civai.nova%2Fblogger-agent?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:be5f1eed8b9995c0…, first seen 2026-10-17, included at leaf 9417 of 76,335. Version history · verify what your client received.

Tools (6)

Compare: most reliable communication servers · most reliable productivity servers · most reliable search servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Civai Nova Blogger Agent MCP server down right now?

As of 2026-10-27 00:26 UTC, the Civai Nova Blogger Agent MCP server is up with a Glimind reliability score of 73/100 (grade C). Over the last 30 days it answered 98.7% of Glimind's liveness checks. It had 61 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Civai Nova Blogger Agent MCP server provide?

Civai Nova Blogger Agent MCP server advertises 6 tools, including converse, create_draft, list_drafts, post_blog_content, trend_search.

How do I install Civai Nova Blogger Agent MCP server?

Point your MCP client at this streamable-http endpoint: https://nova.civai.co/mcp/agents/blogger-agent

Is the Civai Nova Blogger Agent MCP server safe to connect to an AI agent?

Glimind scanned all 6 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.

Operator of Civai Nova Blogger Agent MCP server?

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.

Feedback
Help us improve