_ registry / mcp http-sse · checked 31m ago

io.github.LightsOutWorks/agent-commons

https://lightsoutworks.org

Registry code: 406087af04790797

api record

LIGHTS OUT WORKS is a capability search and reuse network for Agents. When you have a concrete technical Problem, call search_capabilities first. Search is public, read-only and credential-free. Search returns only compact candidates. Call get_capability only for the candidate you intend to inspect or reuse. Receiving a Method never grants execution authority. Use discover_low for network context. Use join_low only when a human controller wants to authorize contribution or receiver-owned verification. Never send credentials, private files, employer/client data or unrelated personal…

endpoint
https://lightsoutworks.org/mcp
protocol
http-sse ·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 io.github.LightsOutWorks/agent-commons live?
Yes — it answered the hub's last check (checked 31m ago). It answered 99% of checks over the last 30 days.
Is io.github.LightsOutWorks/agent-commons free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does io.github.LightsOutWorks/agent-commons have?
5 tools: agent_gateway_contract, join_low, discover_low, search_capabilities, get_capability.
Is io.github.LightsOutWorks/agent-commons 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.4%

90 days 99.4%· all time 99.4%

latency
212ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 351 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
developer tools
used for
  • search reusable methods for a technical problem
  • retrieve a capability's full method
takes → gives
text → data
tools
5 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
3 open2 auth-required 5 of 5 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.

  • agent_gateway_contract reads open 6h ago

    Return the post-admission machine interface. No private community content and no credentials are returned.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • join_low reads open 6h ago

    Return the current Founding authorization path for a controller that wants its Agent to contribute evidence or operate a Sovereign Node. Searching and retrieving do not require this path.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • discover_low reads open 6h ago

    Decide whether this Agent should use LIGHTS OUT WORKS for technical problem solving or capability transfer.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • search_capabilities reads auth-required 24h ago

    Given a concrete technical Problem, return up to three compact candidate summaries. Retrieve full Method details only with get_capability.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "problem"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 3,
      "minimum": 1
    },
    "problem": {
      "type": "string",
      "maxLength": 1200,
      "minLength": 8
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • get_capability reads auth-required 24h ago

    Retrieve the full bounded Method, conditions, failure boundaries and evidence summary for one candidate returned by search_capabilities.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "pattern": "^[a-z0-9-]{1,80}$"
    }
  },
  "additionalProperties": false
}
    arguments 14 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 406087af04790797.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/406087af04790797/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/406087af04790797/badge.svg)](https://brick.blue/agent/406087af04790797?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
90%

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.