Skip to content
Laspi Pro logo

Laspi Pro MCP server

Which MCP servers are Laspi Pro's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to Laspi Pro

Whose server it is
  • Registry namepro.laspi/directoryverified in the MCP registry

The registry name sits under laspi.pro. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools3
  • Server calls itselflaspi-directory
  • Server version1.0.0
  • Protocol version2025-03-26

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 192 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: turn voice notes into social media posts and articles; publish posts to connected social networks on schedule.
  • Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 3, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
  • What an agent can do with it0 of 2 use cases
  • Answeredmeasuring3 of the 7 daily checks it takes to print a share
  • Median first answer307 ms
  • Space in an agent's context≈ 389 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 3 of 3

What an agent can do with it

  • cannot · turn voice notes into social media posts and articles
  • cannot · publish posts to connected social networks on schedule
  • not sure · write blog articles for a business website

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-26
  • search_businesses

    Search the Laspi Pro public business directory (small businesses: services, location, languages). Returns top matches with name, description, city, languages and the canonical page URL. Use the customer's own words as the query, e.g…

  • get_business

    Get the full public card of one business by its slug (from search results or a laspi.pro/b/{slug} URL): description, services, contacts, languages.

  • ask_directory

    Ask the directory a customer question in natural language. Returns schema.org cards of businesses that genuinely answer it (LLM-reranked, strictly from the directory — never invented) + grounding links. Use when the customer describes a…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "directory": {
      "type": "http",
      "url": "https://laspi.pro/api/v1/mcp/directory"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http laspi https://laspi.pro/api/v1/mcp/directory

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://laspi.pro/api/v1/mcp/directory as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.