_ registry / mcp streamable-http · checked 1h ago

ask-the-clock

https://ctrlworx.com

Registry code: 98fddf1447a287a2

api record

Ask the Clock reads the live Ctrl Worx Watch List: public companies whose own SEC filings report a material weakness in internal control over financial reporting with no later annual report saying it is fixed, and how long each has been open (the Clock). Every answer carries its as-of date and an SEC EDGAR link; pass both on to the user. Use lookup_company for one company and clock_headline for the totals. If lookup_company returns candidates or nothing, say so and ask; never infer a company's status. Credit "Ctrl Worx Watch List" with a link to https://ctrlworx.com/watch-list/. Ctrl Worx is…

endpoint
https://ctrlworx.com/wp-json/ctrlworx/v1/ask-the-clock
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 ask-the-clock live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ask-the-clock free to use?
Yes — the hub reached it with no key and no payment.
What tools does ask-the-clock have?
2 tools: lookup_company, clock_headline.
Is ask-the-clock 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
100%

90 days 100%· all time 100%

latency
893ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 open 1 never probed 1 of 2 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.

  • clock_headline open 1h ago

    Returns the live headline Clock figures from the Ctrl Worx Watch List with their as-of date: public companies on the Clock, how many have been open more than one and three years, and the full on-record count. Also returns the frozen October 2026 report figures with their own as-of date. Always quote a figure with its as-of date.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • lookup_company unknown 1h ago

    Looks up one public company by ticker, full company name or SEC CIK number in the live Ctrl Worx Watch List. Returns whether it is on the Watch List, its status, how long the material weakness has been open (years on the Clock and open-since date), the as-of date, its ctrlworx.com page and the SEC filing link. It matches on an exact ticker, CIK or full name. For anything else it returns candidates, and you should ask the user which company they mean. Never state a status the tool did not return.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 60,
      "minLength": 1,
      "description": "Ticker (e.g. CORZ), full company name (e.g. Core Scientific), or SEC CIK number."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
_ try it 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 98fddf1447a287a2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/98fddf1447a287a2/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/98fddf1447a287a2/badge.svg)](https://brick.blue/agent/98fddf1447a287a2?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 know
card completeness
60%

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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.