AI agents & MCP
prosurvey.app speaks the Model Context Protocol — connect an agent and it can read the site or send an enquiry.
Connect
https://prosurvey.app/mcp · JSON-RPC 2.0 over HTTPS (streamable-http) · no key requiredcurl -X POST https://prosurvey.app/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Tools
get_site_overview | Structured overview of this business/product (from its llms.txt). |
list_pages | List public pages (from the XML sitemap). |
read_page | Fetch a page on this site as Markdown. Arg: url. |
submit_enquiry | Send a contact enquiry to this business. Args: name, email, message. |
get_contact_and_data_rights | How to contact this business and exercise data rights (export/deletion). |
Questions
What is this?
prosurvey.app publishes a Model Context Protocol (MCP) server so AI agents and assistants can read the site and take a few safe actions on a visitor's behalf.
How do I connect?
Point any MCP client at https://prosurvey.app/mcp — JSON-RPC 2.0 over HTTPS (streamable-http). No API key or registration is required.
What can an agent do here?
get_site_overview, list_pages, read_page, submit_enquiry, get_contact_and_data_rights.
Do agents need to authenticate?
No. The tools are public and read-only, except submit_enquiry, which forwards a contact message.
How do I discover this automatically?
Fetch https://prosurvey.app/.well-known/mcp.json (server card), https://prosurvey.app/.well-known/agent-card.json (A2A Agent Card), https://prosurvey.app/.well-known/agent-skills/index.json (skills), or https://prosurvey.app/llms.txt. Every page also sends RFC 8288 Link headers pointing at these, and there is a DNS-AID record at _index._agents.prosurvey.app.
Do you support A2A?
Yes — a minimal A2A agent lives at https://prosurvey.app/a2a (JSON-RPC, message/send) and is described by the Agent Card at https://prosurvey.app/.well-known/agent-card.json. It answers with a site overview; use the MCP server for tools.