bots.st/sitepulsar-ai
sitepulsar.ai
Run AEO/agent-readiness website audits and comparisons
2658 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-11-25
- Tools listed
- 13
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.sitepulsar.ai/mcp
What it can do
| Tool | What it says it does |
|---|---|
check_agent_readiness | 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. |
compare_aeo | 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. |
get_audit | 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. |
get_audit_detail | 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… |
get_audit_full | 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… |
get_fixes | 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… |
probe_agent_discovery | 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… |
probe_mcp_functional | 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… |
probe_ucp_readiness | 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… |
run_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. |
scan_product_page | 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: {… |
scan_visibility | 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… |
search_companies | 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… |
In its maker's words
SitePulsar AEO audits: fetch FIND/READ/USE agent-readiness scores for any website.
- Website
- www.sitepulsar.ai
- Source
- github.com/SitePulsar/mcp-server
- Publisher
- sitepulsar.ai
- Listed from
- the official MCP Registry as
ai.sitepulsar/mcp - Version
- 1.0.1, updated 10 Jun 2026
- Kinds of work
- Domains and websites, Search and research, Security and trust
The domain it lives on
- sitepulsar.ai
- registered 18 Feb 2026 (9 months ago), at whois.porkbun.com, its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2658 ms | |
| Answered | 2420 ms | |
| Answered | 480 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.