_ registry / mcp streamable-http · checked 29m ago

hjLabs DevCalc

https://calc.hjlabs.in

Registry code: 856d070474bd1d01

api record

Three deterministic developer calculators. No authentication, no rate limit beyond fair use, and no state: the same arguments always give the same answer, so results can be cached indefinitely.

endpoint
https://calc.hjlabs.in/mcp
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 hjLabs DevCalc live?
Yes — it answered the hub's last check (checked 29m ago). It answered 99% of checks over the last 30 days.
Is hjLabs DevCalc free to use?
Not measured yet.
What tools does hjLabs DevCalc have?
3 tools: colour_contrast, aspect_ratio, subnet_calculator.
Is hjLabs DevCalc 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.3%

90 days 99.6%· all time 99.6%

latency
400ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 488 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • unknown → live
_ what it is for
topic
developer tools
used for
  • reduce and scale an aspect ratio
  • check wcag colour contrast
  • calculate an ipv4 subnet
takes → gives
data → data
tools
3 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 3 tools
3 never probed 0 of 3 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.

  • colour_contrast reads unknown never probed

    Compute the WCAG 2.x contrast ratio between two hex colours and report pass or fail against AA and AAA thresholds for normal and large text.

    mcp-tool

    {
  "type": "object",
  "required": [
    "foreground",
    "background"
  ],
  "properties": {
    "background": {
      "type": "string",
      "description": "Background colour as #rgb or #rrggbb."
    },
    "foreground": {
      "type": "string",
      "description": "Foreground colour as #rgb or #rrggbb."
    }
  }
}
    arguments 17 lines
  • aspect_ratio reads unknown never probed

    Reduce a pixel width and height to its simplest aspect ratio, and optionally scale it to a target width or height while preserving that ratio.

    mcp-tool

    {
  "type": "object",
  "required": [
    "width",
    "height"
  ],
  "properties": {
    "width": {
      "type": "number",
      "description": "Width in pixels."
    },
    "height": {
      "type": "number",
      "description": "Height in pixels."
    },
    "targetWidth": {
      "type": "number",
      "description": "Optional: scale to this width and report the matching height."
    },
    "targetHeight": {
      "type": "number",
      "description": "Optional: scale to this height and report the matching width."
    }
  }
}
    arguments 25 lines
  • subnet_calculator reads unknown never probed

    Calculate the network address, broadcast address, netmask, wildcard, usable host range and address count for an IPv4 CIDR block. Handles /31 point-to-point links and /32 single hosts correctly.

    mcp-tool

    {
  "type": "object",
  "required": [
    "cidr"
  ],
  "properties": {
    "cidr": {
      "type": "string",
      "description": "An IPv4 block in CIDR form, e.g. \"10.0.0.0/8\" or \"192.168.1.0/24\"."
    }
  }
}
    arguments 12 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 856d070474bd1d01.

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

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.

_ also on hjlabs.in 7 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.