Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
SEO Authority is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
6
downloads a day
local
runs on your machine
564
downloads in 30d
What it does
SEO authority, keyword, competitor, content, site-audit, and internal-link tools with optional.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user seo-authority-mcp '--' npx -y @forgemeshlabs/seo-authority-mcp
# 2 — ask your agent for something these tools do
# get_seo_capabilities, get_domain_authority, compare_domain_authority and 8 more
SEO Authority costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts SEO Authority as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user seo-authority-mcp '--' npx -y @forgemeshlabs/seo-authority-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take SEO_API_BASE (Optional backend override; defaults to https://seo.forgemesh.io.), SEO_X402_PRIVATE_KEY (Optional EVM wallet private key for automatic x402 USDC settlement.), SEO_MAX_PAYMENT_USDC (Maximum automatic payment per tool call; defaults to 0.15 USDC.) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Retrieve free capability, provenance, and unavailable-metric disclosures before choosing a paid SEO tool.
No parameter schema on file.
Measure one domain's open-web SEO authority using Common Crawl harmonic centrality and PageRank graph data; costs $0.01 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — |
Compare open-web SEO authority for 2 to 20 domains and rank the results; costs $0.02 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domains | array | yes | Two to twenty domains or URLs. |
Score supplied page HTML for deterministic on-page SEO checks without claiming page authority; costs $0.01 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | yes | — | |
| html | yes | — |
Correct likely spelling errors in an SEO search query; costs $0.005 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | yes | — |
Generate deterministic long-tail and intent-oriented variants of an SEO query; costs $0.01 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | yes | — |
Generate and prioritize long-tail keyword opportunities without fabricating volume, CPC, SERP, or difficulty metrics; costs $0.05 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| seed | yes | — | |
| audience | no | — | |
| domain_authority_score | number | no | Optional known authority score used for prioritization. |
Find content gaps from customer-supplied site and competitor pages without claiming live SERP verification; costs $0.10 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | object | yes | Your domain and supplied pages. |
| competitors | array | yes | One to ten competitors with supplied pages. |
Create an evidence-tagged SEO content brief from a keyword and supplied competitor or site pages; costs $0.10 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | yes | — | |
| competitor_pages | array | no | Optional competitor pages providing evidence. |
| site_pages | array | no | Optional existing site pages for differentiation and linking. |
Audit supplied page HTML for on-page, duplication, and internal-link problems; costs $0.15 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pages | array | yes | Pages to audit; each requires url and html. |
Find missing contextually relevant internal links across supplied pages; costs $0.05 USDC.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | yes | — | |
| pages | array | yes | Two or more site pages with title and text for best results. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SEO Authority or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.3 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest1c9c32533aeea1a5b61f7680b39bea820b996a7108995b9cae355d9d9a1077dc
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest1c9c32533aeea1a5
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.3. Pin a release below and the command asks for exactly that one.
0.1.3
8 Oct 2026
latestNo release note was published with this version.
0.1.1
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish SEO Authority can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.