Description
Mescio Insights is the observability layer for the Mescio stack.
- Mescio for Agents makes the site readable (Markdown, llms.txt).
- WebMCP Bridge makes it usable (search, retrieve, cart, MCP tools).
- Mescio Insights shows whether those layers were actually requested.
It listens to the shared mescio_agent_request hook. You can run Insights with Mescio only, WebMCP only, or both.
What you get
- Hits by channel (
markdown,llms,rest,mcp,webmcp) - Hits by client (GPTBot, Claude, ChatGPT, … — from the User-Agent, not from ChatGPT citations)
- Last request, unique clients, hour-of-day
- Daily bars, filters, pagination
- CSV export
- First open copies an existing Mescio Agent activity log
- Optional public summary: shortcode
[mescio_insights]and REST/wp-json/mescio-insights/v1/summary(counts only, off by default) - Retention 7–90 days
- No IP addresses, no request bodies, nothing sent off-site
What this is not
A ChatGPT ranking score. A GEO API product. A hosted portal. Those may come later as a separate module.
Requirements
WordPress 6.0+ and at least one of:
- Mescio for Agents 1.8.0+
- WebMCP Bridge 1.10.1+ (trunk that always fires
mescio_agent_request)
Installation
- Copy the
mescio-insightsfolder intowp-content/plugins/ - Activate Mescio Insights
- Open Mescio Insights in the admin menu
- Keep Mescio and/or WebMCP active so events are emitted
FAQ
Does this replace Agent activity in Mescio?
No. Mescio 1.8 still has a short local log. Insights is the fuller dashboard and keeps its own table.
Will you see my data?
No. Rows stay in your WordPress database.
Can I show this on the public site?
Yes, after you enable Public summary under Log settings. Use the shortcode [mescio_insights] or [mescio_insights days="7"]. It prints counts, channels and client names — not paths, not user-agent strings, not IP addresses.
Why is the log empty with only WebMCP 1.10.1 from WordPress.org?
1.10.1 only fires the hook if something is already listening. Insights registers a listener, so current trunk of WebMCP (and Insights + Mescio together) is enough. A future WebMCP tag always emits the hook.
Screenshots
Changelog
1.2.0
- Lighter admin screen (no hero photo or paper texture)
- Menu label is Mescio Insights
- First visit copies the Mescio Agent activity log when Insights is empty
- Extra metrics: last request, unique clients, hour of day
- Optional public summary shortcode and REST route (off by default)
1.1.3
- Hide unrelated theme/plugin notices on the Insights screen
- Explain the empty log and how to record the first hit
1.1.2
- Require WordPress 6.0 (same as Mescio and WebMCP), not 6.2
1.1.1
- Dashboard CSS uses system fonts only; no Google Fonts or other remote requests
1.1.0
- Observatory dashboard: hero still-life, paper texture, stacked traffic chart, client mix, ranked paths
- Targeted search: resource query, custom dates, channel, client, HTTP status class
1.0.0
- First release: local log, dashboard, filters, CSV, import from Mescio Agent activity


