_ registry / mcp + a2a JSONRPC · checked 15h ago

hellotime-public

https://mcp.hellotime.ai

Registry code: 24a9ef5f53d6c6ba

api record

Public read-only HelloTime knowledge base. Use these tools to answer questions about HelloTime plans, pricing, features (shifts, rosters, leave, timesheets, geofence, biometric kiosk), supported countries, and payroll capabilities. No customer or timesheet data is available through this server.

endpoint
https://mcp.hellotime.ai/mcp
door code
bc06527a1042ce13
protocol
JSONRPC ·1.0
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 hellotime-public live?
Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
Is hellotime-public free to use?
Yes — the hub reached it with no key and no payment.
What tools does hellotime-public have?
8 tools: List HelloTime pricing plans, Free-text search, Full feature catalog, Payroll capabilities, Statutory payroll rates, Local payment methods, Country support matrix, Competitor positioning.
Is hellotime-public 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 99.2%· all time 97.5%

latency
137ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 533 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get workforce time tracking plans and pricing
  • list shift and leave features
  • get payroll capabilities by country
  • look up statutory payroll rates
takes → gives
text → data
tools
8 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 8 tools
8 never probed 0 of 8 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.

  • list_plans reads unknown never probed

    HelloTime plan tiers (Free, Attend, Track, Business) with the charged price and a standing list-price anchor per region, plus volume and annual-prepay discounts. Free is permanent for a single user; paid tiers each include a 7-day free trial.

    pricinghellotimetime-tracking

  • feature_search reads unknown never probed

    Free-text search across plan features, product features, country features, payroll engines, statutory rates, competitor positioning, and local payment methods. Queries like "PF rate", "PT slab Maharashtra", "vs Truein", or "BACS payroll" surface the matching entry.

    searchhellotimetime-tracking

  • list_features reads unknown never probed

    HelloTime features across shifts, rosters, leave types, timesheets, time tracking, productivity, GPS / geofence, biometric kiosk, payroll, invoicing, analytics, projects, reports, and integrations.

    featureshellotimetime-tracking

  • payroll_capabilities reads unknown never probed

    Supported payroll engines per country (AU STP2 + super, IN PF/ESI/TDS/Form 24Q, US W-2/1099, UK PAYE) with live / beta / coming-soon status.

    compliancehellotimetime-tracking

  • statutory_rates reads unknown never probed

    Statutory payroll-rate entries with rate, ceiling, slab, authority, and verification status. India block (PF / EPS / EDLI / ESI / Professional Tax by state / TDS slabs) is internally reviewed against EPFO / ESIC / state notifications; AU and US entries are public-source-unreviewed.

    compliancehellotimetime-tracking

  • local_payment_methods reads unknown never probed

    Local bank-rail and wallet methods relevant to HelloTime payroll and contractor payouts (UPI, IMPS, NEFT, RTGS, BACS, FPS, PayID, PayTo, ACH, RTP, WPS-SIF, PayNow, FAST, GIRO, NZ Direct Credit) with rail speed, use-cases, issuing authority, and support level.

    integrationshellotimetime-tracking

  • country_support reads unknown never probed

    Per-country features, default currency, and product positioning for a supported country (IN, AU, GB, US, CA, AE, SG, NZ).

    compliancehellotimetime-tracking

  • list_competitors reads unknown never probed

    Competitor entries (Truein, Deputy, When I Work, Connecteam, Hubstaff, Keka) with where HelloTime wins, where the competitor wins, and pricing notes.

    contenthellotimetime-tracking

_ try it over a2a 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 24a9ef5f53d6c6ba.

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

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.