_ registry / mcp streamable-http

onpage-dev

https://onpage.dev

Registry code: 5656cf7a6ba0dfb9

api record

OnPage.dev is an SEO and AI-visibility scanner built for AI assistants that can act on results. Workflows: (1) Audit and fix: scan_page, then get_fix_pack or generate_schema for ready code, apply the changes, check unpublished HTML with scan_html before deploying, then confirm with rescan_and_compare. Repeat until the score is where the user wants it. (2) AI visibility: check_ai_visibility, then ai_crawler_policy for robots.txt rules, generate_llms_txt for an llms.txt file, and find_answer_passages to see whether a page answers the questions people ask AI. (3) Titles and descriptions: write…

endpoint
https://onpage.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is onpage-dev live?
Not measured yet: the hub has not completed a check of this server.
Is onpage-dev free to use?
Not measured yet.
What tools does onpage-dev have?
11 tools: generate_schema, find_answer_passages, generate_llms_txt, ai_crawler_policy, scan_page, check_ai_visibility, check_focus_keyword, get_fix_pack, ….
Is onpage-dev safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 11 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 11 tools
11 never probed 0 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • generate_schema unknown never probed

    Generate a JSON-LD block for a page from its own content and validate it against Google's rich result rules. Types: Article, Product, FAQPage (built from question headings and their answers), Organization (with sameAs links found on the page), BreadcrumbList (from the URL), or auto to pick the best fit. Values that cannot be read from the page are marked TODO.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full address of the page, for example https://example.com/pricing. A bare domain also works."
    },
    "type": {
      "enum": [
        "auto",
        "Article",
        "Product",
        "FAQPage",
        "Organization",
        "BreadcrumbList"
      ],
      "type": "string",
      "description": "Schema type, default auto."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • find_answer_passages unknown never probed

    Find the passages on a page that best answer a given question, the way AI answer engines pick text to quote. Returns the top passages with their heading, word count and whether they are a quotable length (40 to 90 words). Use the result to judge whether the page answers the question well, and to rewrite the best passage into a direct answer.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url",
    "question"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full address of the page, for example https://example.com/pricing. A bare domain also works."
    },
    "question": {
      "type": "string",
      "description": "The question people ask, for example 'how long does shipping take to Germany'."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • generate_llms_txt unknown never probed

    Build a ready-to-upload llms.txt for a site from its sitemap and home page: site name, summary and the main pages grouped by section. Upload the result to the root of the site, for example https://example.com/llms.txt.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Home page of the site, for example https://example.com."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • ai_crawler_policy unknown never probed

    Write robots.txt rules for AI crawlers based on a policy, and merge them into the site's current robots.txt. Policies: allow_all, search_only (allow AI search and user-requested fetches, block model training), block_training (same as search_only), block_all. Returns the full new robots.txt and what changes.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url",
    "policy"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Any page of the site."
    },
    "policy": {
      "enum": [
        "allow_all",
        "search_only",
        "block_training",
        "block_all"
      ],
      "type": "string",
      "description": "Which AI crawlers to allow."
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • scan_page unknown never probed

    Scan one public web page for SEO and AI visibility. Returns a 0-100 score, the issues to fix first with why and how, AI readiness, and the key facts (title, description, headings, words, speed, structured data). Use this first for any question about how a page performs in Google or AI search.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full address of the page, for example https://example.com/pricing. A bare domain like example.com also works."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • check_ai_visibility unknown never probed

    Check whether ChatGPT, Claude, Perplexity, Gemini and other AI crawlers may read a page (robots.txt per bot), whether llms.txt exists, how ready the content is for AI answers (11 checks), and how an AI model sees the page as plain text. Use this for questions like 'why does ChatGPT not mention my site'.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full address of the page, for example https://example.com/pricing. A bare domain like example.com also works."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • check_focus_keyword unknown never probed

    Check how well a page targets one search term: title, meta description, H1, URL, first 100 words, subheadings, image alt texts and keyword density (flags stuffing over 3%). Returns 8 checks with a tip each.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url",
    "keyword"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full address of the page, for example https://example.com/pricing. A bare domain like example.com also works."
    },
    "keyword": {
      "type": "string",
      "description": "The search term the page should rank for, for example 'running shoes'."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • get_fix_pack unknown never probed

    Generate ready-to-paste HTML for the issues on a page, built from the page's own content: a title tag, meta description, canonical, social (Open Graph) tags, viewport and a JSON-LD starting point. Only issues the page actually has are included.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full address of the page, for example https://example.com/pricing. A bare domain like example.com also works."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • scan_html unknown never probed

    Scan raw HTML that is not published yet, for example a local build, a template or a draft from your editor. Returns the same score, fixes and AI readiness as scan_page. Pass the full HTML document; url is optional and only used to resolve relative links. Use this in coding assistants to check SEO before deploying.

    mcp-tool

    {
  "type": "object",
  "required": [
    "html"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Optional address the page will live at, used for relative links and the canonical check."
    },
    "html": {
      "type": "string",
      "description": "The complete HTML document, up to 900 KB."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • rescan_and_compare unknown never probed

    Scan a live page again and compare it with the previous scan of that page: score change, issues fixed, new issues and AI readiness change. Use this after deploying fixes to confirm they worked, or to catch regressions such as a robots.txt change that suddenly blocks AI crawlers. Repeat until the score is where you want it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full address of the page, for example https://example.com/pricing. A bare domain also works."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • check_snippet unknown never probed

    Estimate how a title and meta description show in Google: pixel width against the cut-off on desktop and mobile, and the truncated text a searcher would see. No network call. Use it to iterate on title and description variants until they fit.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title"
  ],
  "properties": {
    "title": {
      "type": "string",
      "description": "Proposed title tag text."
    },
    "description": {
      "type": "string",
      "description": "Proposed meta description."
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5656cf7a6ba0dfb9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5656cf7a6ba0dfb9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5656cf7a6ba0dfb9/badge.svg)](https://brick.blue/agent/5656cf7a6ba0dfb9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.