# HISTOR — MCP tool-definition transparency log (pypi · aimarket-histor)

Check, diff and history of MCP tool definitions, from a public signed log of 88k+ servers.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `aimarket-histor`: 69/100 (this document), [markdown](https://verifymcp.io/servers/alexar76-histor/aimarket-histor.md), [page](https://verifymcp.io/servers/alexar76-histor/aimarket-histor)

## Channel facts

- Registry: `pypi`
- Package: `aimarket-histor`
- Version: `0.6.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.
  - 0 of 22 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 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 316 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "histor_check" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - 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 HISTOR — MCP tool-definition transparency log server?

HISTOR — MCP tool-definition transparency log runs locally as a PyPI package, launched with uvx aimarket-histor. 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 alexar76-histor -- uvx aimarket-histor
```

### Cursor

```json
{
  "mcpServers": {
    "alexar76-histor": {
      "command": "uvx",
      "args": [
        "aimarket-histor"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "alexar76-histor": {
      "command": "uvx",
      "args": [
        "aimarket-histor"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add alexar76-histor -- uvx aimarket-histor
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add alexar76-histor --command uvx --arg aimarket-histor
```

### Hermes

```yaml
mcp_servers:
  alexar76-histor:
    command: "uvx"
    args: ["aimarket-histor"]
```

### Netclaw

```json
{
  "McpServers": {
    "alexar76-histor": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "aimarket-histor"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add alexar76-histor -t stdio -c uvx -a aimarket-histor
```

### Other

```json
{
  "mcpServers": {
    "alexar76-histor": {
      "command": "uvx",
      "args": [
        "aimarket-histor"
      ]
    }
  }
}
```

## 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-05 (score 69, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 53, −14)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.5.2 → 0.6.1

### 2026-11-01 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 52)

First indexed and scored.

## MCP tools (3)

### `histor_changes` (~64 tokens)

The newest tool-definition changes HISTOR observed at remote MCP endpoints in the official registry: which tools were added, removed or modified, any outside address (host, e-mail, IP) that newly appeared, and a link to each full diff.

Input parameters:

- `limit` (integer)

### `histor_check` (~180 tokens)

Send an MCP endpoint (or registry name) and the tools/list you received, or its MTL/1 digest. Returns, signed: whether HISTOR observed the same set there, since when, earlier sets, the WARDEN pattern matches for it, and the stored advisory classifier verdict if HISTOR has one (any language; one model's opinion, not a log label). Says what was advertised, never that a server is safe.

Input parameters:

- `contribute` (boolean): add (endpoint, digest, day) to a public count
- `endpoint` (string): the MCP endpoint URL
- `name` (string): or the server's registry name
- `toolSetDigest` (string): or its MTL/1 tool-set digest (sha256-…)
- `tools` (array): the tools array of the tools/list result you received

### `histor_server` (~72 tokens)

HISTOR's observation record for one MCP endpoint (or every endpoint of a registry name): tool-set digest, tool count, first pinned, last observed, unchanged since, change count and last status, with links to the full record and its labels.

Input parameters:

- `endpoint` (string)
- `name` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 69
- 2026-11-04: 53
- 2026-11-03: 67
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 52

## Common questions

### What is the HISTOR — MCP tool-definition transparency log server?

HISTOR — MCP tool-definition transparency log is listed in the public MCP registry as io.github.alexar76/histor. Check, diff and history of MCP tool definitions, from a public signed log of 88k+ servers. This page covers its PyPI package (aimarket-histor).

### Is the HISTOR — MCP tool-definition transparency log server safe to use?

HISTOR — MCP tool-definition transparency log scores 69 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 HISTOR — MCP tool-definition transparency log server expose?

HISTOR — MCP tool-definition transparency log exposes 3 tools: histor_changes, histor_check, histor_server. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.

### Is the HISTOR — MCP tool-definition transparency log server still maintained?

HISTOR — MCP tool-definition transparency log 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 HISTOR — MCP tool-definition transparency log server under?

HISTOR — MCP tool-definition transparency log 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/aimarket-histor/
- Socket report: https://socket.dev/pypi/package/aimarket-histor
- Repository: https://github.com/alexar76/histor
- Changelog RSS feed: https://verifymcp.io/servers/alexar76-histor/aimarket-histor.xml
- Changelog JSON feed: https://verifymcp.io/servers/alexar76-histor/aimarket-histor.json
- HTML version of this page: https://verifymcp.io/servers/alexar76-histor/aimarket-histor