Is SITEBORNE Utility Network MCP server safe?

Findings (2)

• lowUnusually long tool description (over 2,000 characters)poison.long-description

  tool 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.…

• lowNo source repository listedmaint.no-repo