Google Search Console integration for Model Context Protocol (MCP)
Sitepulsar AI MCP 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.
What it does
SitePulsar AEO audits: fetch FIND/READ/USE agent-readiness scores for any website.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mcp-sitepulsar-ai-mcp https://mcp.sitepulsar.ai/mcp
# 2 — ask your agent for something these tools do
# check_agent_readiness, run_audit, get_audit and 10 more
Sitepulsar AI MCP costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mcp-sitepulsar-ai-mcp https://mcp.sitepulsar.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
13 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.
Fast synchronous AEO / agent-readiness read of a single URL: robots and bot access, structured data (schema), and content structure. Returns immediate signals without running a full audit. Use this to triage a page or sanity-check before deciding whether the heavier run_audit is worth a credit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute URL to audit. |
Run a full AEO audit of a URL covering FIND, READ, and USE. Async: returns an audit_id to poll with get_audit. Accepts an optional target_keyword. Spends one audit credit per fresh run; a same-URL re-run within 24h reuses the cached audit, uncharged.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute URL to audit. |
| target_keyword | string | no | Optional keyword to evaluate against; inferred when absent. |
Fetch an audit's status and, when complete, a compact decision-ready SUMMARY: AEO score (overall + FIND/READ/USE), a short summary, the weakest pillar, headline takeaways, and the top fixes. Lead with this; call get_audit_detail only when you need the full per-section breakdown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | yes | The audit_id returned by run_audit / compare_aeo (poll until status is completed). |
Full structured per-section breakdown of a completed audit, on demand (only call after get_audit when you need depth): per-dimension FIND/READ/USE sub-scores, reputation across AI engines, competitor cluster (named for paid tiers), crawl/schema/robots findings, agentic-readiness + USE functional probes, and rendered-DOM analysis (paid). Typed, sanitized, size-capped (see truncated/dropped_sections
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | yes | The audit_id returned by run_audit / compare_aeo (poll until status is completed). |
Compare AEO posture across multiple URLs (e.g. a brand versus its competitors) on the same FIND/READ/USE pillar scale. Async: returns an audit_id to poll with get_audit. Spends credits only for freshly-audited URLs; recent audits are reused uncharged.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | Absolute URLs to compare. |
Return the prioritized, pillar-tagged (FIND / READ / USE) action plan for a completed audit, deduplicated across sources, with machine-actionable implementation steps included on fixes where available. Use this when you want the to-do list to act on (or hand to a coding agent), rather than the scores or section detail.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | yes | The audit_id returned by run_audit / compare_aeo (poll until status is completed). |
One call that returns a completed audit's SUMMARY, full per-section DETAIL, and deduplicated prioritized FIXES together — so you don't have to chain get_audit → get_audit_detail → get_fixes. Use expand to trim the payload ('summary' | 'detail' | 'fixes' | 'all'; default 'all'). Same ownership, tier gating, and sanitization as those tools. For an in-progress audit it returns the status so you can
| Parameter | Type | Required | Notes |
|---|---|---|---|
| audit_id | string | yes | The audit_id returned by run_audit / compare_aeo (poll until status is completed). |
| expand | string | no | Which sections to include; default 'all'. |
Samples the major AI engines for which companies they name for a query (e.g. "best CRM for startups"); returns a consensus shortlist (≤5). Use when you want to know who agents *recommend* for a category — not where a specific brand is mentioned (use scan_visibility for that). Free, no URL needed. Result: { companies[], tool_schema_version }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Natural-language search query (3–200 chars). |
Checks selected registries (official MCP registry, PyPI, GitHub) for packages/servers tied to a domain or brand. A discovery-surface check (can agents find your published tooling?), not a visibility check. Use when you want to know whether a brand has discoverable agent/developer artifacts listed where agents look for them. Result: { state, score, tier, hits[], tool_schema_version }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute https URL of the target (any public domain). |
| brand | string | no | Optional brand/company name; inferred from the domain when absent. |
Inspects /.well-known/ucp to report whether AI shopping agents can transact with the site (presence + advertised capabilities only — never a live purchase). Use when evaluating an e-commerce or merchant site for agentic-commerce readiness. Result: { has_ucp_profile, capabilities[], score, tool_schema_version }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute https URL of the target (any public domain). |
| brand | string | no | Optional brand/company name; inferred from the domain when absent. |
Discovers a site's advertised MCP endpoint (mcp.json / .well-known) and inspects its *declared* OAuth/transport posture (advertised, not guaranteed-working — it does not run a full live handshake). Use when checking whether a site exposes a connectable MCP server and what it claims to support. Result: { handshake_ok, declared_endpoint, declared_tool_names[], score, tool_schema_version }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute https URL of the target (any public domain). |
| brand | string | no | Optional brand/company name; inferred from the domain when absent. |
Deterministically scores one product page (schema, price, availability, image) 0–100 for shopping-agent readability — no LLM, fully repeatable. Use when you want a precise, single-page readability score for a specific product URL rather than a whole-site audit. Available on Pro+ plans. Result: { result: { readability_score, ... }, tool_schema_version }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute https URL of the target (any public domain). |
| brand | string | no | Optional brand/company name; inferred from the domain when absent. |
Live AI-visibility scan for a brand: crawl + reputation sampled across AI engines, returning where *that* brand is mentioned (any public brand, not just your own). Use when you want to know whether and how a named brand already surfaces in AI answers — complementary to search_companies, which finds who agents recommend for a category. Pro+ (LLM cost). Result: { reputation[], tool_schema_version }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Absolute https URL of the target (any public domain). |
| brand | string | no | Optional brand/company name; inferred from the domain when absent. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Sitepulsar AI MCP or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.0.1.
No release note was published with this version.
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.
Any signed-in account that does not publish Sitepulsar AI MCP can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.