Locus
REMOTE · API.LOCUS.REPORT · 2 COMPONENTS · SCANNED SEP 20
Official US-address public records: zoning, flood, parcel, permits, taxes. Free look, x402 paid.
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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
- Tool/resource definitions use about 475 tokens (~79/item across 6 items; 2 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Locus MCP server?
Locus is a hosted endpoint at https://api.locus.report/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.locus.report
claude mcp add --transport http velinussage-locus 'https://api.locus.report/mcp'
{
"mcpServers": {
"velinussage-locus": {
"url": "https://api.locus.report/mcp"
}
}
} {
"servers": {
"velinussage-locus": {
"type": "http",
"url": "https://api.locus.report/mcp"
}
}
} [mcp_servers.velinussage-locus] url = "https://api.locus.report/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"velinussage-locus": {
"type": "remote",
"url": "https://api.locus.report/mcp",
"enabled": true
}
}
} openclaw mcp add velinussage-locus --url 'https://api.locus.report/mcp' --transport streamable-http
mcp_servers:
velinussage-locus:
url: "https://api.locus.report/mcp" {
"McpServers": {
"velinussage-locus": {
"Transport": "http",
"Url": "https://api.locus.report/mcp"
}
}
} assistant mcp add velinussage-locus -t streamable-http -u 'https://api.locus.report/mcp'
{
"mcpServers": {
"velinussage-locus": {
"type": "http",
"url": "https://api.locus.report/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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +3
- Schema quality: fail → pass ▲ functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 100 functional
- New resource “locus-skill-paying-for-locus” functional
- New resource “locus-skill-choosing-a-locus-tool” functional
- New resource “locus-skill-locus-place-workflow” functional
- New resource “locus-skill-reading-locus-coverage” functional
- 13 Sept 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.
- 11 Sept 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.
- 10 Sept 26 −1
- Schema quality: 157 → 178 ▼ functional
- Schema quality: excellent → good functional
- “locus_execute” added an optional parameter “args” cosmetic
- “locus_execute” added an optional parameter “tool” cosmetic
- “locus_execute” added an optional parameter “input” cosmetic
- “locus_execute” reworded the description of “arguments” cosmetic
- “locus_execute” made “name” optional cosmetic
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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 20 Sept 2026 · Probed https://api.locus.report/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=locus.report | CN=WE1,O=Google Trust Services,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | f17ef57fae0f34b40e69daecc7ebfee9 |
| SANs: locus.report, api.locus.report, *.api.locus.report | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.locus.report. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| report. | present | 23221 | 8 | Verified |
| locus.report. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.locus.report/mcp | Verified | 200 | |
| http (plaintext) | http://api.locus.report/mcp | Inconclusive | 406 |
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 →
locus_execute Execute a Locus catalog tool ~189
Run one Locus catalog tool by name after locus_search_tools or a known tool name. Search and looking are free; this call may charge via MCP-native x402. Free tools return cited official-source primitives; paid tools return payment-required results and accept retry payment in _meta["x402/payment"]. Unsupported places return diagnostics instead of paid guesses. Do not use this for web scrape, LinkedIn, or generic fetch. Install agent skill: npx @velinussage/locus-agent-skill add.
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | Alias of arguments. |
| arguments | object | – | Arguments for the selected catalog tool (the tool's own inputSchema from locus_search_tools). |
| input | object | – | Alias of arguments. |
| name | string | – | Canonical Locus catalog tool name. Paid tools keep their hyphenated REST slugs. |
| tool | string | – | Alias of name. |
No output schema declared.
No examples provided.
locus_search_tools Search Locus tool catalog ~167
Every time the task is a US address or place and you need official public records or local-government context and you do not already know the tool name, search this catalog before locus_execute and before paying a generic scrape of the same official source. Looking is free. Results include full inputSchema, tier, price, and provenance notes. Do not use this for LinkedIn, web scrape, or generic fetch. Install agent skill: npx @velinussage/locus-agent-skill add.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matching catalog entries to return. |
| query | string | – | Keyword query over tool name, title, description, and tags. |
| tags | array | – | Optional tags that every result must include. |
| tier | string | – | Filter by free or paid tools. |
No output schema declared.
No examples provided.
What is the Locus MCP server?
Locus is an MCP server listed in the public MCP registry as io.github.velinussage/locus. Official US-address public records: zoning, flood, parcel, permits, taxes. Free look, x402 paid. This page covers its hosted endpoint (https://api.locus.report/mcp).
Is the Locus MCP server safe to use?
Locus scores 75 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 Locus MCP server expose?
Locus exposes 2 tools: locus_search_tools, locus_execute. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Does the Locus MCP server require authentication?
No. We connected to Locus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Locus MCP server still maintained?
Locus is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.