ai.llmse/mcp
ai.llmse/mcp · 1.3.12
Public MCP server for the LLM Search Engine
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 20 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://llmse.ai/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 10 tools.
- Protocol
- 2025-06-18
- Calls itself
- LLMSE Public API 1.25.0
- Handshake time
- 169 ms
- HTTP status
- 200
The tools it lists (10, as of 9 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
classify_urlClassify a website URL into category, subcategory, language, and sentiment. Fetches the URL content and uses AI for classification. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to classify (e.g., "https://example.com"). Returns: Classification result with: - url: The normalized URL - category: Main category (e.g., "Sports", "Technology") - subcategory: Specific subcategory - language: Detected content language - sentiment: Content sentime
select_advertiserSelect the best advertisers based on website demographics. Matches advertisers to website content based on classification demographics. Provide either a URL (classification will be fetched) or demographics directly. Rate limited to 1 request per minute per domain when using URL. Scoring weights: - Category match: +10 points - Age match: +5 points - Gender match: +3 points - Sentiment match: +2 points - Higher CPM bid as tiebreaker Args: url: URL to match advertisers for (fetches classification from cache). category: Target category (e.
analyze_seoAnalyze a website URL for SEO optimizations. Fetches the URL content and analyzes HTML for possible SEO improvements. Results are cached for fast subsequent lookups. Rate limited to 1 request per minute per domain. Args: url: The website URL to analyze (e.g., "https://example.com"). Returns: SEO analysis result with: - url: The analyzed URL - score: Overall SEO score (0-100) - grade: Letter grade (A-F) - issues: List of SEO issues found (critical, warnings, info) - meta: Extracted meta information (title, descriptio
analyze_eeatAnalyze a website URL for E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness). Evaluates content quality signals based on Google's Search Quality Rater Guidelines and "Creating helpful content" documentation. Detects EEAT signals including: - Experience: First-person language, case studies, testimonials, years of experience - Expertise: Author credentials, certifications, professional memberships, topic depth - Authoritativeness: Organization schema, awards, trust badges, media mentions - Trustworthiness: HTTPS, contact info, privacy policy, source cita
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
ai.llmse/mcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 262 days ago. The registry entry