_ registry / mcp + a2a streamable-http · checked 48m ago

How Good It Can Get™ Clarity MCP

https://ai.howgooditcanget.com

Registry code: 2889b42acd0b2a53

api record

MCP tool for governed nonclinical pattern interruption, emotional clarity, and next-step guidance.

from a public catalogue that lists it, not from the operator

endpoint
https://ai.howgooditcanget.com/mcp
door code
2e5e3545445ccf01
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is How Good It Can Get™ Clarity MCP live?
Yes — it answered the hub's last check (checked 48m ago). It answered 100% of checks over the last 30 days.
Is How Good It Can Get™ Clarity MCP free to use?
Yes — the hub reached it with no key and no payment.
What tools does How Good It Can Get™ Clarity MCP have?
1 tool: clarity_os.
Is How Good It Can Get™ Clarity MCP safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.4%· all time 99.5%

latency
331ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1466 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • help a person sort out a difficult emotional moment
  • suggest a next step
takes → gives
text → text
tools
1 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 1 tools
1 never probed 0 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • clarity_os reads unknown 11h ago

    Use Clarity OS when a person needs help making sense of a difficult moment—such as overthinking, emotional activation, uncertainty, decision friction, conflicting priorities, a repeating pattern, or a difficult conversation. It provides governed, nonclinical clarity support to help identify what is happening, clarify what matters, and choose a grounded next step while preserving uncertainty and personal agency. It may return protective safety routing when appropriate. Do not use for diagnosis, treatment, crisis intervention, or emergency support. Provide the person’s situation in `user_text`.

    mcp-tool

    {
      "type": "object",
      "examples": [
        {
          "user_text": "I keep replaying a difficult conversation and cannot tell whether I am solving anything or just looping.",
          "explicit_request": "Help me understand the pattern and identify a grounded next step."
        }
      ],
      "required": [
        "user_text"
      ],
      "properties": {
        "emotions": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional emotional-state labels supported by the person’s language, such as anxiety, worry, frustration, or uncertainty. These are provisional matching hints; omit them rather than guess."
        },
        "user_text": {
          "type": "string",
          "description": "Required. The person’s current message or situation, preserved as provided. Include enough context to understand the moment; do not add facts the person did not provide."
        },
        "topic_tags": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional concise topics supported by the situation. These improve governed knowledge and resource matching; omit them rather than guess."
        },
        "pattern_refs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional supported pattern labels, such as overthinking loop or anxiety pattern. These improve matching and are not required."
        },
        "safety_evidence": {
          "type": "object",
          "description": "Optional. Structured safety facts directly provided by the person or established by the caller. Omit unsupported fields; never manufacture safety evidence."
        },
        "capacity_signals": {
          "type": "object",
          "description": "Optional. Structured, directly supported signals about current attention, readiness, or ability to engage. Omit rather than infer."
        },
        "explicit_request": {
          "type": "string",
          "description": "Optional. The specific help or clarification the person explicitly requested. Omit when no explicit request was stated; do not infer one."
        },
        "requested_resource": {
          "type": "string",
          "description": "Optional. A governed HGICG resource identifier only when a specific resource is requested. This does not grant access; resource access remains separately governed."
        }
      }
    }
    arguments 55 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2889b42acd0b2a53.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2889b42acd0b2a53/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2889b42acd0b2a53/badge.svg)](https://brick.blue/agent/2889b42acd0b2a53?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
50%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
321ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.