moacut
Registry code: 64ce3480bd54d68b
MOACUT calculates how rectangular parts fit on rectangular sheets (2D nesting / cut-list optimization) for wood, MDF, plywood, acrylic, sheet metal and similar. All sizes are millimetres. Kerf is the cut width between parts; edge margin is kept clear around each sheet. Without an account it calculates up to 10 part types and 30 pieces per job; larger jobs return a link to open the job on moacut.com, where MOACUT Pro calculates them. Parts in separate calls cannot share sheets, so a sheet count is correct only for the whole job sent in one call. Each result includes an openInMoacut link that…
- endpoint
- https://www.moacut.com/api/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 moacut live?
- Yes — it answered the hub's last check (checked 10h ago). It answered 100% of checks over the last 30 days.
- Is moacut free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does moacut have?
- 1 tool: calculate_nesting.
- Is moacut 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 1 tools
- 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: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
calculate_nesting unknown 10h ago
Lay out rectangular parts on rectangular sheets and return how many sheets are needed, the scrap percentage, the largest reusable offcut, each part's position on each sheet, and a link that opens the job in MOACUT. Sizes in millimetres. Free limit: 10 part types and 30 pieces in total. Sheet counts are correct only for the whole job in one call.
{ "type": "object", "required": [ "sheetWidth", "sheetHeight", "parts" ], "properties": { "kerf": { "type": "number", "maximum": 100000, "minimum": 0, "description": "Cut width between parts in mm (default 3)" }, "parts": { "type": "array", "items": { "type": "object", "required": [ "width", "height", "quantity" ], "properties": { "width": { "type": "number", "maximum": 100000, "description": "Part width in mm", "exclusiveMinimum": 0 }, "height": { "type": "number", "maximum": 100000, "description": "Part height in mm", "exclusiveMinimum": 0 }, "quantity": { "type": "integer", "minimum": 1, "description": "How many of this part" } } }, "maxItems": 100, "minItems": 1, "description": "Part types to cut" }, "language": { "enum": [ "en", "ko", "ja", "de", "es", "pt" ], "type": "string", "description": "Language of the MOACUT page the link opens (default en)" }, "edgeMargin": { "type": "number", "maximum": 100000, "minimum": 0, "description": "Clear margin around each sheet in mm (default 10)" }, "sheetWidth": { "type": "number", "maximum": 100000, "description": "Sheet width in mm, e.g. 2440", "exclusiveMinimum": 0 }, "sheetHeight": { "type": "number", "maximum": 100000, "description": "Sheet height in mm, e.g. 1220", "exclusiveMinimum": 0 }, "allowRotation": { "type": "boolean", "description": "Allow parts to turn 90 degrees. Set false when the grain direction matters (default true)" } } }arguments 83 lines
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 id64ce3480bd54d68b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/64ce3480bd54d68b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/64ce3480bd54d68b?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
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- 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
- —
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.