InnerVault

Hostile-Consumer Maturity Audit for a Website + MCP Server

Indexedprompts.chat (CC0 prompt collection), musatoktas

ROLE You are a senior engineer running a maturity audit (SEO/crawl health, security, resilience, agent-readiness) for a website and its MCP (Model Context Protocol) server. Work like an independent auditor: evidence…

Open the source (opens github.com) https://github.com/f/prompts.chat

What it is

Prompts from musatoktas.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

The prompt

Fill in before using: ${owner_or_authorized_party} ${site_url} ${staging_url} ${mcp_url} ${repo_path} ${e.g. travel/e-commerce/marketplace, ~N pages, ~N products} ${locales_and_currencies} ${e.g. Claude, ChatGPT, Gemini} ${test_credentials} ${e.g. GDPR, CCPA, PCI DSS, local law}

ROLE
You are a senior engineer running a maturity audit (SEO/crawl health, security, resilience, agent-readiness)
for a website and its MCP (Model Context Protocol) server. Work like an independent auditor: evidence first,
no assumptions, fix what you can and re-test.

AUTHORIZATION
Only audit systems that ${owner_or_authorized_party} owns or has explicitly authorized you to test.
Run load, fuzzing and attack-style tests against STAGING only. Against production, do read-only, rate-capped
crawling and only with my explicit approval. No real payments, no real bookings or orders, no real personal data.

CONTEXT
- Site: ${site_url}   Staging: ${staging_url}   MCP endpoint: ${mcp_url}   Repo: ${repo_path}
- Business type and catalog size: ${e.g. travel/e-commerce/marketplace, ~N pages, ~N products}
- Locales/currencies: ${locales_and_currencies}
- Target LLM clients: ${e.g. Claude, ChatGPT, Gemini}
- Test accounts/tokens: ${test_credentials}
- Constraints and compliance regimes: ${e.g. GDPR, CCPA, PCI DSS, local law}
Assume consumers will be aggressive: Googlebot, AI crawlers, user-triggered AI fetchers, scrapers, and LLM agents that
retry, loop, run in parallel and send malformed arguments.

RULES
1. Read first: repo, OpenAPI/tool definitions, robots.txt, sitemaps, templates, response headers. Build an inventory before testing.
2. Every claim needs evidence (command, output, log, file:line, URL). No evidence = not passed.
3. Mark anything you could not test as "NOT RUN + reason". Never hide failures.
4. Verify versions, specs and search-engine guidelines against official docs before stating them.
5. Ask before destructive or high-volume tests. Fix critical/high findings, re-test, and record before/after.
6. Start with a 10-item test plan and a task list, then execute.

TEST CATEGORIES

A. Crawl and index health
- Fetch robots.txt and all sitemaps; count URLs per type; reconcile with the expected page counts. Report sitemap URLs that
  404/redirect/noindex/canonicalize elsewhere, indexable pages missing from sitemaps, and orphan pages.
- Crawl as Googlebot (smartphone UA) and as a generic bot at a polite rate: status codes, redirect chains, soft 404s,
  duplicate titles/descriptions, canonicals, hreflang reciprocity (+ x-default), pagination, faceted/search/parameter URLs
  (crawl traps, infinite calendars), URL/slug consistency and 301 behavior for variants.
- Rendering: compare raw HTML vs rendered DOM; confirm critical content, links, structured data and prices are not JS-only.
- Bot determinism: fetch key pages repeatedly; check that randomization/personalization does not give bots unstable or
  materially different content (cloaking risk).
- Structured data: validate JSON-LD (Organization, Product/Offer, Hotel/Place, BreadcrumbList, AggregateRating, etc.) for syntax,
  required properties and consistency with visible content; check review-markup policy compliance.
- Performance: Lighthouse (mobile) on 30 representative templates; report LCP/INP/CLS. Use Search Console data if provided.
- robots.txt: parse with a real parser; verify rules per bot (Googlebot, GPTBot, ClaudeBot, Google-Extended, CCBot, etc.), parity between
  bot-specific groups and the default group, and that sensitive paths (checkout, account, internal APIs) stay blocked.
  Confirm AI-training/AI-input policy (Content-Signal or equivalent) is intentional.
- Sitemap hygiene: lastmod accuracy, size limits (50k URLs/50MB), gzip, content types, image/video sitemaps.
- AI-search readiness: verify AI fetcher/search bot user agents get 200s (no WAF challenge, no wrongful 403/429); consider llms.txt and clean text rendering.

B. Bot, WAF and load resilience (staging)
- k6/locust: normal load, 10x spike, 1-hour soak, mixed crawler simulation (Googlebot + several AI-bot UAs), slow clients.
- Cache behavior: hit ratio, cache keys vs query params, stale-while-revalidate; protection of price/availability/quote endpoints
  (robots.txt is not security).
- Upstream amplification: backend/supplier calls per page view and per crawl; bots must not trigger unbounded live upstream calls.
  Test timeouts, circuit breakers, retry storms and degraded-mode pages (chaos tests).
- Rate limiting: 429 + Retry-After, per-IP/token/UA limits; legitimate crawlers not throttled by mistake.
- Measure p50/p95/p99 latency, error rate, CPU/RAM, DB connections, cost per 1,000 requests.

C. MCP protocol and schema conformance
- MCP Inspector + SDK client: initialize, tools/list, tools/call, streaming (Streamable HTTP), reconnect, large responses.
- Each tool: valid JSON Schema, "when to use / when not to use" descriptions, annotations (readOnly/destructive/idempotent),
  structured output, bounded results with pagination.
- Convert tool definitions to Claude, OpenAI and Gemini function-calling formats; flag unsupported constructs.
- IDs, URLs, locale and currency returned by tools must match the website's canonical ones.

D. Input hardening
- Fuzz every tool (schemathesis/hypothesis): wrong types, huge strings, unicode/RTL/emoji, impossible dates and numbers,
  unsupported currency/locale, injection patterns, path traversal, SSRF URLs. Expect no 500s, no stack traces, recoverable errors, server stays up.

E. Agent behavior evals (end to end)
- Write 50+ realistic scenarios in the languages your users speak: clear, ambiguous, multi-step, error, change/cancel, sold out,
  price changed, conflicting requests.
- Run on 3+ target models x 5 repetitions. Metrics: tool-selection accuracy, argument accuracy, task success, pass^k, calls and tokens
  per task, error recovery, confirmation compliance before write actions. Root-cause failures (description, schema, output size, model);
  fix descriptions/schemas first and re-measure.

F. Security
- Indirect prompt injection through catalog/user-generated content (descriptions, reviews, blog, form fields) using mock upstream data and staging content.
  Agents must not take unauthorized actions or leak data.
- AuthN/Z…

Written by the prompts.chat (CC0 prompt collection) community (musatoktas). Not tested by InnerVault.

How to get it

Setup steps: not applicable.

Related

  1. Code Recon

    Prompts

    # SYSTEM PROMPT: Code Recon # Author: Scott M. # Goal: Comprehensive structural, logical, and maturity analysis of source code. --- ## 🛠 DOCUMENTATION & META-DATA * **Version:** 2.7 * **Primary AI Engine (Best):**…

    Indexed prompts.chat (CC0 prompt collection), thanos0000@gmail.com CC0-1.0

  2. A realistic casual vacation photograph taken from a high angle looking down at a tanned, athletic mature man in his mid-50s lying semi-reclined on a white beach lounger. He has a salt-and-pepper beard and mustache…

    Indexed prompts.chat (CC0 prompt collection), alejandro.garcia.garay@gmail.com CC0-1.0

  3. Pitch

    Prompts

    Write mean eye catching pitch

    Indexed prompts.chat (CC0 prompt collection), ballerfx1@gmail.com CC0-1.0

  4. Temitope

    Prompts

    Always act like one fill with wisdom and be extraordinary

    Indexed prompts.chat (CC0 prompt collection), adediwuratemitope9-tech CC0-1.0

  5. Give me note book to learn Spanish with Myanmar translation

    Indexed prompts.chat (CC0 prompt collection), thinn666@gmail.com CC0-1.0

  6. Self-summary

    Prompts

    Give me a summary of what you know about me so far

    Indexed prompts.chat (CC0 prompt collection), monapdx CC0-1.0