Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"scry-mcp-2","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# scry Marker-indexed SQL cache MCP server. Scry indexes in-file `@scry.*` markers into a SQLite database that agents query via read-only SQL, providing structured project knowledge without LLM reasoning. [](https://pypi.org/project/scry-mcp/) [](https://pypi.org/project/scry-mcp/) ## Install ```bash uv pip install scry-mcp # or: pip install scry-mcp ``` The PyPI distribution is `scry-mcp` (the bare name `scry` was already taken on PyPI). The import name and the installed console command are both `scry`. ## Quickstart ```bash # In your project root: scry init # scaffolds agent/ + driver dirs, updates .gitignore ``` Then add it to your MCP client config: ```json { "mcpServers": { "scry": { "command": "scry" } } } ``` The MCP client inherits cwd from wherever it's launched, and scry walks up from there looking for an `agent/` directory — so the same config works for any project. Bare `scry` (no subcommand) starts the MCP server over stdio — that's what Claude calls. Other subcommands: | Command | Purpose | |---|---| | `scry` | Run the MCP server (default). | | `scry init [path]` | Create `agent/` + `agent/drivers/@local/scry/{data,runtime,scripts}/` and a local `.gitignore` inside the driver dir. Idempotent — safe to run inside an ACP project. | | `scry surface [--force]` | One-shot batch reindex without booting the server. | | `scry version` | Print the package version. | The server walks up from `cwd` until it finds an `agent/` directory; that becomes the project root. The cache lives at `agent/drivers/@<namespace>/scry/data/project.db` and is gitignored. ## Markers Scry recognizes three marker kinds per scry-spec v1.1: `@scry.entry` and `@scry.anchor` are block markers with a YAML body between open/close tokens; `@scry.bind` is a line or block marker declaring cross-references. ```html <!-- @scry.entry id:…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.