Index / MCP servers / Sitepulsar

Sitepulsar MCP server

Sitepulsar is a remote MCP server that gives an AI agent 13 tools, among them check_agent_readiness, compare_aeo, get_audit. It answers at https://mcp.sitepulsar.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.

Status
Answering
Tools
13
Official
yes, served from sitepulsar.ai
Reliability
10 of 10 checks
Response time
206 ms
Transport
streamable HTTP
Last checked
17 October 2026

SitePulsar AEO audits: fetch FIND/READ/USE agent-readiness scores for any website.

Description as the publisher wrote it.

The 13 tools Sitepulsar offers

ToolWhat it does
check_agent_readinessFast 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 de
Inputs: url
compare_aeoCompare 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
Inputs: urls
get_auditFetch 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 y
Inputs: audit_id
get_audit_detailFull 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/sc
Inputs: audit_id
get_audit_fullOne 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' | 'de
Inputs: audit_id, expand
get_fixesReturn 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
Inputs: audit_id
probe_agent_discoveryChecks 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
Inputs: url, brand
probe_mcp_functionalDiscovers 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
Inputs: url, brand
probe_ucp_readinessInspects /.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.
Inputs: url, brand
run_auditRun 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,
Inputs: url, target_keyword
scan_product_pageDeterministically 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 tha
Inputs: url, brand
scan_visibilityLive 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
Inputs: url, brand
search_companiesSamples 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 menti
Inputs: query

Add Sitepulsar to your AI client

Every block below points at https://mcp.sitepulsar.ai/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http sitepulsar https://mcp.sitepulsar.ai/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "sitepulsar": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.sitepulsar.ai/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "sitepulsar": {
      "url": "https://mcp.sitepulsar.ai/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "sitepulsar": {
      "type": "http",
      "url": "https://mcp.sitepulsar.ai/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "sitepulsar": {
      "url": "https://mcp.sitepulsar.ai/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "sitepulsar": {
      "serverUrl": "https://mcp.sitepulsar.ai/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "sitepulsar": {
      "url": "https://mcp.sitepulsar.ai/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Sitepulsar
version: 0.0.1
schema: v1
mcpServers:
  - name: Sitepulsar
    type: streamable-http
    url: https://mcp.sitepulsar.ai/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "sitepulsar": {
      "httpUrl": "https://mcp.sitepulsar.ai/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "sitepulsar": {
      "type": "http",
      "url": "https://mcp.sitepulsar.ai/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "sitepulsar": {
      "url": "https://mcp.sitepulsar.ai/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.sitepulsar.ai%2Fmcp&type=streamable_http&id=sitepulsar&name=Sitepulsar

Is Sitepulsar up right now?

It answered our last check on 17 October 2026 in 206 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Sitepulsar

Questions about Sitepulsar

Is there an official Sitepulsar MCP server?

Yes. It is published by sitepulsar.ai and served from mcp.sitepulsar.ai, the vendor's own domain: https://mcp.sitepulsar.ai/mcp.

How many tools does Sitepulsar have?

13, as returned by the server's own tools/list on 8 September 2026: check_agent_readiness, compare_aeo, get_audit, get_audit_detail, get_audit_full, get_fixes, probe_agent_discovery, probe_mcp_functional, and 5 more.

Is Sitepulsar down?

It answered our last check on 17 October 2026 in 206 ms. Over 10 checks since 4 September 2026 it answered 10.

How do I add Sitepulsar to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.sitepulsar.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Sitepulsar need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: ai.sitepulsar. Endpoint host: mcp.sitepulsar.ai. ARD identifier: urn:air:ai.sitepulsar:mcp:mcp. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.