mcp-registry/rs.monit/monit-rs · v0.2.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 16:28 UTC, the monit.rs MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Schema-aware API monitoring: diff OpenAPI specs for breaking changes, manage endpoints.
Point your MCP client at this streamable-http endpoint: https://monit.rs/integrations/mcp
22 of 22 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 →
34 parameter(s) across 17 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 →
5 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 17 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Frs.monit%2Fmonit-rs/fixes
{
"name": "create_alert_channel",
"description": "Create an alert channel. Pass EXACTLY one of email_address /\n webhook_url / pagerduty_routing_key matching the channel_type:\n\n - channel_type='email' → email_address='[email protected]'\n - channel_type='webhook' → webhook_url='https://your-endpoint'\n - channel_type='slack' → webhook_url='https://hooks.slack.com/...'\n - channel_type='pagerduty' → pagerduty_routing_key='<Events v2 key>'\n ",
"inputSchema": {
"type": "object",
"title": "create_alert_channelArguments",
"required": [
"channel_type"
],
"properties": {
"webhook_url": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Webhook Url",
"default": null
},
"channel_type": {
"enum": [
"email",
"webhook",
"slack",
"pagerduty"
],
"type": "string",
"title": "Channel Type"
},
"min_severity": {
"enum": [
"critical",
"high",
"medium",
"low",
"info"
],
"type": "string",
"title": "Min Severity",
"default": "medium"
},
"email_address": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Email Address",
"default": null
},
"pagerduty_routing_key": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Pagerduty Routing Key",
"default": null
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_endpoint",
"description": "Create a new monitored endpoint. Respects your tier's max_endpoints cap.",
"inputSchema": {
"type": "object",
"title": "create_endpointArguments",
"required": [
"name",
"url"
],
"properties": {
"url": {
"type": "string",
"title": "Url"
},
"name": {
"type": "string",
"title": "Name"
},
"method": {
"type": "string",
"title": "Method",
"default": "GET"
},
"interval_seconds": {
"type": "integer",
"title": "Interval Seconds",
"default": 900
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "create_status_page",
"description": "Create a public status page at https://<slug>.status.monit.rs.\n Add endpoints to it via the dashboard or the HTTP API (adding\n endpoints from chat is deliberately not exposed — the mapping is\n fiddly and easy to get wrong).",
"inputSchema": {
"type": "object",
"title": "create_status_pageArguments",
"required": [
"slug",
"title"
],
"properties": {
"slug": {
"type": "string",
"title": "Slug"
},
"title": {
"type": "string",
"title": "Title"
},
"description": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Description",
"default": null
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/rs.monit/monit-rs"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/rs.monit/monit-rs"}) over MCP.
create_alert_channel ~316 tokensdelete_endpoint ~239 tokensopenapi_diff ~211 tokensset_endpoint_assertions ~191 tokenscreate_status_page ~160 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%2Frs.monit%2Fmonit-rs?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Frs.monit%2Fmonit-rs?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Frs.monit%2Fmonit-rs.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:268f8cc09c87d6a7…, first seen 2026-11-17, included at leaf 319611 of 384,622. Version history · verify what your client received.
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 16:28 UTC, the monit.rs MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
monit.rs MCP server advertises 22 tools, including acknowledge_incident, create_alert_channel, create_endpoint, create_status_page, delete_endpoint.
Point your MCP client at this streamable-http endpoint: https://monit.rs/integrations/mcp
Glimind scanned all 22 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.