Content Tools

stoneytech.net

Manages and retrieves published content and site metadata for a StoneyTECH site.

2 endpoints22 known toolsFirst detected May 23, 2026Last detected September 18, 2026

ENDPOINT 1

https://public-content-mcp.stoneytech.net/mcp

No auth detected

Known tools 9

get_site_overview

Return the published StoneyTECH site identity, counts, routes, and public boundary.

Inferred read-only

list_published_content

List published pages, articles, axioms, builds, or public repositories.

Inferred read-only

get_published_item

Fetch one published item by contract id, route path, or canonical URL.

Inferred read-only

search_published_content

Search only the generated published-content text index.

Inferred read-only

list_axioms

List published StoneyTECH axioms with citations and applied evidence counts.

Inferred read-only

get_applied_evidence

Fetch published applied-evidence records by content id or axiom number.

Inferred read-only

list_proof_receipts

List public proof-of-work receipts by status or ladder rung.

Inferred read-only

get_proof_receipts_for_published_item

Fetch proof receipts for one published item by contract id, route path, or canonical URL.

Inferred read-only

explain_public_narrative

Explain StoneyTECH as a cold-reader using only the published contract.

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.stoneytech-net]
url = "https://public-content-mcp.stoneytech.net/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "stoneytech-net": {
      "type": "http",
      "url": "https://public-content-mcp.stoneytech.net/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: stoneytech-net
Remote MCP URL: https://public-content-mcp.stoneytech.net/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": {
    "stoneytech-net": {
      "url": "https://public-content-mcp.stoneytech.net/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "stoneytech-net": {
      "type": "http",
      "url": "https://public-content-mcp.stoneytech.net/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "stoneytech-net",
  "transport": "streamable-http",
  "url": "https://public-content-mcp.stoneytech.net/mcp"
}

MCP Inspector

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

ENDPOINT 2

https://stoneytech.net/public-content/mcp

No auth detected

MCP server metadata

Name: stoneytech-public-content-mcp
Version: 0.1.0

Capabilities

tools.listChangedresources.listChanged

Known tools 13

get_site_overview

Return the published StoneyTECH site identity, counts, routes, and public boundary.

Inferred read-only

list_published_content

List published pages, articles, axioms, builds, or public repositories.

Inferred read-only

get_published_item

Fetch one published item by contract id, route path, or canonical URL.

Inferred read-only

search_published_content

Search only the generated published-content text index.

Inferred read-only

list_axioms

List published StoneyTECH axioms with citations and applied evidence counts.

Inferred read-only

get_applied_evidence

Fetch published applied-evidence records by content id or axiom number.

Inferred read-only

list_proof_receipts

List public proof-of-work receipts by status or ladder rung.

Inferred read-only

get_proof_receipts_for_published_item

Fetch proof receipts for one published item by contract id, route path, or canonical URL.

Inferred read-only

get_graph_neighbors

Traverse the published StoneyTECH graph from one node id and return inbound or outbound neighbors.

Inferred read-only

explain_public_narrative

Explain StoneyTECH as a cold-reader using only the published contract.

Inferred read-only

get_build_order_crosswalk

Return the nine-gate Build Order reference architecture: each gate mapped to the OWASP Agentic Top 10 (2026) risk it closes, the determinism rung it lives on, and the mature tool that enforces it, plus the coverage gaps.

Inferred read-only

get_voice_contract

Return the full published StoneyTECH writing voice contract: the machine-enforced banned and warn-tier word and phrase lists, the judgment rubric (rule ids V1 to V9 and E1 to E8 plus the eleven prose rules), and worked before-and-after examples drawn from real edits to this corpus.

Inferred read-only

voice_lint

Check a draft against the published StoneyTECH writing voice contract and return violations with line and column, plus prose metrics.

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.stoneytech-public-content-mcp]
url = "https://stoneytech.net/public-content/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "stoneytech-public-content-mcp": {
      "type": "http",
      "url": "https://stoneytech.net/public-content/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: stoneytech-public-content-mcp
Remote MCP URL: https://stoneytech.net/public-content/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": {
    "stoneytech-public-content-mcp": {
      "url": "https://stoneytech.net/public-content/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "stoneytech-public-content-mcp": {
      "type": "http",
      "url": "https://stoneytech.net/public-content/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "stoneytech-public-content-mcp",
  "transport": "streamable-http",
  "url": "https://stoneytech.net/public-content/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.