Empiria Local SEO
REMOTE · MCP.EMPIRIAINSIGHT.COM
Deterministic SEO/GEO checks, business-data comparisons and fixed-price implementation guidance.
Available components
Last scanned (23 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1127 tokens (~112/item across 10 items; 9 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 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 Nov 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 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 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.
- 10 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.
- 8 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.
- 6 Nov 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 21 Nov 2026 · Probed https://mcp.empiriainsight.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=empiriainsight.com | CN=YE1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 519bb270e7e70c5c33d7beeccd0870c76d4 |
| SANs: *.empiriainsight.com, empiriainsight.com | ||||||
| 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 mcp.empiriainsight.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| empiriainsight.com. | No DS | 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 |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.empiriainsight.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.empiriainsight.com/mcp | HTTPS enforced | 308 | https://mcp.empiriainsight.com/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 →
analyze_ai_observations Vorhandene KI-Beobachtungen auswerten ~98
Berechnet Nennungs-, Empfehlungs-, eigene Quellen- und Zitationsquoten aus gelieferten annotierten Antwortprotokollen. Trennt Oberfläche, Modell, Modus, Sprache und Ort. Weist Nenner, Fehlversuche und ungeprüfte Annotationen aus. Führt keine KI-Anfragen durch und beurteilt keine Texte semantisch.
| Name | Type | Req | Description |
|---|---|---|---|
| observations | array | yes | – |
| owned_hosts | array | yes | – |
No output schema declared.
No examples provided.
analyze_performance_export Messdaten und Baseline prüfen ~85
Validiert gelieferte GSC-/GBP-/CRM-ähnliche Datensätze, Definitionen und doppelte IDs. Summiert getrennte Kennzahlen und berechnet Veränderungen nur bei vergleichbarer Baseline. Kein Zugriff auf Konten und keine automatische Zuordnung von KI-Traffic oder Umsatzursachen.
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | – | – | – |
| current | object | yes | – |
No output schema declared.
No examples provided.
analyze_web_performance Gelieferte Web-Performance-Messung prüfen ~145
Trennt Labor- und Felddaten. Prüft gelieferte p75-Feldwerte getrennt nach Gerät gegen gute LCP-/INP-/CLS-Grenzen und listet große Ressourcen im gelieferten Trace. Führt keine Messung aus und berechnet keinen pauschalen SEO-Score.
| Name | Type | Req | Description |
|---|---|---|---|
| device | string | yes | – |
| kind | string | yes | – |
| metrics | object | yes | – |
| observed_at | string | yes | – |
| percentile | number | – | – |
| period_end | string | – | – |
| period_start | string | – | – |
| resources | array | – | – |
| source | string | yes | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
audit_page_snapshot Gespeicherten Seitenstand prüfen ~167
Prüft geliefertes HTML und optionale HTTP-/robots-/Sitemap-/DOM-Snapshots ohne Netzwerkzugriff. Gleiche Eingaben und Regelversion ergeben gleiche Befunde. Fehlende Daten bleiben not_tested; ein DOM-Snapshot ist kein eigener Browser-Test.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_business | object | – | – |
| headers | object | – | – |
| html | string | yes | – |
| llms | – | – | – |
| observed_at | string | – | – |
| paid_link_urls | array | – | – |
| redirect_chain | array | – | – |
| related_pages | array | – | – |
| rendered_html | string | – | – |
| robots | object | – | – |
| sitemap | – | – | – |
| status_code | integer | – | – |
| target_results | array | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
audit_website Öffentliche Website prüfen ~121
Begrenzter HTTP-Crawl einer öffentlichen Website: HTML, Kontaktlinks, Schema, robots, Sitemap. Maximal sechs Seiten und 20 weitere interne Ziele, 45 Sekunden Gesamtbudget. Respektiert robots für den eigenen Audit-Crawler. Kein Browser oder echter Suchbot-Test; externe Buchungsseiten bleiben ungeprüft. Führt öffentliche GET-Abrufe durch, speichert keine Leads.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_business | object | – | – |
| max_link_checks | integer | – | – |
| max_pages | integer | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
compare_business_profiles Unternehmensdaten abgleichen ~91
Vergleicht gelieferte Profil-/Verzeichnisdaten gegen freigegebene Stammdaten: Name, Rufnummern, öffentliche Adresse, Standort-URL, Zeiten, Gebiete, Kategorien und Leistungen. Normalisiert Schreib-/Telefonvarianten; prüft weder Google-Profil live noch Inhaberschaft oder Wahrheit der Stammdaten.
| Name | Type | Req | Description |
|---|---|---|---|
| profiles | array | yes | – |
| reference | object | yes | – |
No output schema declared.
No examples provided.
estimate_remediation Passende Festpreispakete einordnen ~75
Passende Leistungspakete mit vorläufigem Netto-Festpreis und klar begrenztem Umfang aus gelieferten Prüfregel-IDs ableiten. Keine Stundenangaben. Warnungen müssen bestätigt werden; ein verbindliches Festpreisangebot folgt nach Prüfung. Keine Ranking- oder Terminzusage.
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | – | – |
No output schema declared.
No examples provided.
get_check_catalog Prüfkatalog und Grenzen ~29
Liste der deterministischen Regeln mit Version, Skill-Herkunft, Quellen und Prüfgrenzen.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
summarize_local_competitors Lokale Wettbewerbsstichprobe auswerten ~77
Prüft Herkunft und doppelte IDs eines gelieferten lokalen Wettbewerbervergleichs und berechnet Minimum, Median und Maximum vorhandener Ratings/Bewertungszahlen. Keine Live-Maps-Abfrage, Review-Authentizitätsprüfung oder Aussage über das Marktminimum.
| Name | Type | Req | Description |
|---|---|---|---|
| businesses | array | yes | – |
| context | object | yes | – |
No output schema declared.
No examples provided.
How do I install the Empiria Local SEO MCP server?
Empiria Local SEO is a hosted endpoint at https://mcp.empiriainsight.com/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 · mcp.empiriainsight.com
claude mcp add --transport http com-empiriainsight-local-seo-geo 'https://mcp.empiriainsight.com/mcp'
What is the Empiria Local SEO MCP server?
Empiria Local SEO is an MCP server listed in the public MCP registry as com.empiriainsight/local-seo-geo. Deterministic SEO/GEO checks, business-data comparisons and fixed-price implementation guidance. This page covers its hosted endpoint (https://mcp.empiriainsight.com/mcp).
Is the Empiria Local SEO MCP server safe to use?
Empiria Local SEO scores 76 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 Empiria Local SEO MCP server expose?
Empiria Local SEO exposes 9 tools: get_check_catalog, audit_website, audit_page_snapshot, compare_business_profiles, analyze_ai_observations, and 4 more. Their descriptions and schemas cost roughly 888 tokens of context every time the server is loaded.
Does the Empiria Local SEO MCP server require authentication?
No. We connected to Empiria Local SEO without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Empiria Local SEO MCP server still maintained?
Empiria Local SEO is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Empiria Local SEO MCP server?
VerifyMCP ran 13 checks on Empiria Local SEO, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.