Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.dth0108/bies-guardian

REMOTE · BIES.IO · SCANNED AUG 3

Deterministic sealed verdicts on public claims and startup ideas (0-LLM claim-safety guardian).

Available components

+3 this week 65 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 582 tokens (~194/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · bies.io

# add to Claude Code
claude mcp add --transport http dth0108-bies-guardian https://bies.io/mcp
# ~/.codex/config.toml
[mcp_servers.dth0108-bies-guardian]
url = "https://bies.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dth0108-bies-guardian": {
      "type": "remote",
      "url": "https://bies.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dth0108-bies-guardian --url https://bies.io/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dth0108-bies-guardian:
    url: "https://bies.io/mcp"
// mcp.json
{
  "mcpServers": {
    "dth0108-bies-guardian": {
      "type": "http",
      "url": "https://bies.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://bies.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bies.io CN=WE1,O=Google Trust Services,C=US 19 Jun 2026 17 Sept 2026 ECDSA 256 ECDSA-SHA256 a6508cbf056c57f71364f6af3d7c53e3
SANs: bies.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of bies.io. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
bies.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bies.io/mcp Verified 200
http (plaintext) http://bies.io/mcp HTTPS enforced 301 https://bies.io/mcp
MCP tools — 3 exposed · ~523 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
claim_safety_verdict ~148

Deterministic, sealed pre-publication verdict on a PUBLIC claim (marketing copy, product page, ad headline). Returns per-claim verdict (PASS / CONDITIONAL_PASS / STOP), severity, and a reproducible replay_hash. A 0-LLM rules engine grounded in KR 표시광고법 / US FTC claim categories — NOT legal advice, NOT market proof or launch approval. Call this before a public claim ships.

NameTypeReqDescription
copystringyesThe exact public claim text you intend to publish.
langstringLanguage of the claim. Default ko.
marketstringRegulatory jurisdiction. Default follows lang (ko→KR, en→US).

No output schema declared.

No examples provided.

idea_rehearsal ~168

Deterministic decision-rehearsal verdict on a founder's BUSINESS IDEA (not a public claim). Returns a graded verdict (Conditional GO / Clear one critical gate / Confirm the headwind / Verify the basics / Redesign the structure / Firm up the inputs / Hold·Redesign) driven by the venture's structural signals, with a reproducible seal. Classification is retrieval-grounded; the verdict and seal are reproducible. NOT market proof, NOT investment advice. Use to pressure-test an idea before committing.

NameTypeReqDescription
ideastringyesThe business idea in the founder's own words — what you sell, to whom.
langstringLanguage. Default ko.
marketstringMarket. Default follows lang (ko→KR, en→US).

No output schema declared.

No examples provided.

rejudge_claims ~207

Re-judge a prior claim-safety verdict against new EVIDENCE. Pass the 'artifact' returned by claim_safety_verdict plus 'observations' (what happened). The top-level verdict NEVER changes on evidence (conservative by design); what moves is 4 axes — now-sayable lines (behind your owner-gate), permanently issuer-only claims, claims still short on evidence, and new risks. Deterministic, sealed, stateless (nothing stored).

NameTypeReqDescription
artifactobjectyesThe full artifact object returned by claim_safety_verdict (the prior verdict being re-judged).
langstringLanguage. Default ko.
observationsarrayyesEvidence events. Each: { outcome: 'paid_yes'|'written_pilot'|'observed_metric'|'rejection', targets: [{ ref_kind: 'claim_id'|'evidence_id', ref: '<id from the artifact>' }], rejection_reason_ref? }.

No output schema declared.

No examples provided.