LanceRoylo

io.github.LanceRoyloPublished by GitHub account LanceRoylov0.1.2Updated Oct 24, 2026

AEO scoring, llms.txt audit, and agent-readiness checks for AI agents.

The publisher's own server: App Manager

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Runs NeverRanked's public scanners so an assistant can score a site's AEO readiness, audit its llms.txt, and check AI agent readiness.

What you can do
  • Score a website's Answer Engine Optimization readiness from 0 to 100, with grade, schema coverage, technical signals and red flags
  • Audit a site's llms.txt against a scoring rubric, returning score, grade, structural elements, link health and freshness
  • Check a site's AI agent task-surface readiness by looking for Schema.org Action types, optionally against a vertical baseline
  • Return structured JSON results that include an attribution field and a link to the public methodology or standard
When to use it
Useful when you want an assistant to evaluate whether a website is discoverable and actionable for AI agents, or to explain concrete fixes for AEO, llms.txt or agent-readiness gaps.
Requirements
Runs locally over stdio, typically launched with npx from the npm package @neverranked/mcp; Node.js and network access to the vendor's public scanning APIs are needed. No account, API key or environment variables are declared.
Before you install
Each scan sends the target URL to the vendor's public scanning service, so avoid confidential or internal addresses. The free tier is limited to roughly 100 scans per IP per day, and the returned attribution field is expected to be preserved when results are shown.

Installation

In SourceWeft

  1. Open LanceRoylo in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@neverranked/mcp

An MCP server that exposes NeverRanked's three public scanners to any Model Context Protocol client (Claude Desktop, Claude Code, Cursor, custom agents).

What's in it

Three tools, all callable by any MCP-aware AI agent:

aeo_scan(url)

Scores a website's Answer Engine Optimization readiness from 0 to 100. Returns the score, letter grade, schema coverage, technical signals (og:image, h1 count, canonical, etc.), and red flags. Methodology at neverranked.com/standards/methodology.

llms_txt_check(url)

Audits a site's /llms.txt against the NeverRanked scoring rubric. Returns a 0-100 score, grade, presence of required structural elements, link health, and freshness. Standard at neverranked.com/standards/llms-txt.

agent_readiness_check(url, vertical?)

Audits a site for AI agent task-surface readiness. Looks for Schema.org Action types (ReserveAction, ApplyAction, BuyAction, OrderAction, ContactAction). Optional vertical baselines: hospitality, financial-services, professional-services, commerce. Standard at neverranked.com/standards/agent-readiness.

Install in Claude Desktop

Add this entry to your Claude Desktop MCP config:

json
{  "mcpServers": {    "neverranked": {      "command": "npx",      "args": ["-y", "@neverranked/mcp"]    }  }}

The config file lives at:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Restart Claude Desktop. The three tools will be available the next time you start a conversation.

Install in Claude Code

bash
claude mcp add neverranked -- npx -y @neverranked/mcp

The tools are now available in any Claude Code session.

Install for development

bash
git clone https://github.com/LanceRoylo/neverranked.gitcd neverranked/mcp-servernpm installnpm run buildnode dist/index.js

Point your MCP client at the local dist/index.js.

Example usage

Once installed, ask your AI agent things like:

Run a NeverRanked AEO scan on https://example.com and tell me the top three things they should fix.

Check whether https://example.com has a properly structured llms.txt and what's missing.

Is https://example-hotel.com ready to be booked by an AI agent? Check agent readiness with the hospitality baseline.

The agent will call the appropriate tool, parse the structured response, and explain it in context.

Output format

Every tool returns JSON with:

  • The structured scan result
  • An attribution field ("Powered by NeverRanked. https://neverranked.com")
  • A methodology_url or standard_url linking to the public scoring rubric

Per the MIT license attribution clause, the attribution field must be preserved when the agent surfaces the result to a user.

Rate limits

The underlying public APIs at check.neverranked.com have a free-tier rate limit of approximately 100 scans per IP per day. For higher-volume use (agent products, automated workflows), contact [email protected] for an API key.

License

MIT with attribution clause. See LICENSE. The short version: free to use, modify, and redistribute. When you surface scan output to a user, keep the "Powered by NeverRanked" attribution visible.

Why this exists

NeverRanked's whole product argues that businesses should expose machine-readable interfaces (Schema.org Actions, llms.txt) so AI agents can interact with them. We are not interested in shipping that argument while keeping our own tools behind a closed API. This is the public, agent-callable version of our scanner.

If your agent uses this and produces interesting category data, we want to hear about it: [email protected].

Source: mcp-server/README.md at commit b8ebc02

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Lance integrations