Engagemii AI Visibility Data
REMOTE · API.ENGAGEMII.COM
AI visibility of 82M+ companies: scores, AI crawler reads, full records. Free 500 and 1M datasets.
Available components
Last scanned (15 hours ago)
Scores higher than 83% 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 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. 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
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2743 tokens (~211/item across 13 items; 13 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 Management96
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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
- Structured output schemas are declared (100% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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 88 to 96.
- 20 Nov 26 0
- Tool “data_orders” rewrote its description, which is the text the model reads security
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “citation_watch” rewrote its description, which is the text the model reads security
- Tool “connect_tracker” rewrote its description, which is the text the model reads security
- Tool “data_records” rewrote its description, which is the text the model reads security
- Tool “aeo_audit” now declares an output schema ▲ functional
- Tool “aeo_score” now declares an output schema ▲ functional
- Tool “ai_readstream” now declares an output schema ▲ functional
- Tool “brand_profile” now declares an output schema ▲ functional
- Tool “citation_watch” now declares an output schema ▲ functional
- Tool “connect_tracker” now declares an output schema ▲ functional
- Tool “data_orders” now declares an output schema ▲ functional
- Tool “data_records” now declares an output schema ▲ functional
- Tool “data_signup” now declares an output schema ▲ functional
- Tool “dataset_sample” now declares an output schema ▲ functional
- Tool “free_kit” now declares an output schema ▲ functional
- Tool “kit_download” now declares an output schema ▲ functional
- Tool “search_companies” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Server version: 1.2.2 → 1.3.0 functional
- “citation_watch” added an optional parameter “engine” cosmetic
- “citation_watch” added an optional parameter “kind” cosmetic
- “citation_watch” added an optional parameter “topic” cosmetic
- “citation_watch” reworded the description of “category” cosmetic
- “connect_tracker” reworded the description of “email” cosmetic
- “connect_tracker” reworded the description of “platform” cosmetic
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “data_signup” rewrote its description, which is the text the model reads security
- 17 Nov 26 +1
- Tool coverage: 76% → 100% ▲ functional
- Server version: 1.2.0 → 1.2.2 functional
- “brand_profile” reworded the description of “domain” cosmetic
- “data_records” reworded the description of “scope” cosmetic
- “data_records” reworded the description of “scoreMax” cosmetic
- “data_records” reworded the description of “scoreMin” cosmetic
- “kit_download” reworded the description of “session_id” cosmetic
- “search_companies” reworded the description of “scoreMax” cosmetic
- “search_companies” reworded the description of “scoreMin” cosmetic
- “search_companies” reworded the description of “states” cosmetic
- 16 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 166 → 184 ▼ functional
- 15 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “aeo_score” rewrote its description, which is the text the model reads security
- Tool “data_records” rewrote its description, which is the text the model reads security
- Tool coverage: 66% → 76% ▲ functional
- Schema quality: good → excellent functional
- “data_records” added an optional parameter “acceptUnitsPerRow” cosmetic
- “data_records” added an optional parameter “countries” cosmetic
- “data_records” added an optional parameter “offset” cosmetic
- “data_records” added an optional parameter “publicCompanies” cosmetic
- “data_records” reworded the description of “industries” cosmetic
- “data_records” reworded the description of “limit” cosmetic
- “data_records” reworded the description of “states” cosmetic
- 14 Nov 26 0
- Server version: 1.0.0 → 1.2.0 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://api.engagemii.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.engagemii.com | CN=YE1,O=Let's Encrypt,C=US | 6 Oct 2026 | 4 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5dcb5b973d2ac1f4b3cf08d26cedb06770a |
| SANs: api.engagemii.com, engagemii.com, standby-api.engagemii.com, standby.engagemii.com, www.engagemii.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 api.engagemii.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| engagemii.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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';script-src 'self' 'unsafe-inline' https://accounts.google.com https://apis.google.com;frame-ancestors 'self' https://*.myshopify.com https://myshopify.com;frame-src 'self' https://accounts.google.com;connect-src 'self' https://accounts.google.com https: wss:;img-src 'self' data: https:;base-uri 'self';font-src 'self' https: data:;form-action 'self';object-src 'none';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| 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://api.engagemii.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.engagemii.com/api/mcp | HTTPS enforced | 301 | https://api.engagemii.com/api/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 →
aeo_audit Run a live AI visibility audit ~111
Run a LIVE AEO audit of a site right now: fresh fetch of the homepage, robots.txt, sitemap, llms.txt, and about page, scored on the six on-page categories with concrete recommendations. Differs from aeo_score, which returns the stored score from the index; that score updates when Engagemii next reads the site. Free, no auth, up to 5 live audits per hour.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain or URL, e.g. example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| domain | string | – | – |
| profileUrl | string | – | – |
| recommendations | array | – | – |
| score | number | – | The score the brand page shows (blended) when scoreIsBlended, else the on-page scan |
| scoreIsBlended | boolean | – | – |
| shellDetected | boolean | – | – |
| shellMessage | string|null | – | – |
| shellReason | string|null | – | – |
| slug | string | – | – |
| summary | string | – | – |
| url | string | – | – |
| verdict | string | – | – |
No examples provided.
aeo_score Get a company's AI visibility score ~93
Get the Engagemii AEO score (0-10) for any company domain, with the six on-page and six off-page signals each rated Weak, Fair, Good or Strong, and the llms.txt audit verdict. Drawn from the Engagemii Index of more than 81 million companies. Free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain or URL, e.g. example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| aeoScore | number|null | – | AI visibility score, 0 to 10; null when no score is available |
| businessCategory | string|null | – | – |
| companyName | string | – | – |
| disclaimer | string | – | – |
| domain | string | – | – |
| found | boolean | yes | – |
| lastChecked | string|null | – | – |
| llmsTxtAudit | string|null | – | – |
| message | string | – | – |
| note | string | – | – |
| offPage | object|null | – | – |
| onPage | object|null | – | – |
| profileUrl | string|null | – | – |
| scoredAt | string|null | – | – |
| siteStatus | string|null | – | – |
| youCanGet | string | – | – |
No examples provided.
ai_readstream See which AI engines are reading company pages ~117
Which AI engines are reading the business web right now. Server-side, IP-verified crawler logs across one of the largest networks of business pages online. Returns per-engine reads over the last ten minutes, the last 24 hours and all time, plus a daily series. Free, no auth. Answers questions such as which AI crawler is most active, how two engines compare, and whether AI reading is rising.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | How many days of the daily series to return, 0 to 30. Default 7. |
| Name | Type | Req | Description |
|---|---|---|---|
| daily_series | array | – | – |
| engines | array | – | – |
| error | string | – | – |
| note | string | – | – |
| updated_at | string|null | – | – |
No examples provided.
brand_profile Get a company's public profile ~62
Full public profile for a scored company: score breakdown, category, geography, detected platform, social profiles, AI-crawler visit counts. Free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The company's website, e.g. example.com (a full URL is accepted) |
| Name | Type | Req | Description |
|---|---|---|---|
| aeoScore | number|null | – | AI visibility score, 0 to 10; null when no score is available |
| aiBotHitsTotal | number | – | – |
| aiBotsSeen | array | – | – |
| businessCategory | string|null | – | – |
| city | string | – | – |
| companyName | string | – | – |
| country | string | – | – |
| detectedPlatform | string | – | – |
| disclaimer | string | – | – |
| domain | string | – | – |
| found | boolean | yes | – |
| lastChecked | string|null | – | – |
| llmsTxtAudit | string|null | – | – |
| message | string | – | – |
| note | string | – | – |
| offPage | object|null | – | – |
| onPage | object|null | – | – |
| profileUrl | string|null | – | – |
| scoredAt | string|null | – | – |
| siteStatus | string|null | – | – |
| socials | object | – | – |
| state | string | – | – |
| youCanGet | string | – | – |
No examples provided.
citation_watch See which brands AI is recommending ~285
Which brands AI assistants name right now. Every 30 minutes from 6am to 11pm ET, Engagemii puts a real question that names no brand to ChatGPT, Meta AI and Gemini with live web search and records the first brand each names, alongside that brand's standing AI visibility score (computed before the question was asked). Most checks ask about what is trending on Google (kind trending); about 1 in 4 is a buying question in a business category (kind buying). Returns checks from the last 48 hours, newest first, each naming its engine. Filter by business category (for example Technology or Legal), by words in the question (topic, for example crm), by engine or by kind. Free, no auth.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Business category, case-insensitive substring, e.g. Legal, Technology, Finance & Insurance, Trending. Not a topic: use topic for words in the question. |
| engine | string | – | Only checks put to this engine. |
| kind | string | – | buying: a fixed buying question by category; trending: a question about what is trending on Google. |
| limit | number | – | How many checks to return, 1 to 50. Default 20. |
| topic | string | – | Words that must appear in the question, case-insensitive, e.g. crm or help desk. |
| Name | Type | Req | Description |
|---|---|---|---|
| cadence | string | – | – |
| categories_available | array | – | – |
| checks | array | – | – |
| checks_in_window | number | – | – |
| engines | array | – | – |
| error | string | – | – |
| matched | number | – | – |
| no_match | string | – | – |
| note | string | – | – |
| stats | object | – | – |
| window | string | – | – |
No examples provided.
connect_tracker Set up AI crawler monitoring ~234
Set up Engagemii AI-crawler monitoring for a site the user owns. The tracker key goes only to the verified owner of the site: if the email given is the site's verified owner, Engagemii emails it the site's tracker key and install steps (Node/Express, Next.js, PHP, Cloudflare Worker or WordPress); the key is never returned in the chat, and a site has one key. Otherwise the answer explains how to claim and verify the site at engagemii.com/portal/brand. The site shows as connected only after the tracker reports its first AI crawler visit. Terms of the free service: Engagemii licenses the AI-crawler activity data the tracker collects, in aggregated form and, unless the owner opts out in portal settings, identified by their domain. The tracker records bot visits only, never human visitors.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The site, e.g. example.com |
| string | yes | The site owner's email (required). The key is emailed there only when it is the site's verified owner. | |
| platform | string | – | The site's stack, if known. |
| Name | Type | Req | Description |
|---|---|---|---|
| connected | boolean | yes | Always false here: a site shows as connected after the tracker reports its first AI crawler visit |
| consent_note | string | – | – |
| dashboard_url | string | – | – |
| domain | string | – | – |
| how_to_claim | array | – | – |
| message | string | – | – |
| offer | string | – | – |
| status | string | – | – |
No examples provided.
data_orders List data orders and download links ~114
List the data orders on the account behind an Engagemii data API key: order number, records, date, status (preparing, ready or pending), and a download link for each ready file (a delivered file never changes). The same as GET https://api.engagemii.com/api/v1/data/orders. Requires an Engagemii data API key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your Engagemii data API key (edk_...). Only needed when the key is not already sent as a request header. |
| Name | Type | Req | Description |
|---|---|---|---|
| orders | array | yes | – |
No examples provided.
data_records Pull licensed company records ~454
Pull full licensed records from the Engagemii dataset (the same 113 columns as a purchased file, in the same order, fingerprinted; every column is filled where we hold the data, the same as in a data file). Metered: every record returned uses one unit of the account's purchased API quota, public companies included; the response states unitsPerRow and unitsSpent. Asking for public companies only (publicCompanies "only") costs 10 units a record and runs only with acceptUnitsPerRow 10; without it the tool answers with the cost and charges nothing. Page with offset: pass the nextOffset of the previous answer until hasMore is false. A filter value that is not recognised is refused with the allowed values and nothing is charged. Returns 25 records by default and at most 100 per call. Larger pulls are available through the REST API at https://api.engagemii.com/api/v1/data/records with the same key. Any returned record whose score is more than 30 days old is queued for a fresh rescore. Requires an Engagemii data API key.
| Name | Type | Req | Description |
|---|---|---|---|
| acceptUnitsPerRow | number | – | confirm the public rate (10) for publicCompanies "only" |
| api_key | string | – | Your Engagemii data API key (edk_...). Only needed when the key is not already sent as a request header. |
| countries | array | – | Country names or ISO codes (worldwide rows) |
| industries | array | – | Categories, any case: Technology, Healthcare, Real Estate, ... |
| limit | number | – | records to draw, 1 unit each. Default 25, max 100 in-chat. |
| offset | number | – | 0 for the first page, then the previous answer's nextOffset |
| publicCompanies | string | – | public companies only, 10 units a record |
| scope | string | – | us = verified US companies; all = worldwide |
| scoreMax | number | – | Highest AI visibility score to include, 0 to 10 |
| scoreMin | number | – | Lowest AI visibility score to include, 0 to 10 |
| states | array | – | US states by name or code |
| Name | Type | Req | Description |
|---|---|---|---|
| apiQuotaRemaining | number | – | – |
| count | number | – | – |
| hasMore | boolean | – | – |
| message | string | – | – |
| nextOffset | number | – | – |
| publicRecords | number | – | – |
| rateClass | string | – | – |
| recordCheck | object | – | – |
| records | array | – | – |
| standardRecords | number | – | – |
| unitsPerRow | number | – | – |
| unitsSpent | number | – | – |
No examples provided.
data_signup Create a data account ~135
Create a free Engagemii data account, or sign in to an existing one, with just an email address. There is no password: we send a one-click sign-in link (valid 30 days) to the address. When the user clicks it they are signed in and the address is verified, which activates the account's API key (edk_...). The key is then shown at https://engagemii.com/portal/data/connect and unlocks search_companies and data_records. Use the email address the user gives you.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email address. The sign-in link is sent here. |
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| next | string | – | – |
| portalUrl | string | – | – |
| sent | boolean | yes | – |
No examples provided.
dataset_sample Get a sample of the dataset ~93
Sample rows from the Engagemii dataset in exactly the 113 columns of a purchased file, in the same order: the first 15 rows of the free sample (500 US companies, all 113 columns, the same sample as on Databricks Marketplace); the full file downloads as Excel or CSV at engagemii.com/aeo/data after a work email. Always the same rows. Free, no auth.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | – |
| fileRows | number | – | – |
| fullDataset | string | – | – |
| note | string | – | – |
| rows | array | yes | – |
No examples provided.
free_kit Request the free fix kit ~182
Request the FREE Customized Fix Kit for a domain. There is one kit and it is the free Customized Fix Kit: ready-to-install fix files written from your own site, plus a PDF audit. Flow: pass the owner's email; Engagemii emails a verification link; after the owner clicks it the kit is built and the download link is emailed automatically. Kits are queued, so delivery is by email rather than in-chat. One kit per domain; repeat requests resend the stored kit.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The site, e.g. example.com |
| string | yes | The site owner's email (the verification link and the kit go there) | |
| owner_confirmed | boolean | yes | Confirm with the user that this is their own brand. Agencies working on client sites should use the data portal (engagemii.com/aeo/data) instead. |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | – |
| next_step | string | – | – |
| related_free_tool | string | – | – |
| request_id | string|null | – | – |
| state | string | yes | verification_sent, verify_resent, in_progress or ready_resent |
No examples provided.
kit_download Download a purchased fix kit ~72
For a fix kit bought before October 2026 (paid checkout), receive every Customized Fix Kit file plus the badge embed as plain text. Requires the Stripe session id (cs_...) from the checkout success URL.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The Stripe checkout session id from the success URL, starts with cs_ |
| Name | Type | Req | Description |
|---|---|---|---|
| apply | string | – | – |
| domain | string | – | – |
| files | object | yes | – |
No examples provided.
search_companies Search the company dataset ~183
Query the scored dataset with filters (industries, states, score range, scope us|all). Returns up to 100 light rows. Requires an Engagemii data API key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Your Engagemii data API key (edk_...). Only needed when the key is not already sent as a request header. |
| industries | array | – | Business categories, e.g. Technology, Healthcare |
| limit | number | – | max 100 |
| scope | string | – | us = verified US companies; all = worldwide |
| scoreMax | number | – | Highest AI visibility score to include, 0 to 10 |
| scoreMin | number | – | Lowest AI visibility score to include, 0 to 10 |
| states | array | – | US states by name or two-letter code, e.g. Texas or TX |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| dailyRowsRemaining | number | – | – |
| disclaimer | string | – | – |
| licensing | string | – | – |
| rows | array | yes | – |
No examples provided.
How do I install the Engagemii AI Visibility Data MCP server?
Engagemii AI Visibility Data is a hosted endpoint at https://api.engagemii.com/api/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.engagemii.com
claude mcp add --transport http com-engagemii-citation-watch 'https://api.engagemii.com/api/mcp'
What is the Engagemii AI Visibility Data MCP server?
Engagemii AI Visibility Data is an MCP server listed in the public MCP registry as com.engagemii/citation-watch. AI visibility of 82M+ companies: scores, AI crawler reads, full records. Free 500 and 1M datasets. This page covers its hosted endpoint (https://api.engagemii.com/api/mcp).
Is the Engagemii AI Visibility Data MCP server safe to use?
Engagemii AI Visibility Data scores 83 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 Engagemii AI Visibility Data MCP server expose?
Engagemii AI Visibility Data exposes 13 tools: aeo_score, aeo_audit, brand_profile, dataset_sample, citation_watch, and 8 more. Their descriptions and schemas cost roughly 2,135 tokens of context every time the server is loaded.
Does the Engagemii AI Visibility Data MCP server require authentication?
No. We connected to Engagemii AI Visibility Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Engagemii AI Visibility Data MCP server still maintained?
Engagemii AI Visibility Data 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 Engagemii AI Visibility Data MCP server?
VerifyMCP ran 13 checks on Engagemii AI Visibility Data, 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.