# sota-anchor (pypi · sota-anchor)

Finds what shipped after your coding agent's training, before it rebuilds it from scratch.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `sota-anchor`: 84/100 (this document), [markdown](https://verifymcp.io/servers/luckmanqasim-sota-anchor/sota-anchor.md), [page](https://verifymcp.io/servers/luckmanqasim-sota-anchor/sota-anchor)

## Channel facts

- Registry: `pypi`
- Package: `sota-anchor`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 2 of 34 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 28 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 399 tokens (~199/item across 2 items; 1 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the sota-anchor MCP server?

sota-anchor runs locally as a PyPI package, launched with uvx sota-anchor. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add luckmanqasim-sota-anchor -- uvx sota-anchor
```

### Cursor

```json
{
  "mcpServers": {
    "luckmanqasim-sota-anchor": {
      "command": "uvx",
      "args": [
        "sota-anchor"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "luckmanqasim-sota-anchor": {
      "command": "uvx",
      "args": [
        "sota-anchor"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add luckmanqasim-sota-anchor -- uvx sota-anchor
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "luckmanqasim-sota-anchor": {
      "type": "local",
      "command": [
        "uvx",
        "sota-anchor"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add luckmanqasim-sota-anchor --command uvx --arg sota-anchor
```

### Hermes

```yaml
mcp_servers:
  luckmanqasim-sota-anchor:
    command: "uvx"
    args: ["sota-anchor"]
```

### Netclaw

```json
{
  "McpServers": {
    "luckmanqasim-sota-anchor": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "sota-anchor"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add luckmanqasim-sota-anchor -t stdio -c uvx -a sota-anchor
```

### Other

```json
{
  "mcpServers": {
    "luckmanqasim-sota-anchor": {
      "command": "uvx",
      "args": [
        "sota-anchor"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 84, +16)

- [security improvement] Malware scan: unverified → pass
- [security] Stability: 0.97 → pass

### 2026-11-01 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-30 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-28 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 64, −14)

- [security regression] Malware scan: pass → unverified

## MCP tools (1)

### `check_what_exists` (~274 tokens)

Check what already exists

Check whether a plan relies on something being unavailable that may no longer be: no library or reader for a file format, only a vendor SDK able to open it, no API for the data, or a model that cannot do the task. Call it before writing a custom parser, converter or reader, rewriting something from scratch, or adding a workaround, heuristic pipeline or post-processing stage, in any domain - and before telling a user that no tool or library exists for something. Call it with just the pitch first: it returns an inversion prompt asking what would have to be unavailable for the plan to be justified. Answer that, then call again with domain_query (the task in its own vocabulary) and capability_query (whatever would make the workaround unnecessary: an existing implementation, library, tool or model capability), each led by its most specific term, such as a format, product or library name. It returns dated evidence from papers, repositories and package registries, plus the standard for judging it: either the limitation still holds, or an assertion-reason update naming what replaces the workaround. Two queries because a narrow one misses a general advance indexed elsewhere. Raise months if a pass returns nothing.

Input parameters:

- `capability_query`
- `domain_query`
- `months` (integer)
- `pitch` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/luckmanqasim-sota-anchor/sota-anchor#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 68
- 2026-11-01: 68
- 2026-10-31: 67
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 66
- 2026-10-27: 65
- 2026-10-26: 65
- 2026-10-25: 64
- 2026-10-24: 64
- 2026-10-23: 64
- 2026-10-22: 78
- 2026-10-21: 63
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 61
- 2026-10-17: 76
- 2026-10-16: 60
- 2026-10-15: 75
- 2026-10-14: 74
- 2026-10-13: 40
- 2026-10-12: 40
- 2026-10-04: 69

## Common questions

### What is the sota-anchor MCP server?

sota-anchor is an MCP server listed in the public MCP registry as io.github.luckmanqasim/sota-anchor. Finds what shipped after your coding agent's training, before it rebuilds it from scratch. This page covers its PyPI package (sota-anchor).

### Is the sota-anchor MCP server safe to use?

sota-anchor scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the sota-anchor MCP server expose?

sota-anchor exposes 1 tool: check_what_exists. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.

### Is the sota-anchor MCP server still maintained?

sota-anchor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the sota-anchor MCP server under?

sota-anchor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/sota-anchor/
- Socket report: https://socket.dev/pypi/package/sota-anchor
- Repository: https://github.com/luckmanqasim/sota-anchor
- Changelog RSS feed: https://verifymcp.io/servers/luckmanqasim-sota-anchor/sota-anchor.xml
- Changelog JSON feed: https://verifymcp.io/servers/luckmanqasim-sota-anchor/sota-anchor.json
- HTML version of this page: https://verifymcp.io/servers/luckmanqasim-sota-anchor/sota-anchor