Composite MCP tools join six per-URL data sources on the canonical URL key. Every workflow chains across multiple MCPs and emits a tracked_id for the attribution loop.
Eight pluggable sources, one URL key. Each card below is one connector: own MCP servers, vendor MCPs, and HTTP/SSE APIs we wrap in-process.
Anchor MCP: citations, SoV, sentiment, fan-out, prompt suggestions. Streamable-HTTP transport against api.peec.ai/mcp.
Ahrefs MCP for backlinks and keyword volume. Used by the semantic-gap, decay, and prompt-bridge composites for upstream demand context.
Own MCP. Inspection + impressions/clicks/rank. 2000/day quota guard via tiered T1/T2/T3 priority queue.
Own MCP. GEO readiness via stdio MCP. Score + grade + top issues + chunkability hints per URL.
Real-time competitor mention stream over SSE HTTP, not MCP. Peecockpit wraps it in-process and surfaces it through composite tools.
Backlinks JSON API: ExtBackLinks, RefDomains, TrustFlow, CitationFlow. Wired into the URL report's GEO readiness tile and the journey's external-mentions track.
Turnkey AI-bot traffic feed (api.botsanalyser.com). One of three drivers behind bot_log_client.py alongside Cloudflare Logpush and a static-JSON demo adapter.
Per-Peec-project Google OAuth. GA4 for AI-referral sessions / revenue, GSC Inspection for crawl/index state, GSC Wizard for impressions/clicks/rank.
Every page in the dashboard maps to a single composite MCP tool. The tool is the join. Agents call it; humans see it; both get the same payload.
Drop a URL, get the full funnel: bots, Inspection, GSC Wizard, Peec citations, Glippy readiness, GA4 sessions and revenue. The hero composite that powers /url-report.
All ranked opportunities across SEO/PR/Marketing with the prescribed MCP chain to execute each.
Every recommended action emits a tracked_id and is retracked at T+14 / T+28. The outcome delta closes the loop. No more 'we shipped a fix, did it work?'
Each surface carries chips showing live MCP / file snapshot / fallback, so the freshness of every number is explicit on the page.
Writes to Peec are off until you explicitly opt in. Even when on, a daily cap bounds the blast radius and every applied change lands in the audit log.
2000/day/property cap respected via a tiered priority queue: T1 daily, T2 weekly, T3 monthly-rotating, plus on-demand. UTC midnight roll, not Pacific. Over-conservative is the safer choice.
If GA4 reports sampling_metadatas, a Sampled chip surfaces with the sampling ratio. Numbers above the ~10M events/day threshold are not over-trusted.
Each tracked event surfaces how many other actions opened within ±48h, so a metric delta in a crowded window doesn't read as cleanly causal.
You'll get an invite when we open the next batch, plus one short email when we ship a new feature page. No drip campaign, no spam.
Early-access invites go out in small batches. Unsubscribe anytime.