# io.github.vitaliyino/scority (pypi · scority-core)

Technical SEO and AI-answer-readiness audit. Keyless; the metered tool refuses to spend silently.

- Trust score: 31/100 (low)
- Change this week: −6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-23

## Components

- pypi · `scority-core`: 31/100 (this document), [markdown](https://verifymcp.io/servers/vitaliyino-scority/scority-core.md), [page](https://verifymcp.io/servers/vitaliyino-scority/scority-core)

## Channel facts

- Registry: `pypi`
- Package: `scority-core`
- Version: `0.1.2`
- 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-08-23.

- **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 native-build step with no shell scripting around it.
  - 0 of 23 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 5 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.

**Unverified: 4 categories.** Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the io.github.vitaliyino/scority MCP server?

io.github.vitaliyino/scority runs locally as a PyPI package, launched with uvx scority-core. 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 vitaliyino-scority -- uvx scority-core
```

### Cursor

```json
{
  "mcpServers": {
    "vitaliyino-scority": {
      "command": "uvx",
      "args": [
        "scority-core"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vitaliyino-scority": {
      "command": "uvx",
      "args": [
        "scority-core"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add vitaliyino-scority -- uvx scority-core
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add vitaliyino-scority --command uvx --arg scority-core
```

### Hermes

```yaml
mcp_servers:
  vitaliyino-scority:
    command: "uvx"
    args: ["scority-core"]
```

### Netclaw

```json
{
  "McpServers": {
    "vitaliyino-scority": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "scority-core"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add vitaliyino-scority -t stdio -c uvx -a scority-core
```

### Other

```json
{
  "mcpServers": {
    "vitaliyino-scority": {
      "command": "uvx",
      "args": [
        "scority-core"
      ]
    }
  }
}
```

## 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-08-18 (score 31, −6)

- [security regression] Source repository: pass → fail
- [functional regression] Security disclosure: pass → unverified

### 2026-08-16 (score 37)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

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

## Score history

- 2026-08-23: 31
- 2026-08-22: 31
- 2026-08-21: 31
- 2026-08-20: 31
- 2026-08-19: 31
- 2026-08-18: 31
- 2026-08-17: 37
- 2026-08-16: 37

## Common questions

### What is the io.github.vitaliyino/scority MCP server?

io.github.vitaliyino/scority is an MCP server listed in the public MCP registry as io.github.vitaliyino/scority. Technical SEO and AI-answer-readiness audit. Keyless; the metered tool refuses to spend silently. This page covers its PyPI package (scority-core).

### Is the io.github.vitaliyino/scority MCP server safe to use?

io.github.vitaliyino/scority scores 31 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 August 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.

### Is the io.github.vitaliyino/scority MCP server still maintained?

io.github.vitaliyino/scority is still listed as active in the MCP registry. We last reached this channel on 23 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/scority-core/
- Socket report: https://socket.dev/pypi/package/scority-core
- Changelog RSS feed: https://verifymcp.io/servers/vitaliyino-scority/scority-core.xml
- Changelog JSON feed: https://verifymcp.io/servers/vitaliyino-scority/scority-core.json
- HTML version of this page: https://verifymcp.io/servers/vitaliyino-scority/scority-core