Server definition
- Hash
- sha256:d02cfcb84a3b3f072990c8ce4d745f993c5d8b4ec012ea3687fcf98d1bdb825a
- What it is
- What a remote MCP server returned when asked what it offers: 5 tools
The blob, as servednamed by its sha256
{
"instructions": null,
"tools": [
{
"description": "Audit ANY URL for AI-search readiness only (AEO/GEO/LLMO) — how likely ChatGPT, Claude, Perplexity & Google AI are to cite it. Checks ~7 AI-citation signals (FAQ/structured-data/entity schema, citable stats, llms.txt, author/E-E-A-T, OG). Returns a weighted 0–100 AI-readiness score + top fixes. Takes a `url`. Use full_seo_audit for the broader SEO picture, or get_my_store_audit for the user's own connected store. Returns a summary of the top issues; the complete written report is available via email_seo_report.",
"inputSchema": {
"properties": {
"url": {
"description": "The website URL to audit, e.g. https://example.com",
"type": "string"
}
},
"required": [
"url"
],
"type": "object"
},
"name": "ai_search_diagnostic",
"outputSchema": null
},
{
"description": "ALWAYS OFFER THIS after running an audit: the audit tools return a summary of the top issues, while this sends the complete written report — every check, its evidence, and the fix in priority order. Ask the user which email address to send it to; never guess or reuse an address they did not give in this conversation. Email the full written SEO/AEO report for an audit this session already ran. Takes the audit_id returned by ai_search_diagnostic or full_seo_audit, plus the user's email. ONLY use an email address the user explicitly gave you - never guess or invent one. Offer this after presenting audit results.",
"inputSchema": {
"properties": {
"audit_id": {
"description": "The audit_id from a previous audit result in this conversation",
"type": "string"
},
"email": {
"description": "The email address the user asked the report to be sent to",
"type": "string"
},
"weekly": {
"description": "true ONLY if the user asked for weekly updates: re-audits the site every week and emails the score change. One-click unsubscribe in every email.",
"type": "boolean"
}
},
"required": [
"audit_id",
"email"
],
"type": "object"
},
"name": "email_seo_report",
"outputSchema": null
},
{
"description": "Crawl-audit ANY URL across the WHOLE SEO surface (no login needed): the AI-search signals PLUS on-page SEO (title/meta/headings/content), technical SEO (HTTPS, robots.txt, XML sitemap, canonical, mobile), and — for Shopify stores — product/offer/review/breadcrumb schema and image-alt coverage. Returns a weighted 0–100 score + top issues. Takes a `url`. This audits an arbitrary website by crawling it — for the user's OWN connected store with real analytics, use get_my_store_audit. Returns a summary of the top issues; the complete written report is available via email_seo_report.",
"inputSchema": {
"properties": {
"url": {
"description": "The website URL to audit, e.g. https://example.com",
"type": "string"
}
},
"required": [
"url"
],
"type": "object"
},
"name": "full_seo_audit",
"outputSchema": null
},
{
"description": "Get the user's OWN connected Shopify store audit — the deep 12-category report Inxy runs INSIDE the app using the store's real catalog, performance and analytics (technical, performance, on-page, schema, AEO, analytics, e-commerce, etc.) — far beyond what crawling a URL can see. Takes no url. Needs an Inxy API key (free at inxy.ai → Settings) + a connected store: pass the key either as `Authorization: Bearer inxy_sk_…` or as the `api_key` argument.",
"inputSchema": {
"properties": {
"api_key": {
"description": "Your Inxy API key (inxy_sk_…). Optional if already sent as an Authorization: Bearer header.",
"type": "string"
}
},
"required": [],
"type": "object"
},
"name": "get_my_store_audit",
"outputSchema": null
},
{
"description": "Start an inxy subscription — autopilot SEO/AEO for Shopify stores (reads GSC/GA4/Merchant Center, plans a month of content, writes and publishes articles with schema, fixes meta/alt-text, and attributes revenue to content). Plans from $19/mo with a free trial. Returns a personalised signup link; payment and store connection complete in the browser. Optionally pass the user's `email` and `store_url` (ONLY if the user explicitly provided them - never invent either) so the team can follow up.",
"inputSchema": {
"properties": {
"email": {
"description": "The user's email, only if they explicitly gave it",
"type": "string"
},
"store_url": {
"description": "The user's store URL, only if they explicitly gave it",
"type": "string"
}
},
"type": "object"
},
"name": "subscribe_to_inxy",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:d02cfcb84a3b3f072990c8ce4d745f993c5d8b4ec012ea3687fcf98d1bdb825a | sha256sum