Loqal
REMOTE · API.LOQAL.COM.BR · SCANNED OCT 7
Profissionais de serviços locais no Brasil: encanador, eletricista, diarista e +270 tipos
Available components
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 → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1413 tokens (~128/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
- Structured output schemas are declared (20% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
How do I install the Loqal MCP server?
Loqal is a hosted endpoint at https://api.loqal.com.br/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.loqal.com.br
claude mcp add --transport http br-com-loqal-loqal 'https://api.loqal.com.br/mcp'
{
"mcpServers": {
"br-com-loqal-loqal": {
"url": "https://api.loqal.com.br/mcp"
}
}
} {
"servers": {
"br-com-loqal-loqal": {
"type": "http",
"url": "https://api.loqal.com.br/mcp"
}
}
} [mcp_servers.br-com-loqal-loqal] url = "https://api.loqal.com.br/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"br-com-loqal-loqal": {
"type": "remote",
"url": "https://api.loqal.com.br/mcp",
"enabled": true
}
}
} openclaw mcp add br-com-loqal-loqal --url 'https://api.loqal.com.br/mcp' --transport streamable-http
mcp_servers:
br-com-loqal-loqal:
url: "https://api.loqal.com.br/mcp" {
"McpServers": {
"br-com-loqal-loqal": {
"Transport": "http",
"Url": "https://api.loqal.com.br/mcp"
}
}
} assistant mcp add br-com-loqal-loqal -t streamable-http -u 'https://api.loqal.com.br/mcp'
{
"mcpServers": {
"br-com-loqal-loqal": {
"type": "http",
"url": "https://api.loqal.com.br/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “estimate_price” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 38% → 45% ▲ functional
- Server version: 0.1.0 → 1.1.0 functional
- New tool “estimate_job” functional
- 2 Oct 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.
- 1 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Sept 26 74
First indexed and scored.
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 7 Oct 2026 · Probed https://api.loqal.com.br/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.loqal.com.br | CN=YE1,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6dae8a8c8bb97d13b8da90cb3c88818e96e |
| SANs: api.loqal.com.br | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.loqal.com.br. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| br. | present | 38298 | 13 | Verified |
| com.br. | present | 2557 | 13 | Verified |
| loqal.com.br. | 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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.loqal.com.br/mcp | Verified | 200 | |
| http (plaintext) | http://api.loqal.com.br/mcp | HTTPS enforced | 308 | https://api.loqal.com.br/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_coverage Checar cobertura ~68
Diz se a Loqal reconhece um lugar (bairro, cidade, UF em todo o Brasil) e quantos profissionais reais atendem ali, no geral ou para uma necessidade. Use antes de prometer algo ao usuário.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | – | – |
| where | string | yes | – |
No output schema declared.
No examples provided.
compare_providers Comparar profissionais ~81
Compara lado a lado 2 a 6 profissionais (slugs) para uma necessidade: nota, avaliações, distância, preço informado, 24h, verificação. Não inventa: "não informado" quando a Loqal não sabe.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | – | – |
| slugs | array | yes | – |
| where | string | – | – |
No output schema declared.
No examples provided.
estimate_job Estimar o preço do caso ~238
Estima quanto vai custar um serviço específico descrito pelo usuário (ex.: "instalar ar split de 12 mil BTUs no 7º andar, sem infraestrutura, na Tijuca"), separando mão de obra, material e deslocamento, com as premissas e o que falta para refinar. Usa o Índice de Preços Loqal e preços reais publicados por profissionais quando existem (base=indice_loqal|precos_reais); sem eles, é uma referência de mercado (base=ia). É estimativa, não orçamento. Antes de chamar, se faltar o detalhe que mais muda o preço (tamanho, quantidade, m², BTUs), pergunte ao usuário.
| Name | Type | Req | Description |
|---|---|---|---|
| details | array | – | Respostas do usuário que mudam o preço, ex.: "12.000 BTUs", "7º andar" |
| need | string | yes | O caso com os detalhes do usuário |
| niche | string | – | slug do tipo de profissional (search_services/list_categories); se omitido, a Loqal entende pelo texto |
| where | string | – | Bairro e cidade, ou cidade e UF |
No output schema declared.
No examples provided.
estimate_price Estimar preço ~92
Faixa de preço de um serviço numa região, só com preços reais: dos profissionais perto (5 ou mais) ou do Índice de Preços Loqal (preços publicados pelos próprios negócios, por estado ou nacional; source=indice_loqal, com página de referência). Sem dados suficientes, diz que não há e não inventa valores.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | – |
| where | string | – | – |
No output schema declared.
No examples provided.
find_providers Encontrar profissionais ~342
Encontra profissionais reais perto de um lugar para uma necessidade. Ex.: need="instalar 3 ventiladores", where="Tijuca, Rio de Janeiro", min_rating=4.5, max_price_brl=350. Retorna perfis estruturados (nota, avaliações, distância, preço quando informado) e uma tela com cards.
| Name | Type | Req | Description |
|---|---|---|---|
| emergency_24h | boolean | – | Só quem atende 24 horas / emergência |
| lat | number | – | Latitude (busca geolocalizada: use com lng quando o usuário compartilhar a localização) |
| limit | integer | – | – |
| lng | number | – | – |
| max_price_brl | number | – | Mantém quem não informou preço (cobra por orçamento) |
| min_rating | number | – | – |
| min_reviews | integer | – | – |
| need | string | yes | O que o usuário precisa, com as palavras dele |
| niche | string | – | Slug exato do tipo de profissional (de list_categories), ex.: "motorista", "pedreiro". Quando informado, vence a interpretação do texto. |
| radius_km | number | – | Raio da busca em km a partir de lat/lng ou do lugar (padrão: 5 a 15 km conforme o lugar) |
| service | string | – | Subcategoria exata, a service_key de search_services (ex.: "piscina/limpeza"). Prioriza quem faz exatamente isso, sem esconder o resto do tipo. |
| sort | string | – | – |
| where | string | – | Bairro e/ou cidade, ex.: "Tijuca, Rio de Janeiro" ou "Pinheiros SP" |
| Name | Type | Req | Description |
|---|---|---|---|
| loqal_page | string|null | yes | – |
| providers | array | yes | – |
| related_niches | array | – | Presente quando o tipo pedido ainda não tem ninguém na região e a lista é de tipos afins |
| total | number | yes | – |
| understood | object | yes | – |
No examples provided.
get_provider Ver profissional ~61
Perfil completo de um profissional (slug vindo de find_providers): serviços com aliases e preço inicial, bairros atendidos, nota com a fonte, avaliações recentes, ações e o índice de preparo para IAs (agent_readiness).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_request Acompanhar pedido ~45
Situação de um pedido pelo código (LQ-XXXX): status e profissionais que receberam. Respostas de orçamento chegam no WhatsApp do usuário.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
list_categories Catálogo de serviços ~73
Setores e nichos da Loqal (285 tipos de serviço), com quantos profissionais reais atendem. Filtre por setor (slug) ou por lugar para ver só o que existe ali.
| Name | Type | Req | Description |
|---|---|---|---|
| sector | string | – | slug do setor, ex.: reformas-e-reparos |
| where | string | – | – |
No output schema declared.
No examples provided.
rate_service Avaliar serviço ~81
Registra a avaliação do usuário para um profissional que recebeu o pedido dele (código LQ-XXXX). Só aceita avaliação ligada a um pedido real: é o que torna a reputação da Loqal confiável.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| comment | string | – | – |
| provider | string | yes | slug |
| rating | integer | yes | – |
No output schema declared.
No examples provided.
search_services Descobrir o serviço certo ~61
Mapeia uma necessidade em linguagem natural ("cano da pia vazando", "limpar ar-condicionado") para os serviços da Loqal. Use quando não estiver claro qual profissional resolve.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | A necessidade, com as palavras do usuário |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | yes | – |
No examples provided.
What is the Loqal MCP server?
Loqal is an MCP server listed in the public MCP registry as br.com.loqal/loqal. Profissionais de serviços locais no Brasil: encanador, eletricista, diarista e +270 tipos. This page covers its hosted endpoint (https://api.loqal.com.br/mcp).
Is the Loqal MCP server safe to use?
Loqal scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Loqal MCP server expose?
Loqal exposes 10 tools: search_services, list_categories, check_coverage, find_providers, get_provider, and 5 more. Their descriptions and schemas cost roughly 1,142 tokens of context every time the server is loaded.
Does the Loqal MCP server require authentication?
No. We connected to Loqal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Loqal MCP server still maintained?
Loqal is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.