mcp server
bies-guardian
Deterministic sealed verdicts on public claims and startup ideas (0-LLM claim-safety guardian).
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-07-04.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
claim_safety_verdict(copy, lang, market)- 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. Required: copy.
idea_rehearsal(idea, lang, market)- 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. Required: idea.
rejudge_claims(lang, artifact, observations)- 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). Required: artifact, observations.
Last successful function declaration observed on . Source: https://bies.io/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://bies.io/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-04 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-04 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | bies.io | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | bies.io |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json