mcp-registry/io.github.rajeswaran140/crowvault · v3.1.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 14:56 UTC, the CrowVault MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 505 hours.
379 tools that generate production-ready Dockerfiles, Kubernetes, Terraform, schemas, APIs, tests.
Point your MCP client at this streamable-http endpoint: https://api.crowvault.ai/mcp
Loading this server's tool list costs an agent ~62,864 tokens before any work — more than 99% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
370 of 370 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 →
370 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 →
496 parameter(s) across 134 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 →
33 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 →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
In the last 30 days: 201 tool(s) removed and 29 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 134 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.rajeswaran140%2Fcrowvault/fixes
{
"name": "add_audit_fields",
"description": "Add audit trail columns (created_by, updated_by, version) to an existing schema",
"inputSchema": {
"type": "object",
"required": [
"table",
"database"
],
"properties": {
"table": {
"type": "string",
"description": "Target table name"
},
"database": {
"enum": [
"postgresql",
"mysql",
"mongodb",
"sqlite"
],
"type": "string",
"description": "Target database"
},
"withVersion": {
"type": "boolean",
"description": "Add optimistic locking version column"
},
"withUserTracking": {
"type": "boolean",
"description": "Add created_by / updated_by columns"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "build_repository_query",
"description": "Generate a type-safe repository query with filtering, pagination, and sorting",
"inputSchema": {
"type": "object",
"required": [
"aggregate",
"operation",
"database",
"orm"
],
"properties": {
"orm": {
"enum": [
"prisma",
"typeorm",
"mongoose",
"knex",
"raw"
],
"type": "string",
"description": "ORM/query builder"
},
"database": {
"enum": [
"postgresql",
"mysql",
"mongodb",
"sqlite"
],
"type": "string",
"description": "Target database"
},
"aggregate": {
"type": "string",
"description": "Aggregate/entity name"
},
"operation": {
"enum": [
"findById",
"findAll",
"findByFilter",
"count",
"exists"
],
"type": "string",
"description": "Query operation"
},
"withPagination": {
"type": "boolean",
"description": "Add limit/offset pagination"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "convert_schema",
"description": "Convert a schema definition between database dialects (e.g. PostgreSQL → MySQL)",
"inputSchema": {
"type": "object",
"required": [
"schema",
"fromDatabase",
"toDatabase"
],
"properties": {
"schema": {
"type": "string",
"description": "Source DDL or schema description"
},
"toDatabase": {
"enum": [
"postgresql",
"mysql",
"mongodb",
"sqlite"
],
"type": "string",
"description": "Target dialect"
},
"fromDatabase": {
"enum": [
"postgresql",
"mysql",
"mongodb",
"sqlite"
],
"type": "string",
"description": "Source dialect"
}
}
},
"annotations": {
"readOnlyHint": true
}
}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/io.github.rajeswaran140/crowvault"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.rajeswaran140/crowvault"}) over MCP.
generate_db_integration_test ~361 tokensgenerate_api_integration_test ~356 tokensdesign_schema ~342 tokensgenerate_property_test ~336 tokensgenerate_openapi_spec ~331 tokensStatic 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fio.github.rajeswaran140%2Fcrowvault?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.rajeswaran140%2Fcrowvault?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fio.github.rajeswaran140%2Fcrowvault.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0d3ae7fe009b7c13…, first seen 2026-11-22, included at leaf 384035 of 384,087. Version history · verify what your client received.
Compare: most reliable data servers · most reliable testing servers · most reliable code servers · most reliable database servers · most reliable devops servers
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.
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"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 14:56 UTC, the CrowVault MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 505 hours.
CrowVault MCP server advertises 300+ tools, including add_audit_fields, api_test_generator, apply_design_pattern, apply_domain_template, apply_solid_principles.
Point your MCP client at this streamable-http endpoint: https://api.crowvault.ai/mcp
Glimind scanned all 370 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.
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.