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

LocalSchema

REMOTE · LOCAL-SCHEMA-BEACON.LOVABLE.APP

Generate and validate LocalBusiness JSON-LD for local SEO. Free tools, no key needed.

74 Trust /100

Last scanned (21 minutes ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1602 tokens (~145/item across 11 items; 11 tools + 0 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 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
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.

  • 4 Nov 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.

  • 2 Nov 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.

  • 31 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 30 Oct 26 71

    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 5 Nov 2026 · Probed https://local-schema-beacon.lovable.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lovable.app CN=WE1,O=Google Trust Services,C=US 10 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA256 a0305f14b2a99af130a9e43af07d3e5
SANs: lovable.app, *.lovable.app
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 local-schema-beacon.lovable.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
lovable.app. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://local-schema-beacon.lovable.app/mcp Verified 200
http (plaintext) http://local-schema-beacon.lovable.app/mcp HTTPS enforced 301 https://local-schema-beacon.lovable.app/mcp
MCP tools · 11 exposed · ~1,326 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. 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 →

Tool Tokens
generate_schema ~423

Generate LocalBusiness JSON-LD (schema.org) from business details and validate it against Google's rich result rules. Returns the JSON-LD, a ready-to-paste <script> tag and issues to fix. No API key needed.

NameTypeReqDescription
acceptsReservationsboolean––
addressobject––
alternateNamestring––
areaServedarray––
businessTypestring–schema.org type, e.g. Dentist, Plumber, Restaurant. See /business-types.
currenciesAcceptedarray––
descriptionstring––
emailstring––
foundingDatestring––
geoobject––
hasMapstring––
imagesarray––
isAcceptingNewPatientsboolean––
knowsLanguagearray––
legalNamestring––
logostring––
medicalSpecialtystring––
menustring––
namestringyesPublic business name
openingHoursarray–Regular hours. Days not listed are closed. Use two entries for split hours.
paymentAcceptedarray––
priceRangestring–e.g. €€ or €20-€80
ratingobject–LocalSchema Pro — omitted from free output
reviewsarray–LocalSchema Pro — omitted from free output
sameAsarray–Google Business Profile, Yelp, Facebook, LinkedIn… profile URLs
servesCuisinearray––
serviceAreaOnlyboolean–True for service-area businesses without a storefront (address is hidden)
servicesarray––
sloganstring––
specialHoursarray–Holiday exceptions (LocalSchema Pro — omitted from free output)
telephonestring–International format, e.g. +31 50 123 4567
urlstring–Website URL (https://…)

No output schema declared.

No examples provided.

get_embed_snippet ~64

Get the install snippet and live status for a LocalSchema hosted embed key (loc_… for one location, org_… for a client with several). Paste the script tag once; published updates reach the site automatically.

NameTypeReqDescription
keystringyesHosted embed key

No output schema declared.

No examples provided.

get_location ~68

Get one saved location: its business fields (in the same shape save_location accepts), the current JSON-LD, the published JSON-LD, validation issues and embed details. Needs a LocalSchema Pro API key in the request headers.

NameTypeReqDescription
location_idstringyesLocation id from list_locations

No output schema declared.

No examples provided.

list_business_types ~40

List the schema.org LocalBusiness subtypes LocalSchema supports (Dentist, Plumber, Restaurant, …). Use the most specific one as businessType.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_clients ~43

List the agency's clients (brands) with their location counts, client-wide embed script and white-label report link. Needs a LocalSchema Pro API key in the request headers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_locations ~57

List the business locations saved in the LocalSchema account: publish state, hosted embed script, website and latest health check score. Needs a LocalSchema Pro API key in the request headers.

NameTypeReqDescription
client_idstring–Only this client's locations

No output schema declared.

No examples provided.

run_health_check ~74

Run a schema health check for a saved location: validates its markup, scans its website for the embed and conflicting hard-coded schema, detects unpublished changes and records the result in the dashboard and client reports. Needs a LocalSchema Pro API key in the request headers.

NameTypeReqDescription
location_idstringyesLocation id from list_locations

No output schema declared.

No examples provided.

save_client ~196

Create a client (brand) or update one by client_id, and optionally turn its white-label health report link on or off. Needs a LocalSchema Pro API key in the request headers.

NameTypeReqDescription
client_idstring–Update this client. Omit to create one.
contact_emailstring–Contact email. When updating, omit to keep it or send "" to clear it.
contact_namestring–Contact person. When updating, omit to keep it or send "" to clear it.
namestring–Client (brand) name. Required when creating; omit to keep it when updating.
reportboolean–true turns the client's white-label health report link on, false turns it off. Omit to leave it.
websitestring–Brand website; links every branch to one Organization in the client embed. When updating, omit to keep it or send "" to clear it.

No output schema declared.

No examples provided.

save_location ~214

Save a business location to the LocalSchema account — create one, or update one by location_id (only the business fields you send change) — and optionally publish it to its hosted embed so the client's site updates without code changes. Needs a LocalSchema Pro API key in the request headers.

NameTypeReqDescription
businessobjectyesBusiness fields in the same shape as generate_schema (name, businessType, address, openingHours, services, …). When updating, only the fields you send change; address merges field by field, lists are…
client_id––Assign to a client (see list_clients); null removes the assignment. Omit to keep the current client.
location_idstring–Update this location. Omit to create a new one (counts toward the plan's location limit).
publishboolean–Publish to the hosted embed now. Default false (saved as a draft).
website_url––Page where the hosted embed is installed; health checks scan it. Defaults to business.url.

No output schema declared.

No examples provided.

validate_page ~72

Fetch a public web page and audit its structured data: every JSON-LD block and type, the LocalBusiness markup's errors and warnings, LocalSchema embeds on the page and concrete recommendations. No API key needed.

NameTypeReqDescription
urlstringyesPublic http(s) address, e.g. https://example.com/contact

No output schema declared.

No examples provided.

validate_schema ~75

Validate existing LocalBusiness structured data: paste JSON-LD, a <script type="application/ld+json"> tag or a whole HTML page. Reports errors, missing recommended fields and best-practice warnings. No API key needed.

NameTypeReqDescription
codestringyesJSON-LD text, a script tag, or full page HTML

No output schema declared.

No examples provided.

Install

How do I install the LocalSchema MCP server?

LocalSchema is a hosted endpoint at https://local-schema-beacon.lovable.app/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 · local-schema-beacon.lovable.app

# add to Claude Code
claude mcp add --transport http app-lovable-local-schema-beacon-localschema 'https://local-schema-beacon.lovable.app/mcp'
Common questions

What is the LocalSchema MCP server?

LocalSchema is an MCP server listed in the public MCP registry as app.lovable.local-schema-beacon/localschema. Generate and validate LocalBusiness JSON-LD for local SEO. Free tools, no key needed. This page covers its hosted endpoint (https://local-schema-beacon.lovable.app/mcp).

Is the LocalSchema MCP server safe to use?

LocalSchema scores 74 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 LocalSchema MCP server expose?

LocalSchema exposes 11 tools: list_business_types, generate_schema, validate_schema, validate_page, get_embed_snippet, and 6 more. Their descriptions and schemas cost roughly 1,326 tokens of context every time the server is loaded.

Does the LocalSchema MCP server require authentication?

No. We connected to LocalSchema without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LocalSchema MCP server still maintained?

LocalSchema is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.