Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Laspi Business Directory

REMOTE · LASPI.PRO · SCANNED AUG 3

Search a directory of real, owner-confirmed small businesses. Read-only; attribution required.

Available components

+4 this week 67 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 293 tokens (~97/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · laspi.pro

# add to Claude Code
claude mcp add --transport http pro-laspi-directory https://laspi.pro/api/v1/mcp/directory
# ~/.codex/config.toml
[mcp_servers.pro-laspi-directory]
url = "https://laspi.pro/api/v1/mcp/directory"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pro-laspi-directory": {
      "type": "remote",
      "url": "https://laspi.pro/api/v1/mcp/directory",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add pro-laspi-directory --url https://laspi.pro/api/v1/mcp/directory --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  pro-laspi-directory:
    url: "https://laspi.pro/api/v1/mcp/directory"
// mcp.json
{
  "mcpServers": {
    "pro-laspi-directory": {
      "type": "http",
      "url": "https://laspi.pro/api/v1/mcp/directory"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://laspi.pro/api/v1/mcp/directory

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=laspi.pro CN=YR2,O=Let's Encrypt,C=US 14 Jun 2026 12 Sept 2026 RSA 2048 SHA256-RSA 54b34c0481590212b47a18b9a18afc58b0f
SANs: laspi.pro
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of laspi.pro. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pro. present 42154 8 Verified
laspi.pro. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), geolocation=(), microphone=(self)
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://laspi.pro/api/v1/mcp/directory Verified 200
http (plaintext) http://laspi.pro/api/v1/mcp/directory HTTPS enforced 301 https://laspi.pro/api/v1/mcp/directory
MCP tools — 3 exposed · ~251 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
ask_directory ~83

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 NEED rather than a search term.

NameTypeReqDescription
languagestringOptional service language filter (ISO code)
questionstringyesCustomer question

No output schema declared.

No examples provided.

get_business ~51

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.

NameTypeReqDescription
slugstringyesBusiness slug

No output schema declared.

No examples provided.

search_businesses ~117

Search the Laspi 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. 'manicure in Alicante' or 'online QA course in Russian'.

NameTypeReqDescription
citystringOptional city filter (substring)
languagestringOptional service language filter (ISO code)
nichestringOptional niche key filter
querystringyesNatural-language search query

No output schema declared.

No examples provided.