Mcp MCP Server

SitePulsar MCP Server

Agent Experience Optimization (AEO) for AI agents — measure and improve how findable, readable, and usable any website is to AI answer engines and autonomous AI agents, directly from your MCP client.

A remote, hosted Model Context Protocol server. There is nothing to build or run locally — connect your MCP client to the hosted endpoint and the 13 tools below become available.

Endpoint (streamable-http): https://mcp.sitepulsar.ai/mcp

---

What is SitePulsar / AEO?

SitePulsar is an Agent Experience Optimization (AEO) audit platform. It measures how findable, readable, and usable a website is to AI answer engines and autonomous AI agents, and returns one AEO score across three pillars:

• FIND — discoverability across ChatGPT, Claude, Gemini, Perplexity, and Grok.
• READ — comprehension, structured data, and trust signals.
• USE — agent-actionability (can an autonomous AI agent actually take action on the site?).

AEO is the agent-native successor to what used to be split as GEO + AIO. SitePulsar is agent infrastructure, not an SEO tool.

---

Quick start

The server supports two auth modes. Pick whichever fits your client.

Option A — OAuth (recommended for Claude; no API key)

Add SitePulsar as a custom connector in Claude using the endpoint. Claude walks you through the OAuth handshake; no API key needs to be stored.

• Endpoint: https://mcp.sitepulsar.ai/mcp
• OAuth protected-resource metadata: https://mcp.sitepulsar.ai/.well-known/oauth-protected-resource

Option B — Bearer API key (for headless / non-interactive clients)

Mint an MCP API key in the SitePulsar dashboard (Pro/Business plan), then send it on every request:

Authorization: Bearer <mcp_api_key>

See examples/headless-curl.md for raw HTTP usage.

---

Connect matrix

Cursor / Cline JSON config:

{
  "mcpServers": {
    "sitepulsar": {
      "url": "https://mcp.sitepulsar.ai/mcp"
    }
  }
}

A ready-to-paste config is in examples/claude_desktop_config.json.

For headless clients that cannot do interactive OAuth, add an Authorization: Bearer <mcp_api_key> header (see Option B above).

---

Tools

13 tools, grouped by pillar coverage. "Metered" tools run a billed audit/scan and require a Pro/Business plan; "Free" tools are read-only or lightweight probes.

Full machine-readable tool reference: llms.txt.

---

Authentication

SitePulsar accepts either of the following on the hosted endpoint.

OAuth

Used by interactive clients (e.g. Claude custom connectors). The server advertises its OAuth posture via RFC 9728 protected-resource metadata:

https://mcp.sitepulsar.ai/.well-known/oauth-protected-resource

Your client discovers the authorization server from that document and completes the handshake — no API key is stored on your side.

Bearer API key

Used by headless clients. Mint a key in the SitePulsar dashboard (Pro/Business plan) and send it on every request:

Authorization: Bearer <mcp_api_key>

Metered tools (run_audit, scan_visibility, and the metered path of scan_product_page) require a Pro/Business plan regardless of auth mode.

---

Links

• Website: https://www.sitepulsar.ai
• Tool reference (llms.txt): https://www.sitepulsar.ai/llms.txt
• Hosted MCP endpoint: https://mcp.sitepulsar.ai/mcp
• OAuth metadata: https://mcp.sitepulsar.ai/.well-known/oauth-protected-resource
• Listed in the official MCP registry as ai.sitepulsar/mcp (v1.0.0).

---

License

MIT — see LICENSE.

Built by

SitePulsar — EU-based (Netherlands). Founder & CEO: Gijs van Bueren. Questions: info@sitepulsar.ai.