← Back to search
ai.llmse/mcp

ai.llmse/mcp

Public MCP server for the LLM Search Engine

DECISION SUMMARY

Block For Production

Score
n/a
Rank suppressed while production readiness shows a blocking verdict.
Confidence
High
Based on evidence completeness, recency, and validation density.
Evidence age
4.7h old
Freshness: fresh. Snapshot trustsnap_d9c9a70bbe2132d5.
Top risk drivers
  • Utility Coverage
  • Trust Confidence
  • Tool Surface Design
Recommended actions
  • Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
  • Fix the failing checks first, then revalidate to confirm the recovery path.
  • Compare tool enumeration outputs between runs and remove non-deterministic behavior.
Next action
revalidate, add safeguards, export policy
failing live status
Compare alternatives Export policy Open report JSON Dispute this assessment
Observed Attention
Low observed attention
AI discovery detected. This MCP server has recently appeared in AI-assisted discovery or evaluation traffic on Verify.
  • AI crawler activity
  • Search crawler activity
  • profile inspection
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Claim this profile to control the metadata agents are reading and publish verified ownership, security contact, policy metadata, badge status, and Intelligence API fields.
Status
Failing
Score
n/a
Transport
streamable-http
Tools
0
DISPUTE THIS ASSESSMENT

Dispute this assessment

If any published claim about this server -- its score, a risk flag, a capability classification, or its taxonomy -- is factually wrong, tell us what evidence shows and we will review it. This does not require claiming or verifying ownership of the server first.

Verify responds to disputes within 5 business days and resolves them within 15.

Dispute history

No disputes filed for this server.

Risk

Security posture
Tools analyzed
0
High-risk tools
0
Destructive tools
0
Exec tools
0
Egress tools
0
Secret tools
0
Bulk-access tools
0
Risk distribution
none
Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance
Governance status
Not_Assessed
Safe to publish
Auth boundary
public_or_unclear
Blast radius
Low
High-risk tools
0
Confirmation signals
none
Safeguard count
0

Status detail: No write-action governance evidence is available yet.

ToolRiskFlagsSafeguards
No high-risk tools were detected on the latest run.
Action-controls diff

Need at least two validation runs before diffing action controls.

Critical alerts
High/critical-severity alerts
0
Production verdicts degrade quickly when high or critical-severity alerts are active.

Compatibility

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Partially client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.; OAuth interoperability should be strong.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listError
  • transport_compliance_probeWarning
  • step_up_auth_probeMissing
  • connector_replay_probeMissing — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Partially client-compatible
tools/list must succeed.; A useful Claude integration needs at least one exposed tool.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listError
  • transport_compliance_probeWarning
Write-action publishing
Publishing blocked
Active alert(s) affecting production readiness: Latest validation is failing, tools/list regressed, Auth mode changed.
Confidence: high (77.5)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeNot_Assessed
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: high (77.5)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeMissing
  • connector_replay_probeMissing
Client compatibility gate details
ChatGPT custom connector
Partially client-compatible
Remediation checklist
  • OpenAI connectors expect OAuth for remote server auth.
  • Dynamic client registration materially improves connector setup.
  • tools/list must succeed.
  • OAuth interoperability should be strong.
  • The tool surface is not limited to search/fetch-style read tools.
  • OAuth is not configured, so this client cannot authenticate without additional setup.
Claude remote MCP
Partially client-compatible
Remediation checklist
  • tools/list must succeed.
  • A useful Claude integration needs at least one exposed tool.
  • The tool surface is not limited to search/fetch-style read tools.
  • OAuth is not configured, so this client cannot authenticate without additional setup.
  • Not yet safe for company-knowledge use: requires a search/fetch-only surface with no export, bulk, mutating, or high-blast-radius exposure.
  • Not yet safe for the Messages API remote MCP path: requires OAuth, a compatible connector profile, and no pending connector-refresh risk.
Write-safe publishing
Blocked
Remediation checklist
  • Add a clearer auth boundary around risky write actions.
  • Add confirmation or dry-run semantics for risky actions.
  • Production readiness is blocked by an active alert: Latest validation is failing.
  • Production readiness is blocked by an active alert: tools/list regressed.
  • Production readiness is blocked by an active alert: Auth mode changed.
Verdict traces
Production verdict
Metadata only
No live validation evidence exists yet for this entry.
Confidence: high (77.5)
Winning source: live_validation
Triggering alerts
  • server_failing • critical • Latest validation is failing
  • tools_list_regressed • critical • tools/list regressed
  • auth_mode_changed • high • Auth mode changed
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partially client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Partially client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing blocked action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none
Publishability policy profiles
ChatGPT custom connector compatibility
Compatible with review
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.; OAuth interoperability should be strong. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Compatible with review
tools/list must succeed.; A useful Claude integration needs at least one exposed tool. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: No
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Compatibility fixtures
ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.; OAuth interoperability should be strong.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
tools/list must succeed.; A useful Claude integration needs at least one exposed tool.
  • remote_transport: Passes
  • tool_discovery: Likely to fail
  • auth_connect: Passes
  • safe_write_review: Degraded
Recommended for

No recommendation profile is available yet.

Evidence

Current trust snapshot
Snapshot ID
trustsnap_d9c9a70bbe2132d5
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Aug 08, 2026 12:02:14 AM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Aug 07, 2026 07:18:30 PM UTC
Age: 4.73h • evidence age tier: Verified in last 24h • display score: suppressed

Canonical machine links

Evidence confidence
Confidence score
77.5
Based on 10 recent validations, 27 captured checks, and validation age of 4.7 hours.
Live checks captured
27
More direct checks increase trust in the current verdict.
Validation age
4.7h
Lower age means fresher evidence.
Latest validation evidence
Latest summary
Failing
Validation profile
remote_mcp
Started
Aug 07, 2026 07:18:29 PM UTC
Latency
1347.6 ms

Failures

  • oauth_authorization_server no authorization server
  • oauth_protected_resource Client error '403 Forbidden' for url 'https://llmse.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403
  • openid_configuration no authorization server
  • server_card Client error '403 Forbidden' for url 'https://llmse.ai/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403
  • tools_list Client error '400 Bad Request' for url 'https://llmse.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400

Checks

CheckStatusLatencyEvidence
action_safety_probe Not_Assessed n/a No write-action risk evidence recorded.
advanced_capabilities_probe Missing n/a No advanced MCP capability signals detected.
connector_publishability_probe Error n/a Publishability blockers: tools list, action safety, server card, tool surface.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe Missing n/a tools list unavailable
initialize OK 153.5 ms Protocol 2025-03-26
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 79.5 ms Client error '403 Forbidden' for url 'https://llmse.ai/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403
official_registry_probe OK n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 256.6 ms Fetched https://llmse.ai/robots.txt
prompt_get Missing n/a not advertised
prompts_list Missing 167.0 ms Client error '400 Bad Request' for url 'https://llmse.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
protocol_version_probe Warning n/a Claims 2025-03-26; 2 release(s) behind 2025-11-25.
provenance_divergence_probe Not_Assessed n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a not advertised
resources_list Missing 168.3 ms Client error '400 Bad Request' for url 'https://llmse.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
schema_divergence_probe Missing n/a no server card tools
server_card Error 23.9 ms Client error '403 Forbidden' for url 'https://llmse.ai/.well-known/mcp/server-card.json' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403
session_resume_probe OK 172.1 ms 10 tool(s) exposed
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe Missing n/a no tools
tools_list Error 123.8 ms Client error '400 Bad Request' for url 'https://llmse.ai/mcp' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
transport_compliance_probe Warning 106.0 ms Issues: missing protocol header (bad protocol=400, DELETE=200, expired session=404).
utility_coverage_probe Missing 35.2 ms No completions evidence; no pagination evidence; tasks missing.
Raw evidence view
Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [],
        "reason": "empty_observation_set",
        "safeguard_count": 0,
        "summary": {
          "annotation_conflict_tools": 0,
          "bulk_access_tools": 0,
          "capability_distribution": {},
          "declared_non_read_only_tools": 0,
          "destructive_tools": 0,
          "egress_tools": 0,
          "exec_tools": 0,
          "has_non_read_capability": false,
          "high_risk_tools": 0,
          "risk_distribution": {
            "critical": 0,
            "high": 0,
            "low": 0,
            "medium": 0
          },
          "secret_tools": 0,
          "tool_count": 0
        }
      },
      "latency_ms": null,
      "status": "not_assessed"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [],
        "enabled_count": 0,
        "initialize_capability_keys": [
          "experimental",
          "prompts",
          "resources",
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "missing"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "tools_list",
          "action_safety",
          "server_card",
          "tool_surface"
        ],
        "criteria": {
          "action_safety": false,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": false,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": false,
          "tools_list": false,
          "transport_compliance": true
        },
        "high_risk_tools": 0,
        "tool_count": 0,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "error"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "reason": "tools_list_unavailable"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "mcp-session-id": "8ef5045c2f2e44ba8e57fe9db33f6978",
          "strict-transport-security": "max-age=2592000"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "experimental": {},
              "prompts": {
                "listChanged": false
              },
              "resources": {
                "listChanged": false,
                "subscribe": false
              },
              "tools": {
                "listChanged": false
              }
            },
            "protocolVersion": "2025-03-26",
            "serverInfo": {
              "name": "LLMSE Public API",
              "version": "1.25.0"
            }
          }
        },
        "url": "https://llmse.ai/mcp"
      },
      "latency_ms": 153.53,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '403 Forbidden' for url 'https://llmse.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403",
        "url": "https://llmse.ai/.well-known/oauth-protected-resource"
      },
      "latency_ms": 79.55,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": true,
        "official_peer_count": 1,
        "registry_identifier": "ai.llmse/mcp",
        "registry_source": "official_registry"
      },
      "latency_ms": null,
      "status": "ok"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=utf-8",
          "strict-transport-security": "max-age=2592000"
        },
        "http_status": 200,
        "url": "https://llmse.ai/robots.txt",
        "validation_disallowed": false
      },
      "latency_ms": 256.62,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "error": "Client error '400 Bad Request' for url 'https://llmse.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "headers": {
          "content-type": "application/json",
          "mcp-session-id": "a85cdfa79b824f58a175d93313801dc9",
          "strict-transport-security": "max-age=2592000"
        },
        "http_status": 400,
        "payload": {},
        "reason": "not_advertised",
        "url": "https://llmse.ai/mcp"
      },
      "latency_ms": 166.96,
      "status": "missing"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2025-03-26",
        "lag_days": 244,
        "latest_known_version": "2025-11-25",
        "releases_behind": 2,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "comparable_field_count": 0,
        "compared_fields": [
          "title",
          "version",
          "homepage",
          "repository"
        ],
        "direct_official_match": true,
        "drift_fields": [],
        "metadata_document_count": 1,
        "readable_sources": [
          "registry"
        ],
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": null,
        "server_card_version": null
      },
      "latency_ms": null,
      "status": "not_assessed"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "not_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "error": "Client error '400 Bad Request' for url 'https://llmse.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "headers": {
          "content-type": "application/json",
          "mcp-session-id": "2d8ee31756f44dda91067e470cf9b494",
          "strict-transport-security": "max-age=2592000"
        },
        "http_status": 400,
        "payload": {},
        "reason": "not_advertised",
        "url": "https://llmse.ai/mcp"
      },
      "latency_ms": 168.35,
      "status": "missing"
    },
    "schema_divergence_probe": {
      "details": {
        "card_server_name": null,
        "compared_dimensions": [
          "server_name",
          "server_version",
          "declared_vs_observed_auth",
          "tool_membership",
          "parameter_names",
          "required_parameters",
          "parameter_types",
          "output_schema_presence"
        ],
        "compared_tool_count": 0,
        "live_server_name": "LLMSE Public API",
        "reason": "no_server_card_tools",
        "server_name_mismatch": false
      },
      "latency_ms": null,
      "status": "missing"
    },
    "server_card": {
      "details": {
        "error": "Client error '403 Forbidden' for url 'https://llmse.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403",
        "url": "https://llmse.ai/.well-known/mcp/server-card.json"
      },
      "latency_ms": 23.88,
      "status": "error"
    },
    "session_resume_probe": {
      "details": {
        "headers": {
          "content-type": "text/event-stream",
          "mcp-session-id": "8ef5045c2f2e44ba8e57fe9db33f6978",
          "strict-transport-security": "max-age=2592000"
        },
        "http_status": 200,
        "payload": {
          "id": 301,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "Classify a website URL into category, subcategory, language, and sentiment.\n\n    Fetches the URL content and uses AI for classification.\n    Results are cached for fast subsequent lookups.\n    Rate limited to 1 request per minute per domain.\n\n    Args:\n        url: The website URL to classify (e.g., \"https://example.com\").\n\n    Returns:\n        Classification result with:\n        - url: The normalized URL\n        - category: Main category (e.g., \"Sports\", \"Technology\")\n        - subcategory: Specific subcategory\n        - language: Detected content language\n        - sentiment: Content sentiment (Good/Neutral/Bad)\n        - age: Target age group (if available)\n        - gender: Target gender (if available)\n        - cached: Whether result was from cache\n    ",
                "inputSchema": {
                  "properties": {
                    "url": {
                      "title": "Url",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "title": "classify_urlArguments",
                  "type": "object"
                },
                "name": "classify_url",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "classify_urlDictOutput",
                  "type": "object"
                }
              },
              {
                "description": "Select the best advertisers based on website demographics.\n\n    Matches advertisers to website content based on classification demographics.\n    Provide either a URL (classification will be fetched) or demographics directly.\n    Rate limited to 1 request per minute per domain when using URL.\n\n    Scoring weights:\n    - Category match: +10 points\n    - Age match: +5 points\n    - Gender match: +3 points\n    - Sentiment match: +2 points\n    - Higher CPM bid as tiebreaker\n\n    Args:\n        url: URL to match advertisers for (fetches classification from cache).\n        category: Target category (e.g., \"Sports\", \"Automotive\").\n        subcategory: Target subcategory.\n        age: Target age group (e.g., \"18-24\", \"25-34\", \"31-51\").\n        gender: Target gender (\"male\", \"female\", or \"all\").\n        sentiment: Content sentiment (\"Good\", \"Neutral\", or \"Bad\").\n        limit: Number of advertisers to return (1-10, default 3).\n        min_cpm: Minimum CPM cost filter (e.g., 5.0 for $5+ CPM).\n        max_cpm: Maximum CPM cost filter (e.g., 10.0 for $10 or less CPM).\n\n    Returns:\n        Dictionary with:\n        - matches: List of matched advertisers with scores\n        - match_count: Number of matches found\n        - classification: URL classification (if URL provided)\n        - demographics: Provided demographics (if no URL)\n    ",
                "inputSchema": {
                  "properties": {
                    "age": {
                      "anyOf": [
                        {
                          "type": "string"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Age"
                    },
                    "category": {
                      "anyOf": [
                        {
                          "type": "string"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Category"
                    },
                    "gender": {
                      "anyOf": [
                        {
                          "type": "string"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Gender"
                    },
                    "limit": {
                      "default": 3,
                      "title": "Limit",
                      "type": "integer"
                    },
                    "max_cpm": {
                      "anyOf": [
                        {
                          "type": "number"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Max Cpm"
                    },
                    "min_cpm": {
                      "anyOf": [
                        {
                          "type": "number"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Min Cpm"
                    },
                    "sentiment": {
                      "anyOf": [
                        {
                          "type": "string"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Sentiment"
                    },
                    "subcategory": {
                      "anyOf": [
                        {
                          "type": "string"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Subcategory"
                    },
                    "url": {
                      "anyOf": [
                        {
                          "type": "string"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Url"
                    }
                  },
                  "title": "select_advertiserArguments",
                  "type": "object"
                },
                "name": "select_advertiser",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "select_advertiserDictOutput",
                  "type": "object"
                }
              },
              {
                "description": "Analyze a website URL for SEO optimizations.\n\n    Fetches the URL content and analyzes HTML for possible SEO improvements.\n    Results are cached for fast subsequent lookups.\n    Rate limited to 1 request per minute per domain.\n\n    Args:\n        url: The website URL to analyze (e.g., \"https://example.com\").\n\n    Returns:\n        SEO analysis result with:\n        - url: The analyzed URL\n        - score: Overall SEO score (0-100)\n        - grade: Letter grade (A-F)\n        - issues: List of SEO issues found (critical, warnings, info)\n        - meta: Extracted meta information (title, description, headings, etc.)\n        - recommendations: Prioritized list of improvements\n        - cached: Whether result was from cache\n    ",
                "inputSchema": {
                  "properties": {
                    "url": {
                      "title": "Url",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "title": "analyze_seoArguments",
                  "type": "object"
                },
                "name": "analyze_seo",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "analyze_seoDictOutput",
                  "type": "object"
                }
              },
              {
                "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, trust badges, media mentions\n    - Trustworthiness: HTTPS, contact info, privacy policy, source citations\n\n    Also detects YMYL (Your Money or Your Life) content for health, financial, and legal topics.\n\n    Results are cached for fast subsequent lookups.\n    Rate limited to 1 request per minute per domain.\n\n    Args:\n        url: The website URL to analyze (e.g., \"https://example.com\").\n\n    Returns:\n        EEAT analysis result with:\n        - url: The analyzed URL\n        - score: Overall EEAT score (0-100)\n        - grade: Letter grade (A-F)\n        - scores: Individual category scores (experience, expertise, authoritativeness, trustworthiness)\n        - issues: Categorized issues (critical, warnings, info)\n        - signals: Detected EEAT signals\n        - meta: Extracted meta information\n        - recommendations: Prioritized list of improvements\n        - cached: Whether result was from cache\n    ",
                "inputSchema": {
                  "properties": {
                    "url": {
                      "title": "Url",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "title": "analyze_eeatArguments",
                  "type": "object"
                },
                "name": "analyze_eeat",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "analyze_eeatDictOutput",
                  "type": "object"
                }
              },
              {
                "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 schema markup)\n    - Direct Answer Snippets: 20 points (short extractable blocks <50 words)\n    - Entity Clarity Score: 15 points (clear entity definitions)\n\n    Neutral Schema Scoring: If no FAQ/HowTo-style content detected, those\n    schema metrics score full points rather than penalizing.\n\n    Grade Scale: A (85-100), B (70-84), C (55-69), D (40-54), F (0-39)\n\n    Results are cached for fast subsequent lookups.\n    Rate limited to 1 request per minute per domain.\n\n    Args:\n        url: The website URL to analyze (e.g., \"https://example.com\").\n\n    Returns:\n        AEO analysis with:\n        - url: The analyzed URL\n        - aeo_score: Overall AEO score (0-100)\n        - aeo_grade: Letter grade (A-F)\n        - aeo_metrics: Individual metric scores\n        - citation: Full Citation Readiness analysis (score, grade, issues, signals)\n        - issues: Problems detected (critical, warnings, info)\n        - signals: Positive signals detected\n        - recommendations: Prioritized improvements\n        - cached: Whether result was from cache\n    ",
                "inputSchema": {
                  "properties": {
                    "url": {
                      "title": "Url",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "title": "analyze_aeoArguments",
                  "type": "object"
                },
                "name": "analyze_aeo",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "analyze_aeoDictOutput",
                  "type": "object"
                }
              },
              {
                "description": "Analyze a website URL for WCAG 2.1 Level A accessibility issues.\n\n    Automated static HTML analysis covering approximately 30-40% of WCAG 2.1\n    Level A criteria. Checks include: image alt text, form labels, heading\n    hierarchy, page title, html lang, empty links/buttons, ARIA labels,\n    duplicate IDs, skip navigation, table headers, landmarks, viewport zoom,\n    autoplay media, and tabindex ordering.\n\n    Manual testing is required for full WCAG compliance assessment.\n\n    Results are cached for fast subsequent lookups.\n    Rate limited to 1 request per minute per domain.\n\n    Args:\n        url: The website URL to analyze (e.g., \"https://example.com\").\n\n    Returns:\n        WCAG analysis with:\n        - url: The analyzed URL\n        - score: Accessibility score (0-100)\n        - grade: Letter grade (A-F)\n        - issues: Categorized issues (critical, warnings, info)\n        - meta: Extracted accessibility metadata\n        - recommendations: Prioritized improvements\n        - coverage_note: Disclaimer about automated coverage\n        - cached: Whether result was from cache\n    ",
                "inputSchema": {
                  "properties": {
                    "url": {
                      "title": "Url",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "title": "analyze_wcagArguments",
                  "type": "object"
                },
                "name": "analyze_wcag",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "analyze_wcagDictOutput",
                  "type": "object"
                }
              },
              {
                "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 categories (e.g., Adult) always score 0/F regardless of sentiment.\n\n    Args:\n        category: LLMSE category (e.g., \"Adult\", \"Politics\", \"Sports\").\n        sentiment: Content sentiment (\"Bad\", \"Neutral\", \"Good\").\n        url: Optional URL to analyze (fetches classification from cache).\n\n    Returns:\n        GARM brand safety analysis with:\n        - score: Brand safety score (0-100, higher = safer)\n        - grade: Letter grade (A-F)\n        - garm_category: Matched GARM category name or None\n        - risk_level: \"floor\"|\"high\"|\"medium\"|\"low\"|\"none\"\n        - is_floor: True if not suitable for any advertising\n        - issues: Categorized issues {critical, warnings, info}\n        - recommendations: Improvement suggestions\n    ",
                "inputSchema": {
                  "properties": {
                    "category": {
                      "anyOf": [
                        {
                          "type": "string"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Category"
                    },
                    "sentiment": {
                      "anyOf": [
                        {
                          "type": "string"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Sentiment"
                    },
                    "url": {
                      "anyOf": [
                        {
                          "type": "string"
                        },
                        {
                          "type": "null"
                        }
                      ],
                      "default": null,
                      "title": "Url"
                    }
                  },
                  "title": "analyze_garmArguments",
                  "type": "object"
                },
                "name": "analyze_garm",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "analyze_garmDictOutput",
                  "type": "object"
                }
              },
              {
                "description": "Analyze a website URL for content readability using Flesch Reading Ease.\n\n    Extracts plain text from HTML and computes readability metrics including\n    Flesch Reading Ease score, Flesch-Kincaid grade level, reading time,\n    and word/sentence statistics.\n\n    Grade Scale (web-optimized):\n    - A (60-100): Easy, 6th-8th grade \u2014 ideal for web content\n    - B (50-59): Fairly easy, some high school\n    - C (30-49): Standard, college level\n    - D (10-29): Difficult, graduate level\n    - F (0-9): Very difficult, professional/academic\n\n    Results are cached for fast subsequent lookups.\n    Rate limited to 1 request per minute per domain.\n\n    Args:\n        url: The website URL to analyze (e.g., \"https://example.com\").\n\n    Returns:\n        Readability analysis with:\n        - url: The analyzed URL\n        - score: Flesch Reading Ease score (0-100, higher = easier)\n        - grade: Letter grade (A-F)\n        - flesch_kincaid_grade_level: US school grade level equivalent\n        - reading_time_minutes: Estimated reading time in minutes\n        - word_count: Total word count\n        - sentence_count: Total sentence count\n        - difficult_words: Count of difficult/uncommon words\n        - cached: Whether result was from cache\n    ",
                "inputSchema": {
                  "properties": {
                    "url": {
                      "title": "Url",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "title": "analyze_readabilityArguments",
                  "type": "object"
                },
                "name": "analyze_readability",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "analyze_readabilityDictOutput",
                  "type": "object"
                }
              },
              {
                "description": "Perform comprehensive audit of a website URL.\n\n    Fetches the URL content ONCE and provides a combined report with:\n    - Classification: category, subcategory, language, sentiment, demographics\n    - SEO Analysis: score, grade, issues, recommendations\n    - EEAT Analysis: experience, expertise, authoritativeness, trustworthiness scores\n    - AEO Analysis: AI answer engine optimization score, metrics, issues, signals\n      (includes full Citation Readiness analysis in the nested 'citation' key)\n    - Advertiser Matching: best-fit advertising networks with scores\n    - Similar Sites: competitor/related sites from the same category\n\n    This is more efficient than calling classify_url, analyze_seo, analyze_eeat,\n    analyze_aeo, select_advertiser, and find_similar_sites separately as it only\n    fetches the page once.\n\n    Args:\n        url: The website URL to audit (e.g., \"https://example.com\").\n\n    Returns:\n        Comprehensive audit report with:\n        - url: The analyzed URL\n        - classification: Category, subcategory, language, sentiment, demographics\n        - seo: Score, grade, issues, recommendations\n        - eeat: EEAT score, grade, category scores, issues, signals\n        - aeo: AEO score, grade, metrics, issues, signals (includes citation results)\n        - advertisers: Matched advertising networks with scores\n        - similar_sites: Related sites from the same category (up to 10)\n        - cached: Whether result was from cache\n    ",
                "inputSchema": {
                  "properties": {
                    "url": {
                      "title": "Url",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "title": "auditArguments",
                  "type": "object"
                },
                "name": "audit",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "auditDictOutput",
                  "type": "object"
                }
              },
              {
                "description": "Find similar or competitor websites based on classification.\n\n    Takes a URL, classifies it (or uses cached classification), and returns\n    other websites from the same category and subcategory. Useful for\n    competitive analysis and discovering related content.\n    Rate limited to 1 request per minute per domain.\n\n    Args:\n        url: The website URL to find similar sites for.\n        limit: Maximum number of similar sites to return (1-50, default 10).\n\n    Returns:\n        Dictionary with:\n        - url: The input URL (normalized)\n        - classification: The URL's category and subcategory\n        - similar_sites: List of similar URLs from the same category\n        - total_in_category: Total sites in this category/subcategory\n        - cached: Whether the classification was from cache\n    ",
                "inputSchema": {
                  "properties": {
                    "limit": {
                      "default": 10,
                      "title": "Limit",
                      "type": "integer"
                    },
                    "url": {
                      "title": "Url",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "title": "find_similar_sitesArguments",
                  "type": "object"
                },
                "name": "find_similar_sites",
                "outputSchema": {
                  "additionalProperties": true,
                  "title": "find_similar_sitesDictOutput",
                  "type": "object"
                }
              }
            ]
          }
        },
        "requested_protocol_version": "2025-03-26",
        "resumed": true,
        "session_id_present": true,
        "transport": "streamable-http",
        "url": "https://llmse.ai/mcp"
      },
      "latency_ms": 172.12,
      "status": "ok"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "reason": "no_tools"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "error": "Client error '400 Bad Request' for url 'https://llmse.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
        "headers": {
          "content-type": "application/json",
          "mcp-session-id": "00d37cdfa8ab4bf59a81b46f059891d5",
          "strict-transport-security": "max-age=2592000"
        },
        "http_status": 400,
        "payload": {},
        "url": "https://llmse.ai/mcp"
      },
      "latency_ms": 123.76,
      "status": "error"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json",
          "mcp-session-id": "8ef5045c2f2e44ba8e57fe9db33f6978",
          "strict-transport-security": "max-age=2592000"
        },
        "bad_protocol_payload": {
          "error": {
            "code": -32600,
            "message": "Bad Request: Unsupported protocol version: 1999-99-99. Supported versions: 2024-11-05, 2025-03-26, 2025-06-18, 2025-11-25"
          },
          "id": "server-error",
          "jsonrpc": "2.0"
        },
        "bad_protocol_status_code": 400,
        "delete_error": null,
        "delete_status_code": 200,
        "expired_session_error": null,
        "expired_session_status_code": 404,
        "issues": [
          "missing_protocol_header"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2025-03-26",
        "session_id_present": true,
        "transport": "streamable-http"
      },
      "latency_ms": 106.04,
      "status": "warning"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [
          "experimental",
          "prompts",
          "resources",
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 400,
          "probe_status": "missing"
        }
      },
      "latency_ms": 35.24,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '403 Forbidden' for url 'https://llmse.ai/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403",
      "url": "https://llmse.ai/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "server_card": {
      "error": "Client error '403 Forbidden' for url 'https://llmse.ai/.well-known/mcp/server-card.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403",
      "url": "https://llmse.ai/.well-known/mcp/server-card.json"
    },
    "tools_list": {
      "error": "Client error '400 Bad Request' for url 'https://llmse.ai/mcp'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400",
      "headers": {
        "content-type": "application/json",
        "mcp-session-id": "00d37cdfa8ab4bf59a81b46f059891d5",
        "strict-transport-security": "max-age=2592000"
      },
      "http_status": 400,
      "payload": {},
      "url": "https://llmse.ai/mcp"
    }
  },
  "remote_url": "https://llmse.ai/mcp",
  "server_card_payload": null,
  "server_identifier": "ai.llmse/mcp"
}
Known versions
  • 1.3.12
Validation history
7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
0%
Freshness
4.7h
TimestampStatusScoreLatencyTools
Aug 07, 2026 07:18:30 PM UTC Failing 3.6 1347.6 ms 0
Aug 07, 2026 07:18:15 AM UTC Failing 3.6 1223.1 ms 0
Aug 06, 2026 07:17:58 PM UTC Failing 3.3 1008.0 ms 0
Aug 06, 2026 07:17:31 AM UTC Failing 3.3 1552.7 ms 0
Aug 05, 2026 11:17:04 PM UTC Failing 6.4 1179.6 ms 0
Aug 05, 2026 07:16:49 PM UTC Failing 14.0 1187.1 ms 0
Aug 03, 2026 10:24:13 AM UTC Failing 22.1 1303.6 ms 0
Aug 02, 2026 06:30:19 PM UTC Failing 21.9 1094.8 ms 0
Validation timeline
ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Aug 07, 2026 07:18:30 PM UTC Failing 3.6 2025-03-26 public 0 0 auth_mode_changed
Aug 07, 2026 07:18:15 AM UTC Failing 3.6 unknown unknown 0 0 none
Aug 06, 2026 07:17:58 PM UTC Failing 3.3 unknown unknown 0 0 none
Aug 06, 2026 07:17:31 AM UTC Failing 3.3 unknown unknown 0 0 none
Aug 05, 2026 11:17:04 PM UTC Failing 6.4 unknown unknown 0 0 none
Aug 05, 2026 07:16:49 PM UTC Failing 14.0 unknown unknown 0 0 none
Aug 03, 2026 10:24:13 AM UTC Failing 22.1 unknown unknown 0 0 none
Aug 02, 2026 06:30:19 PM UTC Failing 21.9 unknown unknown 0 0 none
Aug 02, 2026 03:58:20 AM UTC Failing 21.7 unknown unknown 0 0 none
Aug 01, 2026 01:09:11 PM UTC Failing 21.6 unknown unknown 0 0 none
Recent validation runs
Recent validation runs for this MCP server
StartedStatusSummaryLatencyChecks
Aug 07, 2026 07:18:29 PM UTC Completed Failing 1347.6 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, schema_divergence_probe, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe
Aug 07, 2026 07:18:14 AM UTC Completed Failing 1223.1 ms
Aug 06, 2026 07:17:57 PM UTC Completed Failing 1008.0 ms
Aug 06, 2026 07:17:30 AM UTC Completed Failing 1552.7 ms
Aug 05, 2026 11:17:02 PM UTC Completed Failing 1179.6 ms
Aug 05, 2026 07:16:47 PM UTC Completed Failing 1187.1 ms
Aug 03, 2026 10:24:11 AM UTC Completed Failing 1303.6 ms
Aug 02, 2026 06:30:18 PM UTC Completed Failing 1094.8 ms
Aug 02, 2026 03:58:19 AM UTC Completed Failing 1237.4 ms
Aug 01, 2026 01:09:10 PM UTC Completed Failing 1565.0 ms
Public server reputation
Validation success 7d
0.0
Validation success 30d
0.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0
Incident & change feed
TimestampEventDetails
Aug 07, 2026 07:18:30 PM UTC Latest validation: failing Score 6.1 with status failing.
Aug 07, 2026 07:18:30 PM UTC Auth mode changed Auth mode moved from unknown to public.
Aug 07, 2026 07:18:15 AM UTC Score changed Score delta +0.3 versus the previous run.
Aug 05, 2026 11:00:59 AM UTC Score corrected (post-1.0.503 remediation, R1 zero-anchoring) Prior: 22.07. Corrected: 14.15.
Capabilities
  • OAuth:
  • DCR/CIMD:
  • Prompts:
  • Homepage: none
  • Docs: none
  • Support: none
  • Icon: none
  • Remote endpoint: https://llmse.ai/mcp
  • Server card: none
Use-case taxonomy
search
Benchmark tasks
Benchmark taskStatusEvidence
Discover tools Likely to fail
  • initializeOK
  • tools_listError
Read-only fetch flow Likely to fail
  • resource_readMissing
  • read_only_tool_surfaceMissing
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Likely to fail
  • action_safety_probeNot_Assessed
Utility coverage
Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no
Transport compliance drilldown
Probe status
Warning
Transport
streamable-http
Session header
yes
Protocol header
no
Bad protocol response
400
DELETE teardown
200
Expired session retry
404
Last-Event-ID visible
no

Issues: missing_protocol_header

Request association
Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none
Connector replay
Status
Missing
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.
Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Validation diff
Score delta
0
Summary changed
no
Tool delta
0
Prompt delta
0
Auth mode changed
yes
Write surface expanded
no
Protocol regressed
no
Registry drift changed
no

Regressed checks: action_safety_probe, connector_publishability_probe, oauth_protected_resource, provenance_divergence_probe, server_card, tools_list

Improved checks: initialize, official_registry_probe, probe_noise_resilience, session_resume_probe

Newly assessed dimensions: none

No longer assessed dimensions: none

ComponentPreviousLatestDelta
No component deltas between the latest two runs.
Registry & provenance divergence
Probe status
Not_Assessed
Direct official match
yes
Drift fields
none
FieldRegistryLive server card
Titlen/an/a
Versionn/an/a
Homepagen/an/a
Active alerts
  • Latest validation is failing (critical)
    Core MCP flows did not validate successfully on the latest run.
  • tools/list regressed (critical)
    Tool discovery became less reliable on the latest run.
  • Auth mode changed (high)
    Auth mode changed from unknown to public.
Aliases & registry graph
IdentifierSourceCanonicalScore
ai.llmse/mcp official_registry yes n/a
Alias consolidation
Canonical identifier
ai.llmse/mcp
Duplicate aliases
0
Registry sources
official_registry
Homepages
none
Source disagreements
FieldWhat differsObserved values
No source disagreements detected.

Fix it

Why this score?
Access & Protocol
18/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
2/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
6/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
6/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
13/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
4/8
Adoption clues and public evidence that the server is intended for external use.
Algorithmic score breakdown
Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
0/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
0/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
0/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
2/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
0/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
0/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
1/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
0/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
0/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
1/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
1/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
1/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
0/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
0/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
0/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
3/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
1/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
4/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
0/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
3/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
0/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
0/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
2/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
0/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
0/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
0/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
0/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Official Registry Presence
4/4
Whether the server appears directly or indirectly in the official MCP registry.
Safety Transparency
2/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
0/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
1/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
1/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
1/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
0/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
1/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
1/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
1/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
0/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
0/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.
Actionable remediation
SeverityRemediationWhy it mattersRecommended action
Critical Ensure tools/list succeeds consistently Tools discovery is the minimum viable contract for most MCP clients and directories. Make tools/list succeed unauthenticated when possible, or document the auth flow in the server card.
Playbook
  • Make `tools/list` deterministic across repeated calls.
  • Document or relax auth requirements for discovery routes.
  • Check that tool names, descriptions, and schemas remain stable across deploys.
Critical Respond to latest validation is failing Core MCP flows did not validate successfully on the latest run. Fix the failing checks first, then revalidate to confirm the recovery path.
Playbook
  • Fix the failing checks first.
  • Review the latest incident feed and validation diff for the first regression.
  • Revalidate once the remediation lands.
Critical Respond to tools/list regressed Tool discovery became less reliable on the latest run. Compare tool enumeration outputs between runs and remove non-deterministic behavior.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Publish a complete server card Missing or incomplete server-card metadata weakens discovery, documentation, and trust signals. Serve /.well-known/mcp/server-card.json and include tools, prompts/resources, homepage, and support links.
Playbook
  • Publish `/.well-known/mcp/server-card.json`.
  • Include homepage, repository, support, tools, prompts/resources, and auth metadata.
  • Revalidate the server after publishing the card.
High Respond to auth mode changed Auth mode changed from unknown to public. Document the new auth posture and confirm protected-resource and challenge metadata still match reality.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Advertise a current MCP protocol revision (2025-06-18 or later) in both the initialize response and the MCP-Protocol-Version header.
Playbook
  • Update the server's advertised protocol version to a current MCP revision (2025-06-18 or later).
  • Return the negotiated version consistently in both the `initialize` response and the `MCP-Protocol-Version` header.
  • Revalidate and confirm `protocol_version_probe` reports `ok`.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Serve `/.well-known/openid-configuration` with `issuer`, `jwks_uri`, `authorization_endpoint`, and `token_endpoint`.
  • List supported grant types in `grant_types_supported` and scopes in `scopes_supported`.
  • Revalidate and confirm the `openid_configuration` check returns `ok`.
Medium Raise Adoption & Market score Adoption clues and public evidence that the server is intended for external use. Increase external documentation and directory coverage so users can discover and evaluate the server.
Medium Raise Interface Quality score How well the tool/resource interface communicates and behaves under automation. Improve schemas, error contracts, and recovery messages so agents can reason about the surface automatically.
Medium Raise Reliability & Trust score Operational stability, consistency, and trustworthiness over time. Stabilize behavior over time and reduce failure drift between validation runs.
Medium Raise Security Posture score How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs. Reduce destructive, egress, exec, secret, and freeform-input risk across the exposed tool surface.
Playbook
  • Classify each tool by read/write/delete/exec/network capability and confirm the classification is intentional.
  • Gate high-risk tools behind scoped auth, narrow their schemas, and document safeguards such as allowlists or dry-run paths.
  • Revalidate after the risky tools are tightened so the security posture score reflects the current surface.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Advertise only the advanced capabilities (roots, sampling, elicitation) you have actually implemented end to end in the initialize capabilities object.
Playbook
  • Add the capabilities you actually support (`roots`, `sampling`, `elicitation`) to the `capabilities` object returned from `initialize`.
  • Only advertise a capability once the corresponding request/response flow is implemented end to end.
  • Revalidate and confirm `advanced_capabilities_probe` reflects the updated capability set.
Point loss breakdown
ComponentCurrentPoints missing
Utility Coverage 0/4 -4.0
Trust Confidence 0/4 -4.0
Tool Surface Design 0/4 -4.0
Tool Snapshot Churn 0/4 -4.0
Tool Namespace Clarity 0/4 -4.0
Tool Capability Clarity 0/4 -4.0
Task Success 0/4 -4.0
Step Up Auth 0/4 -4.0
SLO Health 0/4 -4.0
Schema Completeness 0/4 -4.0
Result Shape Stability 0/4 -4.0
Resource Contract 0/4 -4.0
Compatibility profiles
OpenAI Connectors
55.6
partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; tools/list must succeed.; OAuth interoperability should be strong.
Connector URL: https://llmse.ai/mcp
# No OAuth metadata detected.
# Server: ai.llmse/mcp
Claude Desktop
66.7
partial
tools/list must succeed.; A useful Claude integration needs at least one exposed tool.
{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://llmse.ai/mcp"]
    }
  }
}
Smithery
40.0
blocked
Tool discovery must succeed.; Metadata quality should be serviceable.; Machine-readable failure semantics should be present.
smithery mcp add "https://llmse.ai/mcp"
Generic Streamable HTTP
66.7
partial
tools/list must succeed.; Session behavior should be predictable.
curl -sS https://llmse.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Governance

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Evidence age tier
Verified in last 24h
Policy SLA (contractual, distinct from the public 24h freshness window): 168.0h • confidence-weighted score (display score discounted for evidence age and confidence -- an internal TrustOps input, not the public score): n/a • evidence too old to display:
Policy exports
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/decide
Returns allowed tools, blocked tools, approval requirement, and reason.
Hosted runtime
Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.
Authenticated validation
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
none
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes
MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Activation readiness
Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.
Minimum tier
TrustOps
Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.
Hosted endpoint
/hosted/{namespace}/{name}/mcp
The endpoint enforces egress allowlists and records audit/usage events.
Blockers
score_below_hosting_threshold server_not_healthy_or_degraded latest_validation_not_passing blocked_by_active_alerts blocked_by_production_readiness
DeploymentStatusEndpointRelease
No hosted runtime deployments yet.
Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview
Install snippets
Openai Connectors
Connector URL: https://llmse.ai/mcp
# No OAuth metadata detected.
# Server: ai.llmse/mcp
Claude Desktop
{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://llmse.ai/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://llmse.ai/mcp"
Generic Http
curl -sS https://llmse.ai/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'
Agent access & tool surface
Live server tools
No live tool surface captured yet.
Observed from the latest live validation against https://llmse.ai/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
0 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for ai.llmse/mcp.
Direct machine links