Is the Llmse MCP server down?

mcp-registry/ai.llmse/mcp · v1.25.0

healthy
Last checked 2026-10-26 23:43 UTC · handshake 278ms

As of 2026-10-26 23:43 UTC, the Llmse MCP server is up with a Glimind reliability score of 66/100 (grade C). Over the last 30 days it answered 97.7% of Glimind's liveness checks. It had 127 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
97.7%
checks observed
4,933
outages (90d)
127
tools
10

Public MCP server for the LLM Search Engine

Point your MCP client at this streamable-http endpoint: https://llmse.ai/mcp

Agent-readiness: C (73/100)

C (73/100): 0 error(s), 3 warning(s) across 10 tool(s); ~2,188 tokens of tool definitions.
Scores higher than 8% of 15,780 MCP servers Glimind has audited.
Its tool list costs an agent ~2,188 tokens per session — lighter than 55% of servers.
74 → 73 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability75
Stability100

What to fix (3)

21 parameter(s) across 10 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 →

Tools: analyze_aeo, analyze_eeat, analyze_garm, analyze_readability, analyze_seo and 5 more

10 of 10 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: analyze_aeo, analyze_eeat, analyze_garm, analyze_readability, analyze_seo and 5 more

Reachable 97.7% of the time over the last 30 days; median recovery 2 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

Auto-fix: 7 corrected tool definitions

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

analyze_aeo 1 change
{
  "name": "analyze_aeo",
  "description": "Analyze how well content is optimized for AI answer engines.\n\n    Evaluates content for AI answer engines (ChatGPT, Perplexity, Gemini, Claude).\n    Combines Q&A pattern detection, snippet extractability, and entity clarity\n    analysis with a full Citation Readiness assessment.\n\n    AEO Scoring Framework (100 points):\n    - Answer Format Detection: 30 points (Q&A extractability patterns)\n    - FAQ Schema Presence: 20 points (FAQPage schema markup)\n    - HowTo Schema Presence: 15 points (HowTo s",
  "inputSchema": {
    "type": "object",
    "title": "analyze_aeoArguments",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "title": "Url"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
analyze_eeat 1 change
{
  "name": "analyze_eeat",
  "description": "Analyze a website URL for E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness).\n\n    Evaluates content quality signals based on Google's Search Quality Rater Guidelines\n    and \"Creating helpful content\" documentation. Detects EEAT signals including:\n    - Experience: First-person language, case studies, testimonials, years of experience\n    - Expertise: Author credentials, certifications, professional memberships, topic depth\n    - Authoritativeness: Organization schema, awards, ",
  "inputSchema": {
    "type": "object",
    "title": "analyze_eeatArguments",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "title": "Url"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
analyze_garm 1 change
{
  "name": "analyze_garm",
  "description": "Compute GARM brand safety score for a website or category.\n\n    Based on the GARM (Global Alliance for Responsible Media) Brand Suitability\n    Framework. Maps content categories to 11 GARM sensitive content categories\n    with risk levels (Floor, High, Medium, Low).\n\n    Can either:\n    1. Provide a URL - classification will be fetched and mapped to GARM\n    2. Provide category and sentiment directly for instant scoring\n\n    Score interpretation: higher = safer for advertising.\n    Floor catego",
  "inputSchema": {
    "type": "object",
    "title": "analyze_garmArguments",
    "properties": {
      "url": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Url",
        "default": null
      },
      "category": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Category",
        "default": null
      },
      "sentiment": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Sentiment",
        "default": null
      }
    }
  },
  "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/ai.llmse/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.llmse/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. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.llmse%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fai.llmse%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.llmse%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.llmse%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.llmse%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.llmse%2Fmcp?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:8bd26501c7cf58e0…, first seen 2026-10-17, included at leaf 15113 of 76,136. Version history · verify what your client received.

Tools (10)

Compare: most reliable web servers · most reliable ml servers · most reliable search servers · most reliable advertising 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 Llmse MCP server down right now?

As of 2026-10-26 23:43 UTC, the Llmse MCP server is up with a Glimind reliability score of 66/100 (grade C). Over the last 30 days it answered 97.7% of Glimind's liveness checks. It had 127 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Llmse MCP server provide?

Llmse MCP server advertises 10 tools, including analyze_aeo, analyze_eeat, analyze_garm, analyze_readability, analyze_seo.

How do I install Llmse MCP server?

Point your MCP client at this streamable-http endpoint: https://llmse.ai/mcp

Is the Llmse MCP server safe to connect to an AI agent?

Glimind scanned all 10 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 Llmse 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