@kryptosai/mcp-observatory 0.23.0 → 0.25.0

package/docs/certification-campaign-template.md

@@ -42,7 +42,7 @@ Skip:
 | 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 | pr-opened | https://github.com/cyanheads/filesystem-mcp-server/pull/19 | 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 | | |
@@ -54,7 +54,7 @@ Skip:
 | 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 |
+| 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 | | |
@@ -100,7 +100,7 @@ Statuses:
 ## PR Checklist
 
 - Generate the local kit first:
-  `npx @kryptosai/mcp-observatory init-ci --all --command "<safe startup command>"`
+  `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`
@@ -151,7 +151,7 @@ The goal is to give users a visible compatibility/security signal and catch sche
 
 ## Generated PR Body Printer
 
-After running `init-ci --all`, print the generated maintainer copy with:
+After running `setup-ci --all`, print the generated maintainer copy with:
 
 ```bash
 npm run certification:pr-body -- docs/mcp-observatory-pr-body.md

package/docs/certification-distribution.md

@@ -35,7 +35,7 @@ npx @kryptosai/mcp-observatory badge npx -y <server-package> --output docs/mcp-h
 Fast path:
 
 ```bash
-npx @kryptosai/mcp-observatory init-ci --all --command "npx -y <server-package>"
+npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y <server-package>"
 ```
 
 That creates:

package/docs/directory-listing-copy.md

@@ -25,7 +25,7 @@ For security and platform teams, see the MCP Server Security Field Guide and MCP
 Add MCP CI in one command:
 
 ```bash
-npx @kryptosai/mcp-observatory init-ci --all --command "npx -y my-mcp-server"
+npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y my-mcp-server"
 ```
 
 ## Tags

package/docs/enterprise-outreach-playbook.md

@@ -3,36 +3,36 @@
 Use this playbook after running:
 
 ```bash
-npm run telemetry:intelligence -- --input telemetry-exports/events-flat-full.json --out-dir reports
+npm run telemetry:intelligence -- --input <private-telemetry-export.jsonl> --out-dir reports
 ```
 
 Start from `reports/telemetry-usage-summary.html` to confirm external usage before reading account rankings. Do not treat first-party CI, release workflows, or internal/personal sessions as market traction.
 
-Raw telemetry is allowed for internal account intelligence and may include git email, git remote URL, hostname, target command or URL, CI metadata, target IDs, and command outcomes. Do not include raw personal emails, hostnames, private URLs, target commands, tokens, or private telemetry exports in public issues, posts, docs, or customer-facing outreach. Use account domains, GitHub orgs, and aggregate telemetry evidence.
+Raw telemetry is allowed for internal account intelligence only. Do not include personal emails, hostnames, private URLs, target commands, tokens, proprietary schemas, customer names, or private telemetry exports in public issues, posts, docs, or customer-facing outreach without explicit permission. Keep account-specific rankings in ignored `reports/` outputs or private notes.
 
 ## Priority Accounts
 
 | Priority | Account | Evidence | Motion |
 | ---: | --- | --- | --- |
-| 1 | `thinkingdata.cn` | High-confidence external usage, repeated sessions, private-network target signal, Feishu/Lark MCP targets | Enterprise pilot |
-| 2 | `kimquy.capital` | Recent light usage across multiple sessions | Business pilot / design partner |
-| 3 | `paperstreetdata.com` | Small usage cluster | Business pilot / testimonial ask |
-| 4 | `cyberneticsplus.com` | Single company signal | Team pilot / feedback ask |
+| 1 | Private account A | Repeated external sessions, CI usage, private-target signal, or security workflow evidence | Enterprise pilot |
+| 2 | Private account B | Recent usage across multiple sessions or repos | Business pilot / design partner |
+| 3 | Private account C | Small usage cluster with clear owner signal | Business pilot / testimonial ask |
+| 4 | Private account D | Single company or team signal | Team pilot / feedback ask |
 | 5 | GitHub org/user signals | CI or repo-based usage | Team pilot unless company identity is confirmed |
 
-## ThinkingData First Email
+## First Email Template
 
-Subject: MCP security reporting for Feishu/Lark production workflows
+Subject: MCP security reporting for production agent workflows
 
 Hi,
 
 I build MCP Observatory, an open source tool for testing, securing, and monitoring MCP servers before agents depend on them.
 
-We are seeing serious production-style usage patterns around Feishu/Lark MCP workflows and internal HTTP MCP targets. I am opening a small number of enterprise pilots for teams that want hosted MCP security reports, private-repo CI history, and fleet visibility across agent environments.
+I am opening a small number of enterprise pilots for teams that want hosted MCP security reports, private-repo CI history, and fleet visibility across agent environments.
 
 If your team is running MCP servers in production, I can prepare a short evidence-based report and a pilot proposal focused on:
 
-- Feishu/Lark MCP compatibility
+- MCP compatibility
 - private HTTP MCP health checks
 - security findings and schema drift
 - CI history and controlled drift review

package/docs/mcp-lock-files.md

@@ -21,7 +21,7 @@ npx @kryptosai/mcp-observatory lock verify
 Add CI:
 
 ```bash
-npx @kryptosai/mcp-observatory init-ci --all --command "npx -y my-mcp-server"
+npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y my-mcp-server"
 ```
 
 ## Why It Matters

package/docs/mcp-safety-report-latest.md

@@ -24,13 +24,18 @@ Safe aggregate telemetry from the latest local export:
 
 | Metric | Value |
 | --- | ---: |
-| Total telemetry events | 10,918 |
-| Total sessions | 7,380 |
-| External sessions | 5,379 |
+| Total telemetry events | 11,481 |
+| Total sessions | 7,571 |
+| External sessions | 5,389 |
 | External CI sessions | 2,446 |
-| Attributed company/org sessions | 138 |
-| GitHub clones in visible traffic window | 721 |
-| Unique cloners in visible traffic window | 221 |
+| Attributed company/org sessions | 148 |
+| Attributed company/org candidates | 12 |
+| Latest external activity | June 21, 2026 |
+| npm downloads snapshot | 511 downloads, June 11-20, 2026 |
+| GitHub clones in visible traffic window | 745 |
+| Unique cloners in visible traffic window | 232 |
+| GitHub page views in visible traffic window | 12 |
+| Unique GitHub viewers in visible traffic window | 9 |
 
 Top external commands:
 
@@ -58,7 +63,7 @@ From public sample artifacts and Observatory check categories, the most importan
 ## How Maintainers Add The Check
 
 ```bash
-npx @kryptosai/mcp-observatory init-ci --all --command "npx -y my-mcp-server"
+npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y my-mcp-server"
 ```
 
 That creates a GitHub Action and a README badge snippet. The action can comment on PRs and fail when MCP compatibility or security checks regress.
@@ -74,7 +79,7 @@ Production teams can use MCP Observatory for:
 - support and rollout review
 - fleet visibility across teams and repos
 
-Contact `william@banksey.com` for pilots.
+See [Commercial Pilots](../COMMERCIAL.md) for production/private MCP usage.
 
 ## Launch Post
 
@@ -83,7 +88,7 @@ MCP servers are becoming production dependencies.
 I built MCP Observatory so MCP maintainers can add CI, security checks, schema drift detection, PR reports, and trust badges in one command:
 
 ```bash
-npx @kryptosai/mcp-observatory init-ci --all --command "npx -y my-mcp-server"
+npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y my-mcp-server"
 ```
 
 Free for local OSS use. Paid pilots are available for hosted reporting, private repo CI, certification, support, and fleet visibility.

package/docs/mcp-security-field-guide.md

@@ -60,7 +60,7 @@ A useful MCP server CI gate should answer a few operational questions:
 MCP Observatory is designed to make that a one-command adoption path:
 
 ```bash
-npx @kryptosai/mcp-observatory init-ci --all --command "npx -y my-mcp-server"
+npx @kryptosai/mcp-observatory setup-ci --all --command "npx -y my-mcp-server"
 ```
 
 For a direct check:

package/docs/mcp-server-safety-index.md

@@ -1,85 +1,61 @@
-# MCP Server Safety Index
-
-The MCP Server Safety Index is a public, reproducible way to show how MCP servers behave under compatibility, schema quality, drift, and security checks.
-
-The goal is constructive proof, not callouts. Each entry shows what should be tested, how to reproduce it, what risk class matters, and what a maintainer can do next.
-
-## Index v0
-
-| # | Server | Category | Reproducible Command | What To Check | Risk Class | Status |
-| ---: | --- | --- | --- | --- | --- | --- |
-| 1 | [`modelcontextprotocol/servers`](https://github.com/modelcontextprotocol/servers) sequential thinking | Reference | `npx -y @modelcontextprotocol/server-sequential-thinking@latest` | Startup, tools/list, schema quality, security-lite | Reference compatibility | PR open: [#4392](https://github.com/modelcontextprotocol/servers/pull/4392) |
-| 2 | [`modelcontextprotocol/servers`](https://github.com/modelcontextprotocol/servers) filesystem | Filesystem | `npx -y @modelcontextprotocol/server-filesystem .` | Startup in harmless temp dir, path tools, schema quality | Filesystem boundary | Researched |
-| 3 | [`upstash/context7`](https://github.com/upstash/context7) | Documentation/search | `npx -y @upstash/context7-mcp@latest` | Startup, retrieval tools, schemas, prompt-injection-sensitive text flow | Untrusted content retrieval | PR open: [#2800](https://github.com/upstash/context7/pull/2800) |
-| 4 | [`executeautomation/mcp-playwright`](https://github.com/executeautomation/mcp-playwright) | Browser automation | `npx -y @executeautomation/playwright-mcp-server@latest` | Browser tools, schema quality, intentional code-eval suppressions | Browser/code execution | PR open: [#225](https://github.com/executeautomation/mcp-playwright/pull/225) |
-| 5 | [`microsoft/playwright-mcp`](https://github.com/microsoft/playwright-mcp) | Browser automation | `npx -y @playwright/mcp@latest` | Browser tools, skip-invoke policy, schema quality, suppressions | Browser/code execution | PR open: [#1657](https://github.com/microsoft/playwright-mcp/pull/1657) |
-| 6 | [`kazuph/mcp-taskmanager`](https://github.com/kazuph/mcp-taskmanager) | Developer tools | `npx -y @kazuph/mcp-taskmanager@latest` | Task tools, schema quality, mutation clarity | Project/task mutation | PR open: [#11](https://github.com/kazuph/mcp-taskmanager/pull/11) |
-| 7 | [`cyanheads/filesystem-mcp-server`](https://github.com/cyanheads/filesystem-mcp-server) | Filesystem | `node dist/index.js` | Capability declarations, resources/list, sandboxed filesystem target | Filesystem boundary | PR open: [#19](https://github.com/cyanheads/filesystem-mcp-server/pull/19) |
-| 8 | [`browserbase/mcp-server-browserbase`](https://github.com/browserbase/mcp-server-browserbase) | Browser automation | `npx -y @browserbasehq/mcp-server-browserbase` | Auth-free startup, browser tools, network/browser boundaries | Hosted browser control | Researched; likely needs API key |
-| 9 | [`redis/mcp-redis`](https://github.com/redis/mcp-redis) | Database | `uvx mcp-redis` | Startup without live database, command surface, destructive operations | Data mutation | Researched; may need service |
-| 10 | [`mongodb-js/mongodb-mcp-server`](https://github.com/mongodb-js/mongodb-mcp-server) | Database | `npx -y mongodb-mcp-server` | Connection handling, read/write tools, auth posture | Data mutation/auth | Researched; likely needs connection string |
-| 11 | [`supabase-community/supabase-mcp`](https://github.com/supabase-community/supabase-mcp) | Database/SaaS | `npx -y supabase-mcp` | Startup, token handling, project mutation tools | Cloud data access | Researched; likely needs token |
-| 12 | [`cloudflare/mcp-server-cloudflare`](https://github.com/cloudflare/mcp-server-cloudflare) | Cloud | `npx -y @cloudflare/mcp-server-cloudflare` | Auth posture, deploy/config tools, schema clarity | Cloud control plane | Researched; likely needs auth |
-| 13 | [`stripe/agent-toolkit`](https://github.com/stripe/agent-toolkit) | Payments | `npx -y @stripe/agent-toolkit` | MCP mode, payment/customer mutation tools, auth posture | Payments/destructive action | Researched; likely needs API key |
-| 14 | [`github/github-mcp-server`](https://github.com/github/github-mcp-server) | Developer tools | `docker run ghcr.io/github/github-mcp-server` | Auth handling, repo mutation tools, schema clarity | Source-code control | Researched; likely needs token |
-| 15 | [`jetbrains/mcpProxy`](https://github.com/JetBrains/mcpProxy) | IDE/developer tools | `npx -y @jetbrains/mcp-proxy` | IDE dependency, startup behavior, tool surface | Local IDE control | Researched; may need IDE process |
-| 16 | [`BrowserMCP/mcp`](https://github.com/BrowserMCP/mcp) | Browser automation | `npx -y @browsermcp/mcp` | Browser tools, schema quality, browser-control boundary | Browser control | PR open: [#189](https://github.com/BrowserMCP/mcp/pull/189) |
-| 17 | [`UI5/mcp-server`](https://github.com/UI5/mcp-server) | Developer tools | `npx -y @ui5/mcp-server` | UI5 tooling commands, schema quality, drift risk | App development tooling | PR open: [#348](https://github.com/UI5/mcp-server/pull/348) |
-| 18 | [`antvis/mcp-server-chart`](https://github.com/antvis/mcp-server-chart) | Visualization/data | `npx -y @antv/mcp-server-chart` | Chart generation tools, schema quality, artifact-producing tools | Generated artifacts | PR open: [#312](https://github.com/antvis/mcp-server-chart/pull/312) |
-| 19 | [`makenotion/notion-mcp-server`](https://github.com/makenotion/notion-mcp-server) | SaaS/API | `npx -y @notionhq/notion-mcp-server` | Auth handling, read/write tool separation, schema quality | Workspace data access | PR open: [#324](https://github.com/makenotion/notion-mcp-server/pull/324) |
-| 20 | [`sentry/sentry-mcp`](https://github.com/getsentry/sentry-mcp) | Developer SaaS | `npx -y @sentry/mcp-server` | Auth handling, issue/project tools, schema quality | Production incident data | Researched; likely needs token |
-
-## Evaluation Command
-
-For simple npm-backed servers:
-
-```bash
-npx @kryptosai/mcp-observatory test --security npx -y <server-package>
-```
-
-For safer campaign PRs:
-
-```bash
-npx @kryptosai/mcp-observatory init-ci --all --command "npx -y <server-package>"
-```
-
-For production-style review:
-
-```bash
-npx @kryptosai/mcp-observatory lock
-npx @kryptosai/mcp-observatory lock verify
-```
-
-## What Each Column Means
-
-- What To Check: the minimum compatibility/security surface a maintainer or platform team should inspect.
-- Risk Class: the operational reason the server matters before agents depend on it.
-- Status: public proof such as PR open, PR accepted, badge added, researched, or needs maintainer review.
+# MCP Server Safety Index v1
+
+The MCP Server Safety Index is an evidence standard for MCP readiness. It is not a leaderboard and does not rank maintainers.
+
+Each row links to a reproducible command, a JSON run artifact, and a Markdown report generated by MCP Observatory. The goal is to show which failure classes matter before teams let agents depend on MCP servers.
+
+For the rules behind this page, see the [Safety Methodology](./methodology.md).
+
+## Snapshot
+
+- Evaluated servers: 13
+- Ready for CI: 10
+- Needs review before production: 1
+- Unsafe default posture: 2
+- Not reproducible: 0
+- Latest run: 2026-06-24T02:07:44.894Z
+
+## Evaluations
+
+| # | Server | Category | Verdict | Failure Class | Reproduce | Evidence | Notes |
+| ---: | --- | --- | --- | --- | --- | --- | --- |
+| 1 | [Official everything server](https://github.com/modelcontextprotocol/servers) | Reference | **Ready for CI** | Broad protocol surface | `npx -y @modelcontextprotocol/server-everything` | [JSON](./safety-index/artifacts/everything-server.json) / [report](./safety-index/artifacts/everything-server.md) | Zero-config official package; useful as a broad protocol baseline. [public proof](https://github.com/modelcontextprotocol/servers/pull/4392) |
+| 2 | [Official sequential thinking server](https://github.com/modelcontextprotocol/servers) | Reference | **Ready for CI** | Tool schema clarity | `npx -y @modelcontextprotocol/server-sequential-thinking` | [JSON](./safety-index/artifacts/sequential-thinking-server.json) / [report](./safety-index/artifacts/sequential-thinking-server.md) | Zero-config official package. |
+| 3 | [Official memory server](https://github.com/modelcontextprotocol/servers) | Reference / Memory | **Ready for CI** | Persistent state tools | `npx -y @modelcontextprotocol/server-memory` | [JSON](./safety-index/artifacts/memory-server.json) / [report](./safety-index/artifacts/memory-server.md) | Zero-config official package. |
+| 4 | [Official filesystem server](https://github.com/modelcontextprotocol/servers) | Filesystem | **Needs review before production** | Sandboxed filesystem access | `npx -y @modelcontextprotocol/server-filesystem examples/filesystem-fixture` | [JSON](./safety-index/artifacts/filesystem-server.json) / [report](./safety-index/artifacts/filesystem-server.md) | Runs against the checked-in harmless fixture directory. |
+| 5 | [Context7](https://github.com/upstash/context7) | Documentation / Search | **Ready for CI** | Prompt-injection-sensitive retrieval | `npx -y @upstash/context7-mcp` | [JSON](./safety-index/artifacts/context7-server.json) / [report](./safety-index/artifacts/context7-server.md) | Zero-config public package. |
+| 6 | [Promptopia](https://www.npmjs.com/package/promptopia-mcp) | Prompts | **Ready for CI** | Prompt/resource contract | `npx -y promptopia-mcp` | [JSON](./safety-index/artifacts/promptopia-server.json) / [report](./safety-index/artifacts/promptopia-server.md) | Uses the checked-in prompt fixture through package defaults. |
+| 7 | [Ref tools](https://www.npmjs.com/package/ref-tools-mcp) | Developer Tools | **Ready for CI** | Prompt/tool inventory | `npx -y ref-tools-mcp` | [JSON](./safety-index/artifacts/ref-tools-server.json) / [report](./safety-index/artifacts/ref-tools-server.md) | Zero-config public package. |
+| 8 | [OpenTofu MCP server](https://github.com/opentofu/opentofu-mcp-server) | Infrastructure | **Ready for CI** | Infrastructure tool surface | `npx -y @opentofu/opentofu-mcp-server` | [JSON](./safety-index/artifacts/opentofu-server.json) / [report](./safety-index/artifacts/opentofu-server.md) | Zero-config public package. |
+| 9 | [Puppeteer MCP server](https://www.npmjs.com/package/puppeteer-mcp-server) | Browser Automation | **Ready for CI** | Browser/code execution boundary | `npx -y puppeteer-mcp-server` | [JSON](./safety-index/artifacts/puppeteer-server.json) / [report](./safety-index/artifacts/puppeteer-server.md) | Intentional browser evaluation is suppressed so remaining findings stay readable. |
+| 10 | [BrowserMCP](https://github.com/BrowserMCP/mcp) | Browser Automation | **Ready for CI** | Browser-control boundary | `npx -y @browsermcp/mcp` | [JSON](./safety-index/artifacts/browsermcp-server.json) / [report](./safety-index/artifacts/browsermcp-server.md) | Zero-config public package. [public proof](https://github.com/BrowserMCP/mcp/pull/189) |
+| 11 | [Microsoft Playwright MCP](https://github.com/microsoft/playwright-mcp) | Browser Automation | **Unsafe default posture** | Browser/code execution boundary | `npx -y @playwright/mcp` | [JSON](./safety-index/artifacts/playwright-mcp-server.json) / [report](./safety-index/artifacts/playwright-mcp-server.md) | Zero-config public package; security findings represent policy-review prompts, not a vulnerability claim. |
+| 12 | [AntV chart MCP server](https://github.com/antvis/mcp-server-chart) | Visualization | **Ready for CI** | Artifact-producing tools | `npx -y @antv/mcp-server-chart` | [JSON](./safety-index/artifacts/antv-chart-server.json) / [report](./safety-index/artifacts/antv-chart-server.md) | Zero-config public package. [public proof](https://github.com/antvis/mcp-server-chart/pull/312) |
+| 13 | [ExecuteAutomation Playwright MCP](https://github.com/executeautomation/mcp-playwright) | Browser Automation | **Unsafe default posture** | Startup/listing reproducibility | `npx -y @executeautomation/playwright-mcp-server` | [JSON](./safety-index/artifacts/executeautomation-playwright-server.json) / [report](./safety-index/artifacts/executeautomation-playwright-server.md) | Evaluated as a public package; current result should be treated as a maintainer conversation starter. [public proof](https://github.com/executeautomation/mcp-playwright/pull/225) |
+
+## Patterns Observed
+
+- Browser/code execution boundary: 2 server(s)
+- Artifact-producing tools: 1 server(s)
+- Broad protocol surface: 1 server(s)
+- Browser-control boundary: 1 server(s)
+- Infrastructure tool surface: 1 server(s)
+- Persistent state tools: 1 server(s)
+- Prompt-injection-sensitive retrieval: 1 server(s)
+- Prompt/resource contract: 1 server(s)
+- Prompt/tool inventory: 1 server(s)
+- Sandboxed filesystem access: 1 server(s)
+- Startup/listing reproducibility: 1 server(s)
+- Tool schema clarity: 1 server(s)
 
 ## Publication Rules
 
-- Use only public repositories, public package commands, public PRs, or sample artifacts.
-- Include a reproduction command for every row.
-- Link to the maintainer PR or public artifact when available.
-- Phrase findings constructively: “needs review” rather than “unsafe” unless there is clear public proof.
-- Keep customer/domain telemetry internal unless the customer gives permission or there is independent public evidence.
-
-## Five Patterns To Publish From v0
-
-1. Browser automation MCP servers need explicit policy around code execution, screenshots, navigation, and mutation.
-2. Filesystem MCP servers need harmless CI sandboxes and clear read/write boundaries.
-3. SaaS and cloud MCP servers often cannot be meaningfully checked without token-safe target configs.
-4. Database MCP servers need read/write classification and connection-string hygiene before CI rollout.
-5. Lock files turn MCP surface drift into a reviewable PR event instead of an invisible agent dependency change.
-
-## Next Wave Criteria
-
-Prioritize 20-50 servers that have:
+- Use only public repositories, public package commands, public PRs, and generated sanitized artifacts.
+- Treat findings as reproducible evidence, not public shaming.
+- Prefer “needs review” language unless there is clear artifact-backed proof of a dangerous default.
+- Keep raw telemetry, emails, hostnames, private URLs, tokens, and customer claims out of public materials.
+- Send maintainers the report first; open CI PRs only when the report is useful and the target can run safely.
 
-- active maintenance in the last 90 days
-- visible stars, downloads, or directory listings
-- simple `npx`, `uvx`, or Docker startup commands
-- enterprise-relevant categories such as browser automation, filesystem, documentation/search, databases, cloud, productivity, and developer tools
-- no existing MCP compatibility/security CI
+## Next Step
 
-One accepted PR in a respected repo is worth more than a large list of shallow checks.
+Use this index to start maintainer conversations and private readiness reviews. The buyer-facing offer is a private MCP readiness review with CI rollout, drift/security reporting, and safe-for-agent-dependency verdicts.

package/docs/methodology.md

@@ -0,0 +1,90 @@
+# MCP Observatory Safety Methodology
+
+MCP Observatory treats MCP servers as agent-facing dependencies. The Safety Index is designed to answer one practical question:
+
+> Is this server ready for agents and teams to depend on, and what evidence supports that answer?
+
+The index is not a leaderboard. It is a reproducible evidence standard for maintainers, security teams, platform teams, and buyers evaluating MCP servers.
+
+## What Gets Tested
+
+Each public evaluation runs MCP Observatory against a public repository or package command. A useful entry includes:
+
+- server name and public source
+- exact command and arguments
+- run date
+- MCP Observatory version
+- JSON run artifact
+- Markdown report
+- verdict
+- failure class
+- reproduction notes
+
+The default public check verifies startup, tools, prompts, resources, schema quality, and lightweight security findings. Some entries also include deeper security checks when the target can be evaluated without private credentials.
+
+## Verdicts
+
+- **Ready for CI:** the server starts, lists expected MCP surfaces, and has no high- or medium-severity security finding in the generated artifact.
+- **Needs review before production:** the server is reproducible but has findings or partial results a maintainer/security reviewer should inspect before production use.
+- **Not reproducible:** the server cannot complete a basic startup or listing check from the documented public command.
+- **Unsafe default posture:** the artifact contains high-severity security findings that deserve explicit policy review before agent dependency.
+- **Could not evaluate:** the public command cannot be evaluated without credentials, private infrastructure, or maintainer-provided safe configuration.
+
+These verdicts are intentionally operational. They are not formal vulnerability claims.
+
+## Scoring Inputs
+
+MCP Observatory uses the same run artifact model across CLI, CI, reports, and the Safety Index. The health score considers:
+
+- protocol compliance
+- schema quality
+- security and security-lite checks
+- reliability/startup behavior
+- performance where latency data is available
+
+The Safety Index does not rank by score. Scores are supporting evidence; failure classes are the story.
+
+## Failure Classes
+
+Common MCP readiness patterns include:
+
+- startup/listing reproducibility
+- browser/code execution boundary
+- filesystem boundary
+- prompt-injection-sensitive retrieval
+- persistent state tools
+- infrastructure or cloud control surfaces
+- artifact-producing tools
+- schema clarity and drift
+- token-safe configuration
+
+The first public index emphasizes these classes so maintainers can improve concrete surfaces rather than argue about a single trust score.
+
+## Reproducibility Rules
+
+An index row should be included only when it can be reproduced from public information:
+
+- public repo, package, or container reference
+- no private telemetry
+- no private customer evidence
+- no raw emails, hostnames, private URLs, tokens, or response bodies
+- a generated JSON artifact and Markdown report
+- clear notes when credentials or maintainer context are required
+
+If the safe public command is not known, the right next step is a maintainer note, not a drive-by CI PR.
+
+## Maintainer Posture
+
+The index is constructive by default:
+
+- send the report first
+- describe the failure class, not the maintainer
+- offer a CI PR only if the target can run safely and the maintainer wants it
+- prefer read-only workflows and pinned action refs for third-party repos
+- use issue-first outreach for token-backed SaaS, cloud, payments, database, and browser-control servers
+
+## Limitations
+
+MCP Observatory cannot prove semantic safety. A passing result does not mean a server is safe for every workflow. It means the server produced reproducible evidence for compatibility, schema quality, and common security footguns under the tested command.
+
+Production teams should pair these checks with their own threat model, policy, credential boundaries, sandboxing, approvals, and runtime monitoring.

package/docs/metrics-dashboard.md

@@ -0,0 +1,108 @@
+# Local Metrics Dashboard
+
+MCP Observatory includes a private laptop dashboard for collecting telemetry, GitHub activity, and npm download data going forward.
+
+The dashboard is intentionally local. It stores raw telemetry in a SQLite database on your laptop, then renders a sanitized static HTML view that is safe to screenshot or skim without exposing raw emails, hostnames, private URLs, tokens, or private command bodies.
+
+The layout follows an App Store Connect-style breakdown:
+
+- Overview
+- Strategy
+- Acquisition
+- Downloads
+- Usage
+- Reliability
+
+The Strategy section turns raw telemetry into operator decisions: command funnel, version adoption, account/domain drilldown, CI/local source mix, and release-spike context.
+
+Daily rows are shown newest to oldest so the most recent project activity is always at the top.
+
+## Refresh
+
+```bash
+npm run metrics:refresh
+npm run metrics:serve
+```
+
+Outputs are written to:
+
+- `.mcp-observatory-metrics/observatory.sqlite`
+- `.mcp-observatory-metrics/dashboard/index.html`
+- `.mcp-observatory-metrics/dashboard/latest.json`
+- `.mcp-observatory-metrics/logs/`
+
+The local metrics directory is ignored by git and should not be published.
+
+## Data Sources
+
+The collector stores each source independently. If one source fails, the dashboard still builds from the last good SQLite data and records the failure in the Reliability section.
+
+| Source | Data |
+| --- | --- |
+| Telemetry | Existing Cloudflare D1 export flow via `scripts/export-telemetry-d1.ts` |
+| GitHub | clones, views, referrers, popular paths, repo snapshot, latest release, open issue/PR counts, workflow runs |
+| npm | public daily downloads for `@kryptosai/mcp-observatory` |
+
+GitHub traffic APIs have a limited visible window, so the collector stores snapshots locally going forward. npm daily buckets can lag; the dashboard labels npm data as complete public days rather than assuming current-day zero.
+
+## Credentials
+
+GitHub collection uses either:
+
+```bash
+gh auth login
+```
+
+or:
+
+```bash
+export GH_TOKEN=...
+```
+
+Telemetry collection uses the same Wrangler configuration as the existing telemetry export script. If the config is not auto-discovered, set:
+
+```bash
+export MCP_OBSERVATORY_TELEMETRY_WRANGLER_CONFIG=/path/to/wrangler.toml
+export MCP_OBSERVATORY_TELEMETRY_D1_DATABASE=mcp-observatory-telemetry
+```
+
+No npm token is required for public download counts.
+
+## Commands
+
+```bash
+npm run metrics:collect   # collect telemetry, GitHub, and npm into SQLite
+npm run metrics:build     # render HTML from the existing SQLite database
+npm run metrics:refresh   # collect + build
+npm run metrics:open      # open the static read-only dashboard
+npm run metrics:serve     # open the local dashboard with an Update Data button
+```
+
+The **Update Data** button is available in `metrics:serve` mode. A static `file://` dashboard cannot run local commands from the browser, so `metrics:open` shows the same data but disables the button.
+
+For tests or offline recovery, you can seed telemetry from an existing export:
+
+```bash
+npm run metrics:refresh -- --telemetry-input telemetry-exports/events-flat-full.json
+```
+
+## Optional Hourly Refresh
+
+Generate a small local refresh wrapper:
+
+```bash
+npx tsx scripts/metrics-dashboard.ts scheduler
+```
+
+The generated script lives under `.mcp-observatory-metrics/` and can be called by `launchd` or cron. It uses the same refresh command and writes logs to `.mcp-observatory-metrics/logs/refresh.log`.
+
+## Privacy
+
+Raw telemetry remains available in the local SQLite database for account intelligence and product analytics. The dashboard view uses sanitized aggregates by default:
+
+- company domains, not raw emails
+- aggregate source and command counts, not private command bodies
+- GitHub and npm public metrics
+- collection errors and freshness status
+
+Do not commit `.mcp-observatory-metrics/`, telemetry exports, private reports, or screenshots that reveal raw data.

package/docs/paid-pilot-offer.md

@@ -17,11 +17,13 @@ This is a manual pilot, not a self-serve SaaS promise.
 
 ## What The Pilot Includes
 
-- review of the customer’s MCP config, repo, or startup commands
-- MCP Observatory CI rollout for selected servers
+- MCP server inventory across selected repos, configs, or agent environments
+- reproducible test artifacts for each reviewed server
 - private readiness report covering startup, capabilities, schema quality, security findings, and drift risk
-- MCP lock-file setup for contract drift review
-- prioritized remediation notes
+- schema/tool drift baseline using MCP lock files
+- MCP Observatory CI rollout plan for selected servers
+- executive summary with “safe for agent dependency” verdicts
+- prioritized remediation notes and owner-ready next steps
 - optional certification language for servers that pass agreed checks
 
 ## Starting Prices
@@ -55,4 +57,18 @@ William
 
 ## Delivery Shape
 
-Start with static reports and CI setup. Do not build a dashboard until paid pilot feedback proves exactly what buyers need.
+Start with static reports and CI setup. The first deliverable should look like an internal security/readiness packet, not a SaaS login.
+
+## Evidence Standard
+
+The public [Safety Methodology](./methodology.md) and [MCP Server Safety Index](./mcp-server-safety-index.md) are the template for private work:
+
+- command/config used
+- date and tool version
+- JSON artifact
+- Markdown or HTML report
+- failure class
+- verdict
+- reproduction notes
+
+Private pilots can include customer-specific details, but public/customer-facing summaries should use sanitized evidence unless the customer approves otherwise.

package/docs/project-case-study.md

@@ -57,14 +57,15 @@ For deeper context, see the [MCP Server Security Field Guide](./mcp-security-fie
 
 Telemetry is used privately to understand product usage and identify account-level signals without publishing raw personal data.
 
-As of the latest local export on June 20, 2026:
+As of the latest local export on June 21, 2026:
 
-- 10,918 telemetry events
-- 7,380 total sessions
-- 5,379 external sessions after separating internal activity
+- 11,481 telemetry events
+- 7,571 total sessions
+- 5,389 external sessions after separating internal activity
 - 2,446 external CI sessions
-- 138 attributed company/org sessions
-- 11 attributed company/org candidates
+- 148 attributed company/org sessions
+- 12 attributed company/org candidates
+- latest external activity: June 21, 2026
 
 Public claims use aggregate or sanitized data only. Raw emails, hostnames, private URLs, tokens, and response bodies are not published.
 
@@ -77,9 +78,12 @@ Current public distribution proof includes:
 - latest release: `v0.23.0`
 - npm package: `@kryptosai/mcp-observatory`
 - GitHub Action: `KryptosAI/mcp-observatory/action@main`
-- visible GitHub traffic window: 721 clones and 221 unique cloners
+- npm downloads snapshot: 511 downloads for June 11-20, 2026
+- visible GitHub traffic window: 745 clones and 232 unique cloners
+- visible GitHub page-view window: 12 views and 9 unique visitors
+- public code-search references in MCP indexes, listing mirrors, and external experiment repos
 - official MCP reference PR open and green: [`modelcontextprotocol/servers#4392`](https://github.com/modelcontextprotocol/servers/pull/4392)
-- open certification PRs for Microsoft Playwright MCP, Upstash Context7, ExecuteAutomation Playwright MCP, and other MCP projects
+- open certification PRs for Microsoft Playwright MCP, Upstash Context7, ExecuteAutomation Playwright MCP, AntV, BrowserMCP, UI5, Notion, and other MCP projects
 
 See [reference evaluations](./reference-evaluations.md) and [public proof](./proof.md).