Is the SolidInvoice MCP server down?

mcp-registry/co.solidinvoice/mcp · registry v3.1.3 · server reports v3.2.0-dev

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 17:08 UTC · handshake 780ms

As of 2026-11-22 17:08 UTC, the SolidInvoice MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
99.5%
checks observed
969
outages (90d)
11
tools
41

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

Point your MCP client at this streamable-http endpoint: https://solidinvoice.app/_mcp

Agent-readiness: C (77/100)

C (77/100): 0 error(s), 3 warning(s) across 41 tool(s); ~5,708 tokens of tool definitions.
Scores higher than 19% of 27,660 MCP servers Glimind has audited.
Its tool list costs an agent ~5,708 tokens per session — more than 70% of servers.
76 → 77 since 2026-11-09
no tool-poisoning patterns
Descriptions100
Safety hints0
Schemas100
Protocol100
Stability100
Token cost75
Reliability100
Client compatibility70

What to fix (4)

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: add_client_tax_identifier, add_contact, apply_invoice_transition, apply_quote_transition, apply_recurring_transition 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 →

14 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_invoice, create_product, create_quote, create_recurring_invoice, create_resource and 9 more

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: 36 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%2Fco.solidinvoice%2Fmcp/fixes

add_client_tax_identifier 1 change
{
  "name": "add_client_tax_identifier",
  "description": "Add a tax identifier (VAT, GSTIN, TIN, ABN, CNPJ, TRN, Other) to a client.",
  "inputSchema": {
    "type": "object",
    "required": [
      "client_id",
      "label",
      "value"
    ],
    "properties": {
      "label": {
        "type": "string",
        "description": "Identifier label (e.g. \"VAT\", \"GSTIN\", \"TIN\", \"ABN\", \"CNPJ\", \"TRN\", \"Other\")"
      },
      "value": {
        "type": "string",
        "description": "Identifier value"
      },
      "primary": {
        "type": "boolean",
        "default": false,
        "description": "Whether this is the primary identifier for the client"
      },
      "client_id": {
        "type": "string",
        "description": "Client ULID"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
add_contact 1 change
{
  "name": "add_contact",
  "description": "Add a new contact (email + optional name) to an existing client.",
  "inputSchema": {
    "type": "object",
    "required": [
      "client_id",
      "email"
    ],
    "properties": {
      "email": {
        "type": "string",
        "description": "Contact email (required, must be valid)"
      },
      "client_id": {
        "type": "string",
        "description": "Client ULID"
      },
      "last_name": {
        "type": [
          "null",
          "string"
        ],
        "default": null,
        "description": "Contact last name"
      },
      "first_name": {
        "type": [
          "null",
          "string"
        ],
        "default": null,
        "description": "Contact first name"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
convert_quote_to_invoice 1 change
{
  "name": "convert_quote_to_invoice",
  "description": "Convert a quote into a new invoice, copying client, line items, and totals.",
  "inputSchema": {
    "type": "object",
    "required": [
      "quote_id"
    ],
    "properties": {
      "quote_id": {
        "type": "string",
        "description": "Quote ULID"
      }
    }
  },
  "annotations": {
    "readOnlyHint": 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/co.solidinvoice/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/co.solidinvoice/mcp"}) 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.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fco.solidinvoice%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fco.solidinvoice%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fco.solidinvoice%2Fmcp?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fco.solidinvoice%2Fmcp.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ccf0cd03604bfe0b…, first seen 2026-11-21, included at leaf 374694 of 384,675. Version history · verify what your client received.

Tools (41)

Compare: 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?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the SolidInvoice MCP server down right now?

As of 2026-11-22 17:08 UTC, the SolidInvoice MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 6 minutes.

How many tools does SolidInvoice MCP server provide?

SolidInvoice MCP server advertises 41 tools, including add_client_tax_identifier, add_contact, apply_invoice_transition, apply_quote_transition, apply_recurring_transition.

How do I install SolidInvoice MCP server?

Point your MCP client at this streamable-http endpoint: https://solidinvoice.app/_mcp

Is the SolidInvoice 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 SolidInvoice 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