Is the Laxis Tech Laxis MCP server down?

mcp-registry/io.github.laxis-tech/laxis-mcp · v1.28.1

Also listed as glama/laxis-tech/laxis-mcp-server

As of 2026-10-26 17:58 UTC, the Laxis Tech Laxis MCP server is up (it requires sign-in) with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

Search and read your Laxis meeting transcripts, AI summaries, and participants from Claude.

Point your MCP client at this streamable-http endpoint: https://app.laxis.tech/mcp

Agent-readiness: C (71/100)

What to fix (4)

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.laxis-tech%2Flaxis-mcp/fixes

{
  "name": "get_meeting",
  "description": "Get one meeting's details: title, date, participants, keywords, and summary.\n\n    Does NOT include the transcript text — use get_transcript for that, or\n    search_meetings to find the relevant part of a long meeting. If the meeting is\n    plan-restricted, returns {accessible: false, needs_upgrade: true, reason,\n    upgrade_url}; tell the user it needs a Laxis plan upgrade and share upgrade_url\n    so they can upgrade, rather than treating it as an error.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "get_meetingArguments",
    "required": [
      "meeting_id"
    ],
    "properties": {
      "meeting_id": {
        "type": "string",
        "title": "Meeting Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_transcript",
  "description": "Read a meeting's transcript as '[m:ss] Speaker: text' lines, paginated.\n\n    Returns at most max_chars characters starting at offset; if next_offset is\n    not null, call again with offset=next_offset for the next page. Use this\n    only when you need to read the actual conversation — for locating a topic\n    inside meetings, search_meetings is much cheaper. If the meeting is\n    plan-restricted, returns {accessible: false, needs_upgrade: true, reason,\n    upgrade_url, transcript: null}; tell th",
  "inputSchema": {
    "type": "object",
    "title": "get_transcriptArguments",
    "required": [
      "meeting_id"
    ],
    "properties": {
      "offset": {
        "type": "integer",
        "title": "Offset",
        "default": 0
      },
      "max_chars": {
        "type": "integer",
        "title": "Max Chars",
        "default": 16000
      },
      "meeting_id": {
        "type": "string",
        "title": "Meeting Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "list_meetings",
  "description": "List the user's meetings, newest first (id, title, date, duration, short summary).\n\n    Call this when the user asks about their meetings (\"what meetings did I have\n    last week?\") or when you need a meeting_id for get_meeting / get_transcript\n    and don't have one. For content questions (\"what did we say about pricing?\"),\n    prefer search_meetings.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "list_meetingsArguments",
    "properties": {
      "page": {
        "type": "integer",
        "title": "Page",
        "default": 1
      },
      "page_size": {
        "type": "integer",
        "title": "Page Size",
        "default": 10
      }
    }
  },
  "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.laxis-tech/laxis-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.laxis-tech/laxis-mcp"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~871 tokens).
• Tool names are unique and portable across clients.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• search_meetings ~285 tokens
• get_transcript ~232 tokens
• get_meeting ~185 tokens
• list_meetings ~169 tokens

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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.laxis-tech%2Flaxis-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.laxis-tech%2Flaxis-mcp?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.laxis-tech%2Flaxis-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.laxis-tech%2Flaxis-mcp.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.laxis-tech%2Flaxis-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.laxis-tech%2Flaxis-mcp?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:f73e0698e0fc2d02…, first seen 2026-10-17, included at leaf 15744 of 74,588. Version history · verify what your client received.

Tools (4)

• get_meeting
• get_transcript
• list_meetings
• search_meetings

Compare: most reliable database servers · most reliable files servers · most reliable search servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Laxis Tech Laxis MCP server down right now?

As of 2026-10-26 17:58 UTC, the Laxis Tech Laxis MCP server is up (it requires sign-in) with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Laxis Tech Laxis MCP server provide?

Laxis Tech Laxis MCP server advertises 4 tools, including get_meeting, get_transcript, list_meetings, search_meetings.

How do I install Laxis Tech Laxis MCP server?

Point your MCP client at this streamable-http endpoint: https://app.laxis.tech/mcp

Is the Laxis Tech Laxis MCP server safe to connect to an AI agent?

Glimind scanned all 4 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 Laxis Tech Laxis 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.