General Tools

vehcdj664efetfrsolne5umanq.srv.us

Provides general-purpose tools through the Model Context Protocol.

1 endpoint11 known toolsFirst detected October 13, 2026Last detected October 13, 2026

ENDPOINT 1

https://vehcdj664efetfrsolne5umanq.srv.us/mcp

No auth detected

MCP server metadata

Name: attestpage
Version: 0.1.0

Capabilities

tools

Server instructions

Signed evidence about web pages from https://vehcdj664efetfrsolne5umanq.srv.us: check a quote is on a page before citing it, check every quote and link in a finished document, fetch a page with a verdict on what came back (real page, bot wall, paywall, error), check links, check package names before installing them, or timestamp a SHA-256. Each answer has a "receipt" (an Ed25519-signed JWS); check one with attestpage_verify_receipt (free). A receipt records what the fetcher saw at a given time; it does not show that a statement is correct.

Known tools 11

attestpage_verify_quote

Use when an agent is about to quote or cite a web page as the source of a claim: send the URL and the quote word for word, and get back exact, fuzzy or none, offsets and a signed receipt, so a misquote is caught before a user sees it.

Potential side effects

attestpage_verify_citations

Use before giving an answer that cites web pages: send up to 10 quote and URL pairs, and get back for each an exact, fuzzy or none match, offsets and page status, under one signed receipt: a fact check of each citation against its source.

Potential side effects

attestpage_fetch

Use when an agent needs a web page as clean text, or to notarize one (what it said, and when): send a URL (or urls, up to 10, priced per URL), and get back a content_kind (real, bot_wall, paywall and more), status, final URL, title, hashes, injection flags, clean text with return_text, and a signed receipt per page (checkable offline), so a bot wall is not read as real.

Potential side effects

attestpage_recheck

Use when an agent relies on a web page it read earlier and needs page change detection (does it still say the same thing?

Inferred read-only

attestpage_check_links

Use when an agent is about to give a user links or citations: send up to 10 URLs, and get back for each one the status, redirect chain, final URL, content_kind, title and hash, so a dead, moved or blocked link is caught before it is shown.

Potential side effects

attestpage_check_packages

Use when an agent is about to install or recommend a package an LLM suggested: send up to 10 names, each with its registry (npm, pypi, crates), and get back whether the registry lists each name, latest version, licence, links, flags and known OSV.

Potential side effects

attestpage_attest

Use when an agent needs to show later that a file, answer or record existed unchanged at a point in time: send its sha256, and get back a signed, timestamped receipt over it; a later altered copy no longer matches.

Potential side effects

attestpage_verify_document

Use before sending a finished answer or report that quotes web pages: send the document as written, and get back every quote with its link, checked on the live page: exact, fuzzy or none, score, offsets and each page's status, under one signed receipt.

Potential side effects

attestpage_verify_quotes

Use when an agent is about to quote one web page several times: send the URL and up to 20 quotes in your exact words, and get back for each one exact, fuzzy or none, with offsets and context, plus the page's verdict and hashes, under one signed receipt.

Potential side effects

attestpage_verify_receipt

Use when you are handed an AttestPage evidence receipt and need to check it before relying on it: verifies the compact JWS against this service's published keys and returns its payload, so a forged or altered receipt is caught.

Inferred read-only

attestpage_preview_document

Use before paying for POST /v1/verify/document: send the same body, and get back the quote and link pairs it would check, what was skipped and why, the number of parts and the exact price.

Potential side effects

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.attestpage]
url = "https://vehcdj664efetfrsolne5umanq.srv.us/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "attestpage": {
      "type": "http",
      "url": "https://vehcdj664efetfrsolne5umanq.srv.us/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: attestpage
Remote MCP URL: https://vehcdj664efetfrsolne5umanq.srv.us/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": {
    "attestpage": {
      "url": "https://vehcdj664efetfrsolne5umanq.srv.us/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "attestpage": {
      "type": "http",
      "url": "https://vehcdj664efetfrsolne5umanq.srv.us/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "attestpage",
  "transport": "streamable-http",
  "url": "https://vehcdj664efetfrsolne5umanq.srv.us/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

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