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.
Available components
Last scanned (21 hours ago)
Scores higher than 56% of PyPI servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 22 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 316 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.5.2 → 0.6.1 functional
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 52
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/aimarket-histor@0.6.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
histor_changes ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
histor_check ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
histor_server ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | – | – |
| name | string | – | – |
No output schema declared.
No examples provided.
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.
pypi · aimarket-histor
claude mcp add alexar76-histor -- uvx aimarket-histor
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 53 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 4 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.