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

biowerk

https://bio.halowerk.com

Registry code: 32779433238010f3

api record

Paid tools via x402. tools/list is free. Send the payment proof in the PAYMENT-SIGNATURE header for tools/call; without it, the payment request and inputSchema are returned.

endpoint
https://bio.halowerk.com/
door code
dcfc966db9c94fae
protocol
JSONRPC ·0.3
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 biowerk live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is biowerk free to use?
No — it charges per call, quoted in its own 402 answers.
What tools does biowerk have?
10 tools: Encodes UTF-8 bytes into a deterministic A/C/G/T representation., Estimates idealized porous-scaffold permeability and superficial flow., Validates and scores a supplied two-dimensional HP lattice conformation., Calculates standard alpha-diversity indices from supplied taxon counts., Calculates a transparent homogeneous-mixing R0 and susceptible-adjusted Re., Builds a transparent weighted standardized index from caller-defined biomarker references., Calculates a stoichiometric product ceiling and process-adjusted yield from supplied substrates., Compares a protein sequence with supplied epitopes using transparent sequence similarity metrics., ….
Is biowerk 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.6%

90 days 98.8%· all time 98.7%

latency
99ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 1141 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • score crispr off-target sites
  • compute microbiome diversity
  • estimate pathogen r0
  • encode data as dna
  • check allergen epitope similarity
takes → gives
data → data
tools
10 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 121 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
46

distinct

settlements
9,342

last 2026-11-10

received on chain
37.4096 USDC

shared-payto

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 10 tools
10 never probed 0 of 10 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.

  • biowerk_dna_storage_encode reads unknown never probed

    Maps each two-bit group of caller-supplied UTF-8 bytes to A, C, G or T and reports a SHA-256 checksum of the original bytes. This reversible representation performs no biological synthesis, homopolymer balancing, GC optimization, addressing or error-correcting code.

    biowerk

  • biowerk_tissue_scaffold reads unknown never probed

    Uses the Kozeny-Carman relation with supplied porosity and pore diameter, then applies Darcy’s law with supplied thickness, viscosity and pressure drop. It is an idealized homogeneous porous-medium calculation, not scaffold design validation, cell-transport modeling, biocompatibility assessment or medical guidance.

    biowerk

  • biowerk_protein_folding reads unknown never probed

    Checks that a hydrophobic/polar sequence follows a self-avoiding unit-step lattice path, then counts non-consecutive hydrophobic contacts and assigns one negative energy unit per contact. It evaluates a supplied toy conformation only; it neither predicts a fold nor represents atomic chemistry, kinetics, solvent or biological function.

    biowerk

  • biowerk_microbiome_diversity reads unknown never probed

    Normalizes non-negative caller-supplied taxon counts and computes observed richness, natural-log Shannon entropy, Simpson diversity and Pielou evenness. It does not perform sequence classification, compositional correction, rarefaction, cohort comparison or medical interpretation.

    biowerk

  • biowerk_pathogen_r0 reads unknown never probed

    Multiplies per-contact transmission probability, effective contacts per day and infectious duration to obtain a simple basic reproduction number, then applies a susceptible fraction for an effective number. It is a classroom homogeneous-mixing calculation, not an outbreak estimate, fitted epidemiological model or public-health forecast.

    biowerk

  • biowerk_biomarker_longevity reads unknown never probed

    Standardizes each supplied value against its supplied mean and standard deviation, flips markers whose favorable direction is lower, and computes a weighted composite mapped to a bounded 0–100 index. The references and weights come entirely from the caller; this is not a validated longevity score, diagnosis, prognosis or medical advice.

    biowerk

  • biowerk_syn_yeast_yield reads unknown never probed

    Divides each available substrate mass by its required mass per product mass, selects the limiting substrate, and applies a caller-supplied process efficiency. It does not model yeast metabolism, kinetics, oxygen transfer, toxicity, regulation or actual fermentation performance.

    biowerk

  • biowerk_allergen_epitope reads unknown never probed

    Builds amino-acid k-mer sets, calculates Jaccard similarity, and finds the highest contiguous identity between each supplied epitope and any equal-length window of the query. It does not predict immune binding, allergenicity, cross-reactivity or clinical risk and cannot replace curated databases or laboratory testing.

    biowerk

  • biowerk_phage_matching reads unknown never probed

    Slides each caller-supplied spacer over a bounded phage sequence in both orientations, records its minimum Hamming distance and reports matches within a caller-selected mismatch threshold. It does not account for PAMs, phage taxonomy, infection biology, escape, host range or therapeutic suitability.

    biowerk

  • biowerk_crispr_offtarget reads unknown never probed

    Compares one guide with caller-supplied candidate protospacers, weights mismatches in the guide’s final ten positions twice, applies a simple NGG PAM penalty, and ranks a transparent similarity score. It does not search a genome, model bulges, chromatin or nuclease-specific biology, and must not be used as a clinical or laboratory safety decision.

    biowerk

_ 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 32779433238010f3.

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

_ also on halowerk.com 109 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.

101 more sit on this domain. All of them.