Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Rank by Ouroboros Apps

REMOTE · RANK.OUROBOROSAPPS.COM

SEO rankings and traffic from Google Search Console for AI assistants, read-only

+4 this week 85 Trust /100

Last scanned (6 hours ago)

Scores higher than 92% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security94
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 870 tokens (~96/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +18
    • DNSSEC: unverified → fail ▼ security
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.33 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 15 Oct 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 13 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Oct 2026 · Probed https://rank.ouroborosapps.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rank.ouroborosapps.com CN=YR1,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 RSA 2048 SHA256-RSA 633ae13ca163fa4b277d7d2378d1b74fbd8
SANs: rank.ouroborosapps.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of rank.ouroborosapps.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
ouroborosapps.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://rank.ouroborosapps.com/.well-known/oauth-protected-resource/mcp"

Bearer resource_metadata="https://rank.ouroborosapps.com/.well-known/oauth-protected-resource/mcp"
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Protected resource metadata

Document https://rank.ouroborosapps.com/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://rank.ouroborosapps.com/mcp
Authorisation server https://rank.ouroborosapps.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rank.ouroborosapps.com/mcp Verified 200
http (plaintext) http://rank.ouroborosapps.com/mcp HTTPS enforced 308 https://rank.ouroborosapps.com/mcp
MCP tools · 9 exposed · ~784 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
account_status ~42

Whether Google Search Console is connected, when the 14-day trial ends, and whether Pro access is active. Does not query Search Console and does not include a price.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data–––

No examples provided.

compare_periods ~114

Compare two date ranges using the Search Console totals for a property (no dimension grouping). Reports both API metric objects. Differences are labeled as derived from those returned numbers. Omit compare dates to use the previous window of the same length.

NameTypeReqDescription
compareEndDate–––
compareStartDate–––
countrystring––
devicestring––
endDate–––
searchTypestring––
siteUrlstringyes–
startDatestring––
NameTypeReqDescription
data–––

No examples provided.

dropped_pages ~104

Pages whose Search Console position got worse, whose clicks fell, or that disappeared from the current response. Does not invent zeros for pages the current response omitted.

NameTypeReqDescription
compareEndDate–––
compareStartDate–––
countrystring––
devicestring––
endDate–––
limitinteger––
searchTypestring––
siteUrlstringyes–
startDatestring––
NameTypeReqDescription
data–––

No examples provided.

inspect_url ~67

URL Inspection status for one URL on a property you can access. Returns the Search Console inspection response, including verdict, coverage, and last crawl fields when the API sent them.

NameTypeReqDescription
inspectionUrlstringyes–
languageCodestring––
siteUrlstringyes–
NameTypeReqDescription
data–––

No examples provided.

list_properties ~34

List the Search Console properties on the connected Google account. Returns siteUrl and permissionLevel exactly as the sites.list API returned them.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data–––

No examples provided.

performance_trends ~89

Daily clicks, impressions, ctr, and position for a property. Each row is a date Search Console returned. Missing dates are not filled in, and ctr is the API fraction.

NameTypeReqDescription
countrystring––
devicestring––
endDate–––
searchTypestring––
siteUrlstringyes–
startDatestring––
NameTypeReqDescription
data–––

No examples provided.

quick_wins ~124

Queries with high impressions and low ctr in Search Console. Defaults are at least 100 impressions and ctr at or below 0.02 (the API fraction, so 0.02 is 2%). Does not estimate missed clicks.

NameTypeReqDescription
countrystring––
devicestring––
endDate–––
limitinteger––
maxCtrnumber––
minImpressionsnumber––
searchTypestring––
siteUrlstringyes–
startDatestring––
NameTypeReqDescription
data–––

No examples provided.

top_pages ~100

Top pages for one property and date range. Metrics are copied from Search Console rows. ctr is the API fraction from 0 to 1. Omit dates to use the default 28-day window.

NameTypeReqDescription
countrystring––
devicestring––
endDate–––
limitinteger––
searchTypestring––
siteUrlstringyes–
startDatestring––
NameTypeReqDescription
data–––

No examples provided.

top_queries ~110

Top search queries for one property and date range. clicks, impressions, ctr, and position are copied from Search Console. ctr is a fraction from 0 to 1, not a percent. Omit dates to use the default 28-day window.

NameTypeReqDescription
countrystring––
devicestring––
endDate–––
limitinteger––
searchTypestring––
siteUrlstringyes–
startDatestring––
NameTypeReqDescription
data–––

No examples provided.

Install

How do I install the Rank by Ouroboros Apps MCP server?

Rank by Ouroboros Apps is a hosted endpoint at https://rank.ouroborosapps.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · rank.ouroborosapps.com

# add to Claude Code
claude mcp add --transport http lahutchins91-rank 'https://rank.ouroborosapps.com/mcp'
Common questions

What is the Rank by Ouroboros Apps MCP server?

Rank by Ouroboros Apps is an MCP server listed in the public MCP registry as io.github.LAHutchins91/rank. SEO rankings and traffic from Google Search Console for AI assistants, read-only. This page covers its hosted endpoint (https://rank.ouroborosapps.com/mcp).

Is the Rank by Ouroboros Apps MCP server safe to use?

Rank by Ouroboros Apps scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Rank by Ouroboros Apps MCP server expose?

Rank by Ouroboros Apps exposes 9 tools: list_properties, top_queries, top_pages, performance_trends, compare_periods, and 4 more. Their descriptions and schemas cost roughly 784 tokens of context every time the server is loaded.

Does the Rank by Ouroboros Apps MCP server require authentication?

Yes. Rank by Ouroboros Apps asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Rank by Ouroboros Apps MCP server still maintained?

Rank by Ouroboros Apps is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.