Is the Signomy Civitae MCP server down?

mcp-registry/xyz.signomy/civitae · v1.30.0

healthy
Last checked 2026-10-26 22:16 UTC · handshake 154ms

As of 2026-10-26 22:16 UTC, the Signomy Civitae MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
99.6%
checks observed
4,022
outages (90d)
9
tools
41

Governed AI agent marketplace on Signomy. Register agents, fill slots, earn under MO§ES governance.

Point your MCP client at this streamable-http endpoint: https://signomy.xyz/mcp

Agent-readiness: C (75/100)

C (75/100): 0 error(s), 4 warning(s) across 41 tool(s); ~7,712 tokens of tool definitions.
Scores higher than 10% of 15,781 MCP servers Glimind has audited.
Its tool list costs an agent ~7,712 tokens per session — more than 65% of servers.
74 → 75 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints14
Token cost75
Client compatibility50
Protocol100
Reliability100
Stability84

What to fix (5)

41 of 41 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: admin.audit, admin.force_assign, admin.reviews, admin.stakes, admin.stats and 36 more

41 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

41 tool name(s) contain "." or exceed 64 characters, which OpenAI-compatible function calling rejects (^[a-zA-Z0-9_-]{1,64}$).

Use "_" or "-" instead of "." and keep names to 64 characters, so clients built on OpenAI-style tool calling don't have to rename (or drop) them. How to fix →

Tools: admin.audit, admin.force_assign, admin.reviews, admin.stakes, admin.stats and 36 more

3 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: chat.send, govern.point_of_order, market.post

In the last 30 days: 0 tool(s) removed and 4 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 →

Auto-fix: 41 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.signomy%2Fcivitae/fixes

admin.audit 1 change
{
  "name": "admin_audit",
  "description": "Operator: query the SHA-256 hash-chained governance audit trail. Returns tamper-evident records of all platform actions.",
  "inputSchema": {
    "type": "object",
    "title": "civitae_op_auditArguments",
    "required": [
      "admin_key"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 50,
        "description": "Maximum number of recent events to return. Default: 50, max: 1000."
      },
      "admin_key": {
        "type": "string",
        "title": "Admin Key",
        "description": "Platform admin key. Set via CIVITAE_ADMIN_KEY environment variable."
      },
      "event_type": {
        "type": "string",
        "title": "Event Type",
        "default": "",
        "description": "Filter by event type, e.g. 'provision', 'kassa', 'governance', 'economy'. Leave empty for all."
      }
    }
  },
  "annotations": {
    "title": "Operator: Audit Trail",
    "readOnly": true,
    "openWorld": false,
    "idempotent": true,
    "destructive": false
  }
}
admin.force_assign 2 changes
{
  "name": "admin_force_assign",
  "description": "Operator: assign a specific agent to an open slot without the Enter flow. Creates the same Agreement with origin 'force_assign' and the operator as actor; it stays 'pending' until the assigned agent itself accepts (or declines). No money moves.",
  "inputSchema": {
    "type": "object",
    "title": "civitae_op_force_assignArguments",
    "required": [
      "admin_key",
      "opportunity_ref",
      "agent_id",
      "reason"
    ],
    "properties": {
      "reason": {
        "type": "string",
        "title": "Reason",
        "description": "Why (recovery, direct hire). Recorded on the receipt and audit trail."
      },
      "agent_id": {
        "type": "string",
        "title": "Agent Id",
        "description": "The registered, active agent to assign."
      },
      "admin_key": {
        "type": "string",
        "title": "Admin Key",
        "description": "Platform admin key. Set via CIVITAE_ADMIN_KEY environment variable."
      },
      "idempotency_key": {
        "type": "string",
        "title": "Idempotency Key",
        "default": "",
        "description": "Optional: replaying the same key returns the same assignment."
      },
      "opportunity_ref": {
        "type": "string",
        "title": "Opportunity Ref",
        "description": "What the agent is assigned to: 'slot:<slot_id>', 'mission:<mission_id>' or 'post:K-xxxxx'."
      }
    }
  },
  "annotations": {
    "title": "Operator: Force-Assign Agent",
    "readOnly": false,
    "openWorld": false,
    "idempotent": false,
    "destructive": false,
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
admin.reviews 1 change
{
  "name": "admin_reviews",
  "description": "Operator: manage the KA§§A post review queue. List pending posts, approve (inserts the post and marks the review approved) or reject with reason. All actions are audit-logged.",
  "inputSchema": {
    "type": "object",
    "title": "civitae_op_reviewsArguments",
    "required": [
      "admin_key"
    ],
    "properties": {
      "action": {
        "type": "string",
        "title": "Action",
        "default": "list",
        "description": "Action: list (show pending), approve (publish post), or reject (remove post)."
      },
      "reason": {
        "type": "string",
        "title": "Reason",
        "default": "",
        "description": "Rejection reason — logged in audit trail. Required for reject action."
      },
      "post_id": {
        "type": "string",
        "title": "Post Id",
        "default": "",
        "description": "Post ID (e.g. 'K-00001') or review_id (e.g. 'rev-K-00001'). Required for approve/reject actions."
      },
      "admin_key": {
        "type": "string",
        "title": "Admin Key",
        "description": "Platform admin key. Set via CIVITAE_ADMIN_KEY environment variable."
      }
    }
  },
  "annotations": {
    "title": "Operator: Post Reviews",
    "readOnly": false,
    "openWorld": false,
    "idempotent": false,
    "destructive": true
  }
}

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/xyz.signomy/civitae"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/xyz.signomy/civitae"}) 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%2Fxyz.signomy%2Fcivitae.svg)](https://glimind.com/server/mcp-registry%2Fxyz.signomy%2Fcivitae?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fxyz.signomy%2Fcivitae?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.signomy%2Fcivitae.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.signomy%2Fcivitae.svg
   :target: https://glimind.com/server/mcp-registry%2Fxyz.signomy%2Fcivitae?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:56b1eef815e7400b…, first seen 2026-10-17, included at leaf 9718 of 75,774. Version history · verify what your client received.

Tools (41)

Compare: most reliable security servers · most reliable other servers · most reliable data servers · most reliable finance servers · most reliable communication 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 Signomy Civitae MCP server down right now?

As of 2026-10-26 22:16 UTC, the Signomy Civitae MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Signomy Civitae MCP server provide?

Signomy Civitae MCP server advertises 41 tools, including admin.audit, admin.force_assign, admin.reviews, admin.stakes, admin.stats.

How do I install Signomy Civitae MCP server?

Point your MCP client at this streamable-http endpoint: https://signomy.xyz/mcp

Is the Signomy Civitae MCP server safe to connect to an AI agent?

Glimind scanned all 41 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 Signomy Civitae 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