histor
Related Servers
Alternatives to histor
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents and gateways to seal each action into a tamper-evident W3C PROV record backed by a signed Merkle transparency log, and to fetch tree heads, inclusion and consistency proofs, verify records, and trace artifact lineage through six typed MCP tools.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides read-only MCP tools to list archived snapshots, retrieve methodology and proof bundles, and verify supplied evidence bundles.MIT
- AlicenseAqualityCmaintenanceMCP server for offline verification of signed artifacts — receipts, manifests, and audit bundles. MIT licensed, works without accounts or API calls. Tools: self_test, verify_receipt, verify_bundle, explain_artifact.495 npm6Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables searching and comparing cataloged MCP servers by capability, retrieving installation snippets and trust reports, and checking a ledger of requested abilities through MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceEnables compatible MCP clients and coding agents to index a local repository, search and trace symbols, analyze change impact, and execute verification only when explicitly authorized, returning machine-checkable evidence and limitations.Apache 2.0

marketnow-mcpofficial
FlicenseNot gradedqualityBmaintenanceEnables MCP clients and AI agents to verify credentials through a 12-stage pipeline, translate between eight credential formats, check domain risk and revocation status, search security-scored indexed MCP servers, fingerprint tool definitions, and submit scanned skills for catalog publication.-
TDQS
Scored across 3 tools
Each tool targets a distinct aspect of MCP endpoint observation: a global recent-changes feed, a verification check against a supplied tools list, and a stored per-endpoint record. The check and server tools overlap somewhat in returning historical observation details, but the need to supply a digest versus retrieving a record distinguishes them.
All three tools share the consistent 'histor_' prefix followed by a single noun/verb, with no mixing of styles (e.g., histor_changes, histor_check, histor_server). The pattern is predictable and readable.
Three tools is well-scoped for a focused, read-only history/monitoring service, with each tool covering a distinct workflow (recent changes, verification, record lookup). No bloat or thinness.
The surface covers the core read-only operations: global change feed, endpoint record retrieval, and verification of a supplied tools list. Minor gaps exist—no direct per-endpoint change listing or endpoint/registry enumeration tool—but agents can work around these via the global changes feed or record links.