Is the Skewing1 Insurelink MCP server down?

mcp-registry/io.github.skewing1/insurelink · v1.0.0

healthy
Last checked 2026-10-21 17:27 UTC · handshake 868ms

As of 2026-10-21 17:27 UTC, the Skewing1 Insurelink MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 3 minutes.

uptime (30d checks)
100%
checks observed
4,185
outages (90d)
20
tools
32

AI agent-to-agent SLA agreements on Base with insurance, reputation, and x402 payments.

Install Skewing1 Insurelink MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http skewing1-insurelink-mcp-server https://ivnmscuuljqubunqcgkh.supabase.co/functions/v1/mcp-server/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "skewing1-insurelink-mcp-server": {
      "type": "http",
      "url": "https://ivnmscuuljqubunqcgkh.supabase.co/functions/v1/mcp-server/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (81/100)

B (81/100): 0 error(s), 3 warning(s) across 32 tool(s); ~7,134 tokens of tool definitions.
Scores higher than 36% of 15,472 MCP servers Glimind has audited.
Its tool list costs an agent ~7,134 tokens per session — more than 65% of servers.
81 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints15
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (4)

32 of 32 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: attest_reputation, check_agent_insurance, claim_breach_credit, discover_capabilities, early_exit and 27 more

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: insurelink_charge, pay_then_call

Handshake + tools/list takes ~1,859 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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: 15 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%2Fio.github.skewing1%2Finsurelink/fixes

check_agent_insurance 1 change
{
  "name": "check_agent_insurance",
  "description": "Checks whether an AI agent / wallet has active insurance coverage on InsureLink, including tier, caps, expiry, and covered events. Free. Standard HTTPS + JSON via the agent-assurance REST module.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "agent_id"
    ],
    "properties": {
      "agent_id": {
        "type": "string",
        "pattern": "^0x[a-fA-F0-9]{40}$",
        "description": "Agent / wallet address (0x...)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_activity 1 change
{
  "name": "get_activity",
  "description": "Returns recent platform transactions.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "limit": {
        "type": "number",
        "description": "Max transactions (default 50, max 200)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_agent_claim_history 1 change
{
  "name": "get_agent_claim_history",
  "description": "Returns recent insurance claim history for an AI agent / wallet on InsureLink, including filed, approved, partial, and denied claims. Free.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "agent_id"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1,
        "description": "Max claims to return. Default 25."
      },
      "agent_id": {
        "type": "string",
        "pattern": "^0x[a-fA-F0-9]{40}$",
        "description": "Agent / wallet address (0x...)"
      }
    },
    "additionalProperties": false
  },
  "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/io.github.skewing1/insurelink"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.skewing1/insurelink"}) 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%2Fio.github.skewing1%2Finsurelink.svg)](https://glimind.com/server/mcp-registry%2Fio.github.skewing1%2Finsurelink?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.skewing1%2Finsurelink?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.skewing1%2Finsurelink.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.skewing1%2Finsurelink.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.skewing1%2Finsurelink?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:63057fa172b831f6…, first seen 2026-10-17, included at leaf 15034 of 40,720. Version history · verify what your client received.

Tools (32)

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

As of 2026-10-21 17:27 UTC, the Skewing1 Insurelink MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Skewing1 Insurelink MCP server provide?

Skewing1 Insurelink MCP server advertises 32 tools, including attest_reputation, check_agent_insurance, claim_breach_credit, discover_capabilities, early_exit.

How do I install Skewing1 Insurelink MCP server?

Point your MCP client at this streamable-http endpoint: https://ivnmscuuljqubunqcgkh.supabase.co/functions/v1/mcp-server/mcp

Is the Skewing1 Insurelink MCP server safe to connect to an AI agent?

Glimind scanned all 32 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 Skewing1 Insurelink 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