SITEBORNE Utility Network MCP server

• siteborne_build_company_evidence_graphFree

  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_jsonFree

  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_quoteFree

  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_healthFree

  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_contextFree

  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_outputFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1756ms20/20
• Tool poisoning6 tool descriptions checked13/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

SITEBORNE Utility Network: common questions

Is SITEBORNE Utility Network MCP server safe?

With care: it is graded C, so read the findings first (64/100). Read the SITEBORNE Utility Network safety report

How do I install SITEBORNE Utility Network?

It runs remotely at utility.siteborne.net. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does SITEBORNE Utility Network need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is SITEBORNE Utility Network maintained?

The latest release is v0.1.0.

Is SITEBORNE Utility Network up?

100% of our last 19 checks got an answer. We check remote servers about four times a day.