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

cn.mackorn/mackorn-cone-crusher

https://mackorn.cn

Registry code: 253dc106d632d65c

api record

MACKORN(美矿)液压圆锥破碎机与破碎筛分生产线选型工具。29 个工具。所有结果带 assumptions 与 warnings;未知字段返回 null,不估算;多来源冲突并列保留,绝不取平均。不含报价。

endpoint
https://mackorn.cn/ai/agent/
door code
479e6b3ccf24cb91
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 cn.mackorn/mackorn-cone-crusher live?
Yes — it answered the hub's last check (checked 8h ago). It answered 99% of checks over the last 30 days.
Is cn.mackorn/mackorn-cone-crusher free to use?
Yes — the hub reached it with no key and no payment.
What tools does cn.mackorn/mackorn-cone-crusher have?
10 tools: Hydraulic cone crusher selection, Calibrate on measured data, Market intelligence, Contact & partner programme, Product size simulation, Multi-stage flowsheet simulation, Investment & operating cost, Crushing & screening plant design, ….
Is cn.mackorn/mackorn-cone-crusher 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
98.6%

90 days 74.9%· all time 46.9%

latency
237ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 334 checks · signed record
  • down → live
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • retired → live
_ 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 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.

  • cone-crusher-selection unknown never probed

    Model, cavity, CSS, unit count and power from ore type, feed size and target capacity.

    miningcrusherselectioncone crusher

  • parameter-calibration unknown never probed

    Invert breakage parameters from measured feed and product sieve analyses.

    calibrationsieve analysisleast squares

  • market-intelligence unknown never probed

    Five-dimension market analysis with real customs data (HS 847420 / 847490).

    marketcustoms dataUN Comtrade

  • contact-and-partner unknown never probed

    Contact details and distributor/agent recruitment in 12 languages.

    contactdistributorpartner

  • product-size-simulation unknown never probed

    Whiten (1972) steady-state model for P20/P50/P80 and reduction ratio; Bond (1952) for specific energy.

    simulationWhitenBondPSD

  • flowsheet-simulation unknown never probed

    Population-balance closed-circuit iteration: per-stage P80, circulating load, mass balance.

    simulationcirculating loadclosed circuit

  • cost-estimate unknown never probed

    Installed power, annual energy, liner cost per tonne, installation at 2000 CNY/t, lease payment.

    costopexcapex

  • plant-design unknown never probed

    Stage count, per-stage size split, screen area, belt width, auxiliaries and a 14-section proposal.

    plant designflowsheetaggregate

  • liner-wear-design unknown never probed

    Wear uniformity across chamber sections; multi-gradient hardness design.

    wear partsmantlebowl linerliner life

  • distributor-evaluation unknown never probed

    Three-dimension 17-item scoring with veto items and verification coverage gate.

    channeldistributordue diligence

_ 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 253dc106d632d65c.

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