Skip to content
SITEBORNE logo

SITEBORNE MCP server

Which MCP servers are SITEBORNE's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to SITEBORNE

Whose server it is
  • Registry namenet.siteborne/utilityverified in the MCP registry

The registry name sits under siteborne.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools10
  • Server calls itselfnet.siteborne/utility
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 1134 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Check runtime status metadata before wiring up a integration", the likely first call is siteborne_get_service_health.
  • Its definitions take about 17684 tokens of context: enable only the tools a task needs.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer574 ms
  • Space in an agent's context≈ 17,684 tokensthe definitions of all its tools (10), which an agent carries on every turn
  • Tool definitionsA · 98 of 100
  • Typed results10 of 10 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a type: in 1 of 10

What an agent can do with it

  • not sure · Look up contract and schema definitions for integrations
  • not sure · Discover machine manifests and agent cards for automated systems
  • can do · Check runtime status metadata before wiring up a integration

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-10-26
  • 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…

  • 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_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…

  • 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…

  • siteborne_build_company_evidence_graph_v3_candidate

    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…

  • siteborne_retrieve_verified_web_context_v3_candidate

    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_extract_document_evidence_json_v3_candidate

    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…

  • siteborne_verify_agent_output_v3_candidate

    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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "utility": {
      "type": "http",
      "url": "https://utility.siteborne.net/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http siteborne https://utility.siteborne.net/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://utility.siteborne.net/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.