peptides-farm
Registry code: 899068cc1b1d51e4
Free: list_peptides, list_body_systems. Paid tools return an x402 payment requirement in _meta['x402/error']; pay and retry with _meta['x402/payment'], or connect with an X-API-KEY header (prepaid credits, POST https://peptides.farm/api/v1/accounts). Data is a public-record compilation, not medical advice.
- endpoint
- https://peptides.farm/
- door code
- 760a362ab81d6f5c
- protocol
- JSONRPC ·0.2
- authentication
- none, x402
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is peptides-farm live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is peptides-farm free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does peptides-farm have?
- 7 tools: get_point_in_time_regulatory_shocks, search_fda_patents_suppliers_reimbursement, unlock_full_dataset_with_tx, request_missing_dataset_or_entity, list_biomedical_datasets, query_dataset_preview, get_x402_payment_instructions.
- Is peptides-farm 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.
90 days 100%· all time 100%
last good check
of 7 tools
- unknown → live
- unknown → live
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.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes
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.
get_point_in_time_regulatory_shocks auth-required never probed
Returns the live 90-day Point-in-Time State-Transition Delta Radar (NADAC sole-source price spikes, FDA OAI facility downgrades, OASIS port detentions, unlabeled FAERS safety signals, and CMS J-Code spread shifts).
search_fda_patents_suppliers_reimbursement auth-required never probed
Searches across 90 programmatic dossiers covering FDA Orange Book NDA patent cliffs (/patents/), Type II DMF / FEI API manufacturers & OASIS port refusals (/suppliers/), and CMS Part B J-Code / Medicaid NADAC reimbursement spreads (/reimbursement/).
unlock_full_dataset_with_tx auth-required never probed
Verifies a confirmed Base Mainnet (0x...) or Solana Mainnet transaction signature on-chain via Mainnet RPC and returns the full unlocked dataset rows.
request_missing_dataset_or_entity auth-required never probed
Submits a structured request when an AI agent, researcher, or developer needs a specific molecule, NDA/DMF/J-Code entity, regulatory silo, or custom schema field not yet in the 12 datasets. Logs to https://peptides.farm/api/demand.
list_biomedical_datasets auth-required never probed
Lists all 12 entity-resolved FDA, CMS, NIH, Orange Book, DMF/FEI, NADAC, OASIS Port Refusal, and Peptide datasets on peptides.farm with row counts, schema columns, free preview URLs, and x402 USDC unlock pricing.
query_dataset_preview auth-required never probed
Queries the 10-row entity-resolved public preview and 5 derived quant layers (canonicalEntityId, normalizedCostPerMgUsd, spofRiskScore0to100, delta90dFlag, rowSha256) for any of the 12 datasets.
get_x402_payment_instructions auth-required never probed
Returns exact x402 USDC payment instructions for Base Mainnet (eip155:8453) and Solana Mainnet (SPL USDC / Phantom Cash) to unlock any full multi-hundred-row dataset.
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id899068cc1b1d51e4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/899068cc1b1d51e4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/899068cc1b1d51e4?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 0
- failed
- 1
- success rate
- 0%
- median latency
- 262ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
1 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.