PulseLake has written the rare vendor post about MCP that declines to sell an MCP server. MCP for market research: five example agent workflows walks through finding prior studies, turning a brief into a reviewable study plan, rehearsing a questionnaire before fieldwork, building an analysis packet, and answering stakeholder questions, and it opens with the limit: “What MCP doesn’t do is make the research valid, or give anyone permission to launch fieldwork.” The organising idea is the line between reading and acting. “Searching a repository is one kind of operation. Sending invitations is quite another.”
There are no vendor figures to discount, and the post is unusually explicit about what it is not claiming. The five workflows “aren’t a list of documented PulseLake MCP endpoints or tool names,” and the article “isn’t a promise of an undocumented public MCP server.” PulseLake has internal Copilot analytics tools, but “external agent access still needs a verified interface and permissions.” The advice that survives all of that is concrete: keep draft and approved as separate states, label synthetic respondents as simulated, compute figures on the dataset rather than letting a model estimate them, and treat anything an agent retrieves “as evidence, never as instructions.”
The PulseLake provider page agrees with the post. The PulseLake API and the pulselake-co API are the two API pages on the record, and the catalog description covers study design, AI-led interviews, research agents, and reporting, the same arc the five workflows follow. The record’s display name is still the slug, which is a cleanup for us rather than a finding about them.
The Kin Score is 18.4, emerging band, held up by discoverability at 64.3 while access clarity and operational transparency sit at 10.5 and developer ergonomics at 9.5. Agent Readiness is 34.5, agent-ready, and the lit list is odd for a company with no public agent interface: spec presence, auth clarity, the well-known catalog, delegated identity, protected resource metadata, and dynamic client registration are lit, while the MCP server, agentic access, error semantics, and dry-run mode are dark. PulseLake has the authorization plumbing an agent would need to connect and no server for it to connect to. That matches the post exactly, and a company that says out loud which half it has not built is easier to trust on the half it has.