Analytics

holoweave.org

Performs automated citation and claim checks in documents, verifying counts, listings, vocabulary consistency, totals, and internal references.

x402 supported2 endpoints8 known toolsFirst detected August 8, 2026Last detected August 8, 2026

ENDPOINT 1

https://check.holoweave.org/mcp

No auth detected

MCP server metadata

Name: citation-check
Version: 0.1.0

Capabilities

tools

Known tools 1

citation_check

Mechanical citation/claim checks for a document: counts whose members are not named, listings that do not match contents, marker vocabulary drift, totals graded above their weakest part, and internal references that resolve to nothing.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.citation-check]
url = "https://check.holoweave.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "citation-check": {
      "type": "http",
      "url": "https://check.holoweave.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: citation-check
Remote MCP URL: https://check.holoweave.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "citation-check": {
      "url": "https://check.holoweave.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "citation-check": {
      "type": "http",
      "url": "https://check.holoweave.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "citation-check",
  "transport": "streamable-http",
  "url": "https://check.holoweave.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://witness.holoweave.org/mcp

No auth detected

MCP server metadata

Name: auto-witness
Version: 0.2.0

Capabilities

tools

Server instructions

Seven paid tools, each returning an Ed25519-signed attestation: witness_url and read_url (what a public URL served, with SHA-256 and text), check_ai_permission (may this agent fetch or train on a URL, per robots.txt RFC 9309 and published signals), check_tx_finality (did a Base USDC transfer settle and is it final), witness_keys (a counterparty's JWKS by thumbprint, and whether it rotated), pin_tool_surface and check_tool_surface_drift (an MCP server's tools/list, pinned and diffed). You keep the baseline; we store no digest and keep no record of which server you watch. Ordinary short-lived web-server logging applies, described at https://witness.holoweave.org/datenschutz.html. Every answer is an Ed25519-signed attestation anyone can verify against https://witness.holoweave.org/v1/key, so it is evidence a third party can check rather than a report you have to trust.

Known tools 7

pin_tool_surface

Compute a stable digest over an MCP server's tools/list — each tool's name, description and inputSchema — and return a signed attestation.

Inferred read-only

check_tool_surface_drift

Compare an MCP server's current tools/list against a baseline digest you hold and return a signed attestation naming every tool added, removed or silently redefined since then.

Inferred read-only

witness_url

Fetch a public URL and return signed, timestamped evidence of what it served: status, provenance headers, SHA-256 of the body.

Inferred read-only

check_tx_finality

Read a Base transaction's receipt and return a signed settlement statement: succeeded or reverted, every USDC transfer it carried, block time, confirmations, and whether the block is safe or finalized by the chain's own tags.

Potential side effects

check_ai_permission

May a named AI agent fetch, or train on, a URL?

Inferred read-only

witness_keys

Fetch a counterparty's JWK Set (OIDC jwks_uri or web bot auth key directory) and return a signed record of every key by RFC 7638 thumbprint, its defects, and a set digest; pass your prior digest or thumbprints to be told whether the keys rotated and which.

Inferred read-only

read_url

Fetch a public page and return its title and extracted text, bound to signed evidence of the bytes it came from — URL, time, status, SHA-256 — so what you quote is traceable to what was served.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.auto-witness]
url = "https://witness.holoweave.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "auto-witness": {
      "type": "http",
      "url": "https://witness.holoweave.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: auto-witness
Remote MCP URL: https://witness.holoweave.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "auto-witness": {
      "url": "https://witness.holoweave.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "auto-witness": {
      "type": "http",
      "url": "https://witness.holoweave.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "auto-witness",
  "transport": "streamable-http",
  "url": "https://witness.holoweave.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for holoweave.org was fetched 2026-08-21T13:35:04.184Z.

Trust status New

This domain appears to have previously been parked, so its current status is new or unverified.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.