@kryptosai/mcp-observatory 0.26.0 → 0.27.0

package/docs/certification-campaign-template.md

@@ -1,181 +0,0 @@
-# MCP Observatory Certification Campaign
-
-Use this tracker for outbound PR waves against MCP server repositories.
-
-## Campaign Goal
-
-Open helpful PRs that add MCP Observatory CI checks and a public compatibility/security badge to popular MCP server projects.
-
-One-shot campaign target:
-
-- 50 researched repos
-- 25 PRs opened
-- 10 accepted checks or badges
-- 5 public proof points added to launch materials
-- 3 production/security pilot conversations started
-
-## Qualification Rules
-
-Prioritize:
-
-- active MCP server repos
-- clear install/run command
-- recent commit or release in the last 90 days
-- 100+ stars, meaningful npm downloads, directory popularity, or enterprise category
-- developer tools, security, CI/CD, database, browser automation, SaaS, cloud, or finance servers
-
-Skip:
-
-- servers that require private credentials to start
-- repos with destructive default tools
-- abandoned repos unless they have major download volume
-- projects that already have equivalent MCP compatibility/security CI
-
-## Tracker
-
-| Priority | Repo | Package/Command | Category | Stars/Downloads/Listing Signal | Activity Signal | Risk Notes | Status | PR URL | Accepted/Badge/Proof |
-| ---: | --- | --- | --- | --- | --- | --- | --- | --- | --- |
-| 1 | `modelcontextprotocol/servers` | `npx -y @modelcontextprotocol/server-sequential-thinking@latest` | Reference | Official/reference signal | GitHub check passing on PR; local validation passed: 1 tool | Fork PR token is read-only, so workflow disables PR comment/status writes | pr-opened | https://github.com/modelcontextprotocol/servers/pull/4392 | Waiting for maintainer review |
-| 2 | `modelcontextprotocol/servers` | `npx -y @modelcontextprotocol/server-filesystem .` | Filesystem | Official/reference signal | verify package location | Needs harmless temp directory target | researched | | |
-| 3 | `upstash/context7` | `npx -y @upstash/context7-mcp@latest` | Developer Tools | 57k+ stars / major MCP docs server | Local validation passed: 2 tools | `@latest` required for npx bin resolution | pr-opened | https://github.com/upstash/context7/pull/2800 | Waiting for maintainer review |
-| 4 | `executeautomation/mcp-playwright` | `npx -y @executeautomation/playwright-mcp-server@latest` | Browser Automation | 5k+ stars / high-interest browser MCP category | Local validation passed: 33 tools, 1 resource | Requires Chromium install; suppressed intentional `playwright_evaluate:shell-injection` finding | pr-opened | https://github.com/executeautomation/mcp-playwright/pull/225 | Waiting for maintainer review |
-| 5 | `browserbase/mcp-server-browserbase` | `npx -y @browserbasehq/mcp-server-browserbase` | Browser Automation | Hosted browser MCP category | verify auth-free startup | May require API key; issue-only if startup requires credentials | researched | | |
-| 6 | `smithery-ai/server-sequential-thinking` | `npx -y @smithery-ai/server-sequential-thinking` | Developer Tools | MCP directory ecosystem | verify package/repo naming | Good low-risk simple server if public package starts cleanly | researched | | |
-| 7 | `kazuph/mcp-taskmanager` | `npx -y @kazuph/mcp-taskmanager@latest` | Developer Tools | 200+ stars / task/project MCP category | Local validation passed: 10 tools | Scoped package name corrected from tracker | pr-opened | https://github.com/kazuph/mcp-taskmanager/pull/11 | Waiting for maintainer review |
-| 8 | `cyanheads/filesystem-mcp-server` | `node dist/index.js` | Filesystem | Filesystem MCP category | Local validation passed after fix: 10 tools | Fixed real conformance bug: advertised resources without `resources/list`; workflow uses temp sandbox | closed-unmerged | https://github.com/cyanheads/filesystem-mcp-server/pull/19 | Closed by maintainer without merge |
-| 9 | `redis/mcp-redis` | `uvx mcp-redis` | Database | Enterprise database category | verify auth-free startup | Database target may require service; issue-only if credentials needed | researched | | |
-| 10 | `mongodb-js/mongodb-mcp-server` | `npx -y mongodb-mcp-server` | Database | Enterprise database category | verify auth-free startup | Likely needs connection string; issue-only first | researched | | |
-| 11 | `supabase-community/supabase-mcp` | `npx -y supabase-mcp` | Database | Enterprise/SaaS category | verify current package | Likely requires token; issue-only first | researched | | |
-| 12 | `cloudflare/mcp-server-cloudflare` | `npx -y @cloudflare/mcp-server-cloudflare` | Cloud | Enterprise cloud category | verify package | Likely requires auth; issue-only first | researched | | |
-| 13 | `stripe/agent-toolkit` | `npx -y @stripe/agent-toolkit` | Payments | Enterprise payments category | verify MCP mode | Likely requires API key; issue-only first | researched | | |
-| 14 | `github/github-mcp-server` | `docker run ghcr.io/github/github-mcp-server` | Developer Tools | Major platform category | verify image/startup | Auth required for useful checks; issue-only first | researched | | |
-| 15 | `microsoft/playwright-mcp` | `npx -y @playwright/mcp@latest` | Browser Automation | 34k+ stars / major platform category | Local validation passed: 23 tools | Uses `skipInvoke` and explicit suppressions for intentional browser-code tools | pr-opened | https://github.com/microsoft/playwright-mcp/pull/1657 | Waiting for maintainer review |
-| 16 | `jetbrains/mcpProxy` | `npx -y @jetbrains/mcp-proxy` | Developer Tools | IDE platform category | verify package | May depend on IDE process; issue-only first | researched | | |
-| 17 | `BrowserMCP/mcp` | `npx -y @browsermcp/mcp` | Browser Automation | 6k+ stars / browser-control MCP category | Local validation passed: 12 tools | Browser automation trust boundary; workflow is inventory/security only | pr-opened | https://github.com/BrowserMCP/mcp/pull/189 | Waiting for maintainer review |
-| 18 | `UI5/mcp-server` | `npx -y @ui5/mcp-server` | Developer Tools | SAP/UI5 ecosystem MCP package | Local validation passed: 10 tools | Developer tooling surface; no credentials required for inventory | pr-opened | https://github.com/UI5/mcp-server/pull/348 | Waiting for maintainer review |
-| 19 | `apify/actors-mcp-server` | `npx -y @apify/actors-mcp-server` | SaaS/API | Automation platform category | verify auth-free startup | Likely requires token; issue-only first | researched | | |
-| 20 | `makenotion/notion-mcp-server` | `npx -y @notionhq/notion-mcp-server` | SaaS/API | Major SaaS category | Local validation passed: 24 tools | Workspace-data MCP; PR is compatibility/schema/security inventory only | pr-opened | https://github.com/makenotion/notion-mcp-server/pull/324 | Waiting for maintainer review; external Semgrep check failing |
-| 21 | `linear/linear-mcp` | `npx -y @linear/mcp-server` | SaaS/API | Developer SaaS category | verify package | Likely requires token; issue-only first | researched | | |
-| 22 | `sentry/sentry-mcp` | `npx -y @sentry/mcp-server` | Observability | Developer SaaS category | verify package | Likely requires token; issue-only first | researched | | |
-| 23 | `elastic/mcp-server-elasticsearch` | `npx -y @elastic/mcp-server-elasticsearch` | Search | Enterprise search category | verify package | Likely requires service; issue-only first | researched | | |
-| 24 | `qdrant/mcp-server-qdrant` | `uvx mcp-server-qdrant` | Vector Database | AI infra category | verify package | May require service URL; issue-only first | researched | | |
-| 25 | `weaviate/mcp-server-weaviate` | `uvx mcp-server-weaviate` | Vector Database | AI infra category | verify package | May require service URL; issue-only first | researched | | |
-| 26 | `antvis/mcp-server-chart` | `npx -y @antv/mcp-server-chart` | Visualization/Data | 4k+ stars / chart-generation MCP category | Local validation passed: 27 tools | Generated chart artifacts; no credentials required for inventory | pr-opened | https://github.com/antvis/mcp-server-chart/pull/312 | Waiting for maintainer review |
-| 27 | `owner/repo` | `uvx package` | API | | | | researched | | |
-| 28 | `owner/repo` | `npx -y package` | Database | | | | researched | | |
-| 29 | `owner/repo` | `npx -y package` | Search | | | | researched | | |
-| 30 | `owner/repo` | `docker run image` | Cloud | | | | researched | | |
-| 31 | `owner/repo` | `npx -y package` | Developer Tools | | | | researched | | |
-| 32 | `owner/repo` | `uvx package` | Security | | | | researched | | |
-| 33 | `owner/repo` | `npx -y package` | SaaS | | | | researched | | |
-| 34 | `owner/repo` | `npx -y package` | Data | | | | researched | | |
-| 35 | `owner/repo` | `docker run image` | Infrastructure | | | | researched | | |
-| 36 | `owner/repo` | `npx -y package` | Finance | | | | researched | | |
-| 37 | `owner/repo` | `uvx package` | Browser Automation | | | | researched | | |
-| 38 | `owner/repo` | `npx -y package` | API | | | | researched | | |
-| 39 | `owner/repo` | `npx -y package` | Database | | | | researched | | |
-| 40 | `owner/repo` | `docker run image` | Security | | | | researched | | |
-| 41 | `owner/repo` | `npx -y package` | Developer Tools | | | | researched | | |
-| 42 | `owner/repo` | `uvx package` | Data | | | | researched | | |
-| 43 | `owner/repo` | `npx -y package` | Search | | | | researched | | |
-| 44 | `owner/repo` | `npx -y package` | SaaS | | | | researched | | |
-| 45 | `owner/repo` | `docker run image` | Cloud | | | | researched | | |
-| 46 | `owner/repo` | `npx -y package` | Filesystem | | | | researched | | |
-| 47 | `owner/repo` | `uvx package` | Security | | | | researched | | |
-| 48 | `owner/repo` | `npx -y package` | Developer Tools | | | | researched | | |
-| 49 | `owner/repo` | `npx -y package` | Infrastructure | | | | researched | | |
-| 50 | `owner/repo` | `docker run image` | Browser Automation | | | | researched | | |
-
-Statuses:
-
-- `researched`
-- `branch-ready`
-- `pr-opened`
-- `accepted`
-- `declined`
-- `needs-maintainer-input`
-- `proof-captured`
-- `pilot-lead`
-
-## PR Checklist
-
-- Generate the local kit first:
-  `npx @kryptosai/mcp-observatory setup-ci --all --command "<safe startup command>"`
-- Add `.github/workflows/mcp-observatory.yml`
-- Add `mcp-observatory.target.json` when the startup command needs args, cwd, or env placeholders
-- Use `deep: true` and `security: true`
-- Keep `fail-on-regression: true` unless the repo is noisy
-- Add README badge only when it fits the repo style
-- Include the generated maintainer PR body from `docs/mcp-observatory-pr-body.md`
-- Do not include raw telemetry, private evidence, or sales pricing
-- Prefer issue-only fallback when the server requires credentials, paid services, destructive tools, or unclear startup
-
-## PR Templates
-
-### Workflow-Only PR
-
-```md
-This adds a lightweight MCP Observatory check for this MCP server.
-
-Why it helps:
-
-- verifies MCP tools/prompts/resources still respond correctly
-- catches schema drift and common security footguns before release
-- posts a readable PR report for maintainers
-- gives users a compatibility signal when evaluating MCP servers
-
-It runs in GitHub Actions and does not require an account. If the check is too strict for this repo, `fail-on-regression: false` can be used while keeping the report visible.
-```
-
-### Workflow + Badge PR
-
-```md
-This adds MCP Observatory CI plus a small README badge so users can see this server is checked for MCP compatibility, schema drift, and common security issues.
-
-The workflow runs on PRs and pushes to `main`. The badge links back to MCP Observatory for context and can be removed if it does not fit the repo style.
-```
-
-### Issue-Only Fallback
-
-~~~md
-I tried preparing a small MCP Observatory CI check for this server, but did not want to open a PR without confirming the safest startup command.
-
-Would you accept a workflow that runs:
-
-```bash
-npx @kryptosai/mcp-observatory test <server command> --security --deep
-```
-
-The goal is to give users a visible compatibility/security signal and catch schema drift before releases.
-~~~
-
-## Generated PR Body Printer
-
-After running `setup-ci --all`, print the generated maintainer copy with:
-
-```bash
-npm run certification:pr-body -- docs/mcp-observatory-pr-body.md
-```
-
-For a repo-specific body, run the command from the target branch after generating the local adoption kit.
-
-## Proof Capture
-
-For accepted PRs, record:
-
-- repo
-- PR URL
-- category
-- accepted date
-- badge added: yes/no
-- CI status
-- quote or maintainer reaction if public
-- whether the repo appears in Glama, PulseMCP, Smithery, or awesome-MCP lists
-
-Use accepted PRs as proof for:
-
-- README traction section
-- launch posts
-- enterprise outreach
-- directory listing copy
-- weekly MCP safety report

package/docs/certification-distribution.md

@@ -1,145 +0,0 @@
-# Certification Distribution Loop
-
-Use this when opening helpful PRs to MCP server projects. The motion is simple: run MCP Observatory, give the maintainer a useful security/compatibility check, and leave them with a badge/report they can keep.
-
-## Offer
-
-MCP Observatory gives MCP server maintainers:
-
-- CI coverage for tools, prompts, resources, schema quality, and security checks
-- A PR comment report on every change
-- A README badge they can show publicly
-- A local-first OSS path with no account required
-- A paid production path only if they need hosted history, private repo reporting, support, certification, or fleet visibility
-
-## Copy-Paste Badge
-
-For repos that add the GitHub Action, suggest this README badge:
-
-```md
-[![MCP Observatory](https://img.shields.io/badge/MCP%20Observatory-enabled-2563eb)](https://github.com/KryptosAI/mcp-observatory)
-```
-
-For repos that generate a score badge, suggest:
-
-```bash
-npx @kryptosai/mcp-observatory badge npx -y <server-package> --output docs/mcp-health.svg
-```
-
-```md
-[![MCP Health](./docs/mcp-health.svg)](https://github.com/KryptosAI/mcp-observatory)
-```
-
-## GitHub Action Template
-
-Fast path:
-
-```bash
-npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y <server-package>"
-```
-
-That creates:
-
-- `.github/workflows/mcp-observatory.yml`
-- `docs/mcp-observatory-badge.md`
-- `mcp-observatory.target.json`
-- `docs/mcp-observatory-pr-body.md`
-- `docs/mcp-observatory-issue.md`
-- `docs/mcp-observatory-score-badge.md`
-
-Manual template:
-
-```yaml
-name: MCP Observatory
-
-on:
-  pull_request:
-  push:
-    branches: [main]
-
-permissions:
-  contents: read
-  pull-requests: write
-  statuses: write
-
-jobs:
-  mcp-observatory:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6
-      - uses: KryptosAI/mcp-observatory/action@main
-        with:
-          command: npx -y <server-package>
-          deep: true
-          security: true
-          comment-on-pr: true
-```
-
-For production CI, pin the package version:
-
-```yaml
-- uses: KryptosAI/mcp-observatory/action@main
-  with:
-    command: npx -y <server-package>
-    package-version: 0.25.1
-    deep: true
-    security: true
-```
-
-For repos with a local target config:
-
-```yaml
-- uses: KryptosAI/mcp-observatory/action@main
-  with:
-    target: ./observatory-target.json
-    deep: true
-    security: true
-```
-
-## Maintainer PR Body
-
-```md
-This adds a lightweight MCP Observatory check for this server.
-
-Why it helps:
-
-- verifies MCP tools/prompts/resources still respond correctly
-- catches schema drift and common security footguns before release
-- posts a readable PR report for maintainers
-- creates a public compatibility signal for users evaluating MCP servers
-
-It runs locally/inside GitHub Actions and does not require an account. If the check is too strict for this repo, `fail-on-regression: false` can be used while keeping the PR report visible.
-```
-
-## Comment For Passing Repos
-
-```md
-Nice, this server passes MCP Observatory checks. If you want the signal in the README, you can add:
-
-```md
-[![MCP Observatory](https://img.shields.io/badge/MCP%20Observatory-enabled-2563eb)](https://github.com/KryptosAI/mcp-observatory)
-```
-
-That gives users a quick compatibility/security signal when they are choosing MCP servers.
-```
-
-## Targeting Order
-
-Prioritize repos with:
-
-- 100+ GitHub stars or visible npm downloads
-- active releases in the last 90 days
-- MCP servers used by developer tools, security, CI/CD, databases, browser automation, or enterprise SaaS
-- no existing MCP compatibility/security CI
-- clear package command that can run in GitHub Actions
-
-Avoid drive-by PRs where the server requires private credentials, paid services, or destructive default actions.
-
-## Directory Follow-Through
-
-After a repo accepts the check or badge:
-
-- ask the maintainer to mention “tested with MCP Observatory” in their MCP directory listing
-- update the MCP Observatory launch/story docs with the accepted repo
-- use accepted PRs as proof in enterprise outreach
-- invite production users to hosted reporting or certification pilots

package/docs/certification-pr-campaign.md

@@ -1,68 +0,0 @@
-# Certification PR Campaign
-
-The certification campaign creates public proof by opening small, helpful PRs that add read-only MCP Observatory checks to public MCP servers.
-
-## Goal
-
-Create maintainer conversations and accepted public integrations around one clear offer:
-
-> Add MCP CI/security checks in 60 seconds.
-
-## PR Shape
-
-Each PR should be narrow:
-
-- add `.github/workflows/mcp-observatory.yml`
-- add `mcp-observatory.target.json` when needed
-- add optional badge snippet
-- keep permissions read-only by default
-- avoid changing server implementation code
-
-Generate the kit:
-
-```bash
-npx @kryptosai/mcp-observatory setup-ci --all --command "<safe startup command>"
-npx @kryptosai/mcp-observatory setup-ci --doctor
-```
-
-## Target Criteria
-
-Prioritize repos with:
-
-- active MCP server maintenance
-- clear package or local startup command
-- meaningful usage, stars, directory visibility, or enterprise category
-- safe CI startup without real credentials
-- maintainers likely to value compatibility/security proof
-
-Avoid repos where:
-
-- startup requires private credentials with no fixture mode
-- the server performs irreversible side effects during startup
-- maintainers have already rejected third-party CI without a new reason to revisit
-
-## Maintainer Message
-
-```markdown
-This PR adds a read-only MCP Observatory GitHub Action for MCP compatibility, schema drift, and common security checks.
-
-It does not require an account and does not change runtime code. The workflow is read-only by default; maintainers can opt into PR comments/statuses later.
-
-I used `setup-ci --doctor` to verify the adoption kit. If the startup command should use a repo-local build instead of the published package, I can adjust it.
-```
-
-## Weekly Quota
-
-- 5 researched targets
-- 3 opened PRs
-- 1 follow-up on existing open PRs
-- 1 accepted or meaningfully discussed PR converted into proof/docs
-
-## Success Signals
-
-- accepted workflows
-- maintainer replies
-- badge adoption
-- directory mentions
-- reference evaluations linked from maintainers
-- inbound certification or pilot requests

package/docs/clone-to-ci-campaign.md

@@ -1,62 +0,0 @@
-# Clone To CI Campaign
-
-This is the operating campaign for turning anonymous clone/download activity into durable MCP Observatory adoption.
-
-## Campaign Promise
-
-Add MCP CI/security checks in 60 seconds.
-
-```bash
-npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y <server-package>"
-```
-
-## Strategy Map
-
-| Strategy | Move | Success Signal |
-| --- | --- | --- |
-| Passive credibility | Link `CLONED_THIS.md`, proof docs, badges, and sample reports from README/npm | higher repo views per clone |
-| Product-led conversion | Prompt `setup-ci` after `test`, `scan`, `diff`, `score`, and `lock verify`; expose `setup-ci --doctor` | more `setup-ci` sessions |
-| Ecosystem distribution | Submit directory/listing copy and Action examples to MCP/devtool/security indexes | more qualified clones/downloads |
-| Authority | Publish safety field reports and reference evaluations | backlinks, citations, inbound issues |
-| Certification | Open small read-only CI PRs against public MCP servers | merged PRs, maintainer replies, badge adoption |
-| Revenue | Offer private readiness reviews and hosted history to high-signal teams | pilot calls and paid reviews |
-
-## Weekly Loop
-
-1. Refresh the local metrics dashboard.
-2. Record clone/download/view and `setup-ci` conversion.
-3. Pick 5 public MCP repos for certification PRs.
-4. Submit or refresh 3 directory/listing entries.
-5. Publish one short public note from the safety findings.
-6. Draft private outreach to 3 high-signal accounts using sanitized evidence only.
-7. Generate a sanitized sample enterprise report for pilot conversations:
-   `npx @kryptosai/mcp-observatory enterprise-report --sample --format html --output reports/sample-enterprise-report.html`
-
-## Public Copy
-
-Short:
-
-> MCP Observatory adds CI, compatibility, drift, and security checks for MCP servers before agents depend on them.
-
-Clone conversion:
-
-> Cloned this? Add MCP CI in 60 seconds with `setup-ci --all`.
-
-Security-team angle:
-
-> Treat MCP servers like production dependencies: check startup, schema quality, tool safety, drift, and CI history before agents use them.
-
-## Metrics
-
-Track these in the local dashboard:
-
-- GitHub clones
-- npm downloads
-- GitHub views
-- local validation sessions
-- `setup-ci` sessions
-- clone/download to CI conversion
-- latest version adoption
-- external CI sessions
-
-The primary campaign goal is not raw clones. It is increasing `setup-ci` sessions and accepted CI/badge integrations.

package/docs/directory-listing-copy.md

@@ -1,85 +0,0 @@
-# Directory And Marketplace Listing Copy
-
-## Standard Positioning
-
-MCP Observatory is the CI and security gate for MCP servers before agents depend on them.
-
-## Short Description
-
-CI, security checks, schema drift detection, lock files, reports, and badges for MCP servers.
-
-## Medium Description
-
-MCP Observatory is a CLI, GitHub Action, and MCP server for testing MCP servers before agents depend on them. It checks tools, prompts, resources, schema quality, security footguns, regressions, and drift, then generates lock files, reports, and badges maintainers can share.
-
-## Long Description
-
-MCP Observatory gives MCP servers production safety rails: one-command CI setup, compatibility checks, security analysis, schema drift detection, lock-file verification, record/replay/verify workflows, PR comments, health score badges, and static enterprise reports. It can run as a CLI, inside GitHub Actions, or as an MCP server that lets agents inspect other MCP servers.
-
-Free for local OSS use. Paid pilots are available for hosted reporting, private repo CI history, recurring security reports, certification, support, and fleet visibility.
-
-For security and platform teams, see the MCP Server Security Field Guide and MCP Server Safety Index for agent security, AI supply chain security, and production MCP server review guidance.
-
-## Primary CTA
-
-Add MCP CI in one command:
-
-```bash
-npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y my-mcp-server"
-```
-
-## Tags
-
-### GitHub Topics
-
-- `mcp`
-- `model-context-protocol`
-- `mcp-server`
-- `mcp-testing`
-- `mcp-security`
-- `mcp-ci`
-- `schema-drift`
-- `developer-tools`
-- `security`
-- `github-action`
-
-### Directory Tags
-
-- MCP
-- Model Context Protocol
-- Security
-- Developer Tools
-- Testing
-- CI/CD
-- Schema Drift
-- Regression Testing
-- AI Agents
-
-### npm Keywords
-
-- `mcp`
-- `mcp-server`
-- `model-context-protocol`
-- `mcp-testing`
-- `mcp-security`
-- `mcp-ci`
-- `schema-drift`
-- `github-action`
-- `developer-tools`
-- `security`
-- `agent-security`
-- `ai-supply-chain`
-- `production-monitoring`
-- `enterprise-report`
-
-## Links
-
-- README: `https://github.com/KryptosAI/mcp-observatory#readme`
-- GitHub Action: `https://github.com/KryptosAI/mcp-observatory/tree/main/action`
-- Security field guide: `https://github.com/KryptosAI/mcp-observatory/blob/main/docs/mcp-security-field-guide.md`
-- Reference evaluations: `https://github.com/KryptosAI/mcp-observatory/blob/main/docs/reference-evaluations.md`
-- Safety index: `https://github.com/KryptosAI/mcp-observatory/blob/main/docs/mcp-server-safety-index.md`
-- Lock files: `https://github.com/KryptosAI/mcp-observatory/blob/main/docs/mcp-lock-files.md`
-- Certification guide: `https://github.com/KryptosAI/mcp-observatory/blob/main/docs/certification-distribution.md`
-- Proof: `https://github.com/KryptosAI/mcp-observatory/blob/main/docs/proof.md`
-- Commercial pilots: `https://github.com/KryptosAI/mcp-observatory/blob/main/COMMERCIAL.md`

package/docs/distribution-launch.md

@@ -1,76 +0,0 @@
-# Distribution And Pilot Launch
-
-Use this as the reversible launch motion for MCP Observatory commercialization.
-
-For the release gate and publication checklist, see [Publish And Distribution Readiness](./publish-readiness.md).
-For listing copy, use [Directory And Marketplace Listing Copy](./directory-listing-copy.md).
-For public proof, use [MCP Observatory Proof](./proof.md).
-
-## Positioning
-
-MCP Observatory is the CI and security gate for MCP servers before agents depend on them.
-
-## Public Surface Checklist
-
-- README pricing and enterprise CTA
-- npm description and keywords
-- GitHub repository homepage pointing to the README or commercial page
-- MCP directory listings updated with production/security language
-- Launch post published
-- Badge or certification language available for passing servers
-- Certification distribution loop published at [`docs/certification-distribution.md`](./certification-distribution.md)
-
-## Launch Post Draft
-
-MCP servers are becoming production dependencies. If an agent depends on a server, that server needs regression tests, security checks, and drift gates before it breaks workflows.
-
-MCP Observatory scans MCP servers, verifies capabilities, detects schema drift, records/replays sessions, and can run in CI or as an MCP server itself.
-
-Free for local OSS use. Paid pilots are available for hosted reporting, private repo CI, recurring security reports, certification, support, and fleet visibility.
-
-Production MCP usage? Contact william@banksey.com.
-
-## Outreach Template
-
-Subject: MCP production testing and security checks
-
-Hi,
-
-I noticed signals that your team may be evaluating or using MCP servers. MCP Observatory is the CI and security gate for MCP servers before agents depend on them.
-
-We are running a small number of production pilots for hosted reports, private repo CI, recurring security reviews, certification, support, and fleet visibility.
-
-Would it be useful to compare what your MCP servers look like today and where regressions or production risk could show up?
-
-William
-
-## Helpful Maintainer PR Motion
-
-For popular MCP server repositories, open small PRs that add:
-
-- `.github/workflows/mcp-observatory.yml`
-- optional README badge
-- a short PR body explaining the security/compatibility benefit
-
-Frame this as free OSS safety infrastructure:
-
-> I added a lightweight MCP Observatory check so users can see this server is tested for compatibility, schema drift, and common security issues. It runs in GitHub Actions, comments a readable report on PRs, and does not require an account.
-
-Use the full template in [`certification-distribution.md`](./certification-distribution.md).
-
-Track each outbound wave with [`certification-campaign-template.md`](./certification-campaign-template.md).
-
-## Account Ranking Inputs
-
-Rank prospects with:
-
-- Company domain or GitHub organization
-- Evidence source: git email domain, git remote URL, hostname domain, CI provider
-- Event count and unique sessions
-- Commands used
-- Targets or servers seen
-- Production signals: CI, private repo naming, repeated scans, security checks, matrix scans
-- Confidence: high, medium, low
-- Tier recommendation: Team, Business, Enterprise, Strategic
-
-Do not publish raw emails. Keep account evidence internal.