mcpbeat Sign in

SITEBORNE Utility Network MCP Server

by siteborne Your server? Claim it
answering

SITEBORNE Utility Network is answering right now. Last checked 14 min ago. It exposes 6 tools.

Machine-native utility network: verified evidence services for autonomous agents.

Uptime history 35 days of history · worst day 0%
35 days agonow
93.4%
Uptime 24h
85 of 91 checks
6
Tools
read from the server
724 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 27

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 September 2026. No other catalogue keeps this.

21 Sep 3 tools appeared siteborne_build_company_evidence_graph, siteborne_extract_document_evidence_json, siteborne_retrieve_verified_web_context
21 Sep 3 tools disappeared siteborne_company_evidence_graph, siteborne_document_evidence_json, siteborne_web_context_verified
21 Sep 2 tool descriptions were rewritten siteborne_get_quote, siteborne_verify_agent_output
20 Sep 6 tool descriptions were rewritten siteborne_company_evidence_graph, siteborne_document_evidence_json, siteborne_get_quote and 3 more
20 Sep 2 tools changed the parameters they ask for siteborne_verify_agent_output, siteborne_web_context_verified
12 Sep 6 tool descriptions were rewritten siteborne_company_evidence_graph, siteborne_document_evidence_json, siteborne_get_quote and 3 more
12 Sep 5 tools changed the parameters they ask for siteborne_company_evidence_graph, siteborne_document_evidence_json, siteborne_get_quote and 2 more

SITEBORNE Utility Network does not always answer

Over the last week it answered 98.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add utility --transport http https://utility.siteborne.net/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "utility": {
      "url": "https://utility.siteborne.net/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.utility]
url = "https://utility.siteborne.net/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "utility": {
      "url": "https://utility.siteborne.net/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "utility": {
      "url": "https://utility.siteborne.net/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

siteborne
siteborne_build_company_evidence_graph
Build a proof-carrying graph of public company identity, SEC filings, website observations, regulatory mentions, and repository signals. Use when: the request needs entity-level evidence synthesized across sources. Do not use when: one URL is the subject (use siteborne_retrieve_verified_web_context), one document is the subject (use siteborne_extract_document_evidence_json), or an existing agent output needs evaluation (use siteborne_verify_agent_output). Parameters: authoritative identifiers (cik, lei, isin, cusip, figi) resolve entities more reliably than company_name, ticker or domain alone, and combining them reduces ambiguity; requested_field_groups narrows provider work; maximum_authorized_price only constrains payment and never widens scope. Behavior: open-world: a paid request queries public data providers over the network and persists governed payment, audit, job and Workflow state; an unpaid request returns payment_required; a repeated identical request with the same payment is replay-protected and is not charged twice. This service is currently production-disabled and rejects execution. Economics: exact price of $0.0312 USD per request; the payment challenge requires that amount and the charge settles at exactly that amount. Failure: input that fails schema validation is rejected before any payment challenge; provider or service unavailability returns a structured MCP error. Returns: a company evidence graph with provenance, completeness, verification, and PCC context—not a raw webpage or document extraction.
siteborne_extract_document_evidence_json
Extract and verify structured evidence from exactly one authorized artifact, prior SITEBORNE upload, or public document URL. Use when: the source of truth is a PDF or supported image and the desired result is evidence JSON. Do not use when: a webpage alone is sufficient (use siteborne_retrieve_verified_web_context), company-wide public evidence is needed (use siteborne_build_company_evidence_graph), or an existing agent response needs evaluation (use siteborne_verify_agent_output). Parameters: provide exactly one reference mode: artifact_reference (an authorized stored artifact), upload_reference (a prior SITEBORNE upload handle, not document bytes) or document_url (a public URL, no credentials). ocr_permission must be true before image-based content is read by OCR, and OCR pages bill at the OCR tier; extraction_request.extract_tables and table_extraction_request request table extraction, and pages with tables bill at the table tier; declared_page_count and page_range are bounded by the page limit below; maximum_authorized_price only constrains payment. Behavior: open-world: a paid request may read governed artifact storage or fetch a public document URL, calls the document provider, and persists payment, audit, job and Workflow state; an unpaid request returns payment_required; a repeated identical request with the same payment is replay-protected and is not charged twice. This service is currently production-disabled and rejects execution. Economics: upto pricing: the payment challenge authorizes a maximum of $0.19 USD per job; the actual charge is measured per processed page (native-text $0.0098, OCR $0.0156, table $0.0238 per page, the highest applicable tier per page) and never exceeds the authorization. The authorization is a ceiling, not the charge. Documents are limited to 10 pages per job. Failure: schema-invalid input is rejected before any payment challenge; a document over the page limit, an unreadable or encrypted document, or an unavailable provider returns a structured MCP error. Returns: extracted document evidence, integrity/provenance findings, and PCC verification—not an uploaded file.
siteborne_get_quote
Build a canonical x402 payment quote for one SITEBORNE service and exact request input. Use when: an agent needs the governed price, payee, network, asset, resource, expiry, and payment requirement before deciding whether to invoke a paid service. Do not use when: evidence work is required now (use the matching siteborne_build_company_evidence_graph, siteborne_retrieve_verified_web_context, siteborne_extract_document_evidence_json, or siteborne_verify_agent_output tool), or only availability is needed (use siteborne_get_service_health). Parameters: scheme must be the one scheme the service is offered under (company_evidence_graph.v2 exact, web_context_verified.v2 exact, document_evidence_json.v2 upto, verify_agent_output.v2 exact); any other scheme is rejected with scheme_not_offered. input is hashed, so the quote binds only that exact request. Behavior: quote-only and read-only; it hashes the proposed input, and does not execute the underlying paid service, verify payment, call a provider, create a Workflow, or settle. Economics: free of charge. The returned amount is the exact price, or for upto an authorized maximum whose actual_amount is null because the real charge is measured at settlement and never exceeds it. Failure: a mode that has a governed price but is unavailable returns retrieval_mode_unavailable or verification_mode_unavailable and no quote; a quote expires at expires_at. Returns: an expiring input-bound quote with its x402 payment requirement and the canonical economics block.
siteborne_get_service_health
Report MCP server readiness and production-enable status for each SITEBORNE service. Use when: an agent must check protocol availability, tool count, or whether a service is currently production-enabled before selecting a paid tool. Do not use when: a quote is needed (use siteborne_get_quote) or company, web, document, or agent-output evidence work is required (use the corresponding SITEBORNE service tool). Behavior: read-only and credential-independent; it does not perform paid evidence work, create quotes, verify payment, call providers, write service state, create Workflows, or settle. Economics: free of charge; it never issues a payment challenge. Failure: it depends on no provider, so it does not fail because a provider is unavailable. Returns: the server and protocol versions plus truthful local, production, and external-publication status for all four evidence services.
siteborne_retrieve_verified_web_context
Retrieve and verify evidence from one public web URL using direct HTTP retrieval. Use when: the request is specifically about the content and provenance of a URL. Do not use when: evidence must be synthesized for a company (use siteborne_build_company_evidence_graph), extracted from an authorized document (use siteborne_extract_document_evidence_json), checked against an existing output contract (use siteborne_verify_agent_output), or the page requires JavaScript rendering (rendered retrieval is not available). Parameters: retrieval_mode must be direct; rendered is defined but unavailable and is rejected before any payment challenge, never substituted with direct retrieval. output_mode structured needs buyer_schema and field_selectors to be meaningful; redirect_policy and max_redirects bound redirect following; max_content_size bounds returned bytes; maximum_authorized_price only constrains payment and never changes retrieval scope. Behavior: open-world: a paid request performs bounded outbound HTTP retrieval of the target URL through a safe-egress boundary (private and loopback destinations are refused) and persists governed payment, audit, job and Workflow state; an unpaid request returns payment_required; a repeated identical request with the same payment is replay-protected and is not charged twice. Retrieval admission follows the governed runtime rate policy; no fixed public per-origin rate is promised. This service is currently production-enabled. Economics: exact price of $0.008 USD per request in direct mode; the payment challenge requires that amount and the charge settles at exactly that amount. rendered mode has a governed price of $0.029 USD but is not available: it is rejected before any payment challenge and never substituted. Failure: schema-invalid input and unavailable modes are rejected before any payment challenge; target-site errors, timeouts and unavailable retrieval return a structured MCP error and are never answered with a substitute result. Returns: normalized, source-attributed web context with verification and PCC evidence.
siteborne_verify_agent_output
Evaluate a supplied agent output against explicit claims, deterministic requirements, a required JSON Schema, and optional evidence. Use when: the caller already has an output and needs a governed verification verdict. Do not use when: evidence must first be gathered from a company (use siteborne_build_company_evidence_graph), URL (use siteborne_retrieve_verified_web_context), or document (use siteborne_extract_document_evidence_json), or independent reproduction of the output is required (not available). Parameters: verification_mode must be standard; independent_reproduction is defined but unavailable and is rejected before any payment challenge, never downgraded to standard. required_schema must fit SITEBORNE JSON Schema Profile 1 or the request is rejected before payment; minimum_score sets the acceptance threshold; maximum_authorized_price only constrains payment and never relaxes verification policy. Behavior: closed-world: standard mode evaluates only the supplied claims, requirements, output and evidence with no outbound retrieval, and persists governed payment, audit, job and Workflow state; an unpaid request returns payment_required; a repeated identical request with the same payment is replay-protected and is not charged twice. The verification policy and verdict rules do not depend on price or maximum_authorized_price. This service is currently production-enabled. Economics: exact price of $0.017 USD per request in standard mode; the payment challenge requires that amount and the charge settles at exactly that amount. independent_reproduction mode has a governed price of $0.049 USD but is not available: it is rejected before any payment challenge and never substituted. Failure: an unsupported or oversized required_schema, schema-invalid input and unavailable modes are rejected before any payment challenge; a failed verification is a normal fail or conditional verdict, not an error. Returns: claim-level and deterministic-check results, an overall verification verdict, and PCC evidence—not newly gathered source content.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

siteborne_company_evidence_graph
removed 21 Sep 2026
siteborne_document_evidence_json
removed 21 Sep 2026
siteborne_web_context_verified
removed 21 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://utility.siteborne.net/mcp streamable-http answering 1184 ms 14 min ago

Alternatives to SITEBORNE Utility Network

same job, measured the same way
MERCATOR Verify
by arzuo

MERCATOR Verify: evidence-backed verification and decision support for autonomous agents.

2 tools answering
ARAKEL Machine Evidence Network
by arakelproof-proof

High-frequency OFAC wallet screening and recurring signed x402 checks for autonomous agents.

13 tools answering
Hive Identity
by srotzin

W3C DID issuance and verification for autonomous AI agents

4 tools answering
Speedbot Autonomous Work Network
by ulasarslan6262-ui

Fixed services, direct hiring and collaboration for autonomous AI agents and swarms.

76 tools answering
01Mind
by 01mind

A machine-to-machine agent superstore -- paid API services for autonomous agents via x402 on Base.

3 tools answering
01Mind
by 01mind

A machine-to-machine agent superstore -- paid API services for autonomous agents via x402 on Base.

3 tools answering
Atinamos Evidence
by co-atinamos

Read-only verification evidence for paid machine services and buyer policy checks.

6 tools answering
Verantis MCP
by m9labs-railscope

Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.

138 installs/wk 4 tools answering

SITEBORNE Utility Network — questions

Answers built from our own checks of this server.

What can SITEBORNE Utility Network do?
It exposes 6 tools, read directly from the server on our last check. Among them: siteborne_build_company_evidence_graph, siteborne_extract_document_evidence_json, siteborne_get_quote, siteborne_get_service_health, siteborne_retrieve_verified_web_context, siteborne_verify_agent_output. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is SITEBORNE Utility Network working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 85 of 91 checks got a reply (93.4%), average response time 724 ms. The bar chart above shows every period we have measured.
Did SITEBORNE Utility Network ever remove tools?
Yes. siteborne_company_evidence_graph, siteborne_document_evidence_json, siteborne_web_context_verified are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect SITEBORNE Utility Network?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does SITEBORNE Utility Network need an API key?
No. SITEBORNE Utility Network completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SITEBORNE Utility Network?
It answers our handshake in 724 ms on average, which is faster than 17% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.