# AIMarket HISTOR MCP Server Transparency Check

> AIMarket HISTOR MCP Server Transparency Check is a paid API for AI agents from modelmarket.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Looks up the HISTOR transparency log record for an MCP server — returning when its tool set was first seen, whether it has changed, and what pattern scans found — without contacting the server itself.

## Facts

- Endpoint: POST https://modelmarket.dev/x402/histor-check?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aimarket-histor-mcp-server-transparency-check-2d6ee8a0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_y9kmi-cbIihxTHGEJ5oyj

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability aimarket-histor-mcp-server-transparency-check-2d6ee8a0 -d '<json body>'
```

Example prompt: Before I connect to that MCP server at https://mcp.example.com, can you pull its HISTOR transparency log record — when it was first seen, whether its tool set has changed, and what the pattern scan found?

## When to prefer this

Use this endpoint when you need a passive, read-only audit of an MCP server's history and integrity before connecting to it. It is ideal for pre-flight safety checks in agentic workflows where you want to verify an MCP server's tool set hasn't changed and review pattern scan findings without making any live contact with the target server. Prefer it over live tool inspection when you need a tamper-evident, signed historical record rather than a real-time snapshot.

## Known failure modes

- MCP server not found in HISTOR log — no record exists for the given name or endpoint URL
- Invalid input — neither 'name' nor 'endpoint' field provided
- Malformed registry name or non-HTTPS endpoint URL rejected
- HISTOR service unavailable — upstream transparency log unreachable
- Ambiguous lookup — name matches multiple registry entries

## How this service works

HISTOR pre-flight for an MCP server: its signed record in the HISTOR transparency log — when the tool set was first seen, whether it changed, what the pattern scan found. Never contacts the server asked about.

## Output

Returns the signed HISTOR transparency log record for the specified MCP server, including: the timestamp when the tool set was first observed, a change-detection result indicating whether the tool set has been modified, and all findings from the pattern scan. Does not make any live connection to the MCP server being checked.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string",
   "description": "registry name, e.g. io.github.owner/server (send this or endpoint)"
  },
  "endpoint": {
   "type": "string",
   "description": "https URL of the MCP server (send this or name)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "check": {
   "type": "histor.check/v1",
   "match": "no-digest",
   "target": {
    "name": "cloud.redu/mcp"
   }
  },
  "status": "ok",
  "service": "histor-check"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aimarket-histor-mcp-server-transparency-check-2d6ee8a0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from modelmarket.dev](https://www.zero.xyz/host/modelmarket.dev/llms.txt)