nomicheck
Registry code: f73467ae7572de81
Verifiable Colombian payroll: a deterministic engine over a dated legal catalog, with a free pre-check, a pay-per-call report (x402, USDC) and Ed25519-signed output verifiable offline.
from a public catalogue that lists it, not from the operator
- endpoint
- https://nomicheck.ynt.codes/api/mcp
- door code
- 17ac510c77c024df
- 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 nomicheck live?
- Yes — it answered the hub's last check (checked 22m ago). It answered 100% of checks over the last 30 days.
- Is nomicheck free to use?
- Not measured yet.
- What tools does nomicheck have?
- 5 tools: nomicheck_verificar_sobre, nomicheck_ejemplo, nomicheck_calcular, nomicheck_schema, nomicheck_info.
- Is nomicheck 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 99%· all time 99.3%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- calculate a payroll settlement
- get an example input and output
- get the input schema
- verify a signed calculation result
- takes → gives
- data → data
- tools
- 5 reads
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
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.
nomicheck_verificar_sobre reads unknown never probed
LOCALLY verifies a signed NomiCheck output (Ed25519 over the canonical JSON) with the vendored copy of the `sobre` verifier — the verification itself never touches the network. Verdicts: `verificable`, `firmado_sin_procedencia` (valid signature but no reglasHash: a signed opinion) or `invalido`. If no key is passed, it is fetched from /api/batch/publickey — same origin as the envelope, i.e. consistency, not identity.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "documento" ], "properties": { "documento": { "type": "object", "description": "The complete envelope exactly as the API returned it, with its `signature` field.", "additionalProperties": {} }, "llave_publica_pem": { "type": "string", "description": "Ed25519 public key in PEM, pinned by the caller. The strong case." } }, "additionalProperties": false }arguments 19 linesnomicheck_ejemplo reads unknown never probed
Free. Returns a listing's real input+output pair so you can copy the contract without reading documentation. The `output` comes SIGNED by production, so it also works as direct input for `nomicheck_verificar_sobre`.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "ruta" ], "properties": { "ruta": { "enum": [ "retencion", "verificar", "liquidacion-final" ], "type": "string", "description": "Route to fetch the example from." } }, "additionalProperties": false }arguments 19 linesnomicheck_calcular reads unknown never probed
POSTs the body to a listing. Without `x_payment` and with the paywall on, it returns the STRUCTURED 402: the full `accepts` array (network, token, amount, payTo, EIP-712 domain) plus the payTo cross-check against the agent card. The caller picks a network, signs EIP-3009 and retries passing `x_payment`; the paid response returns the signed result with the X-PAYMENT-RESPONSE header already decoded.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "ruta", "body" ], "properties": { "body": { "type": "object", "description": "The JSON body of the listing's v1 contract (see nomicheck_ejemplo / nomicheck_schema).", "additionalProperties": {} }, "ruta": { "enum": [ "liquidar", "retencion", "verificar", "liquidacion-final", "pago-onchain", "comprobante" ], "type": "string", "description": "Route to run." }, "x_payment": { "type": "string", "description": "Serialized EIP-3009 authorization; sent as the X-PAYMENT header." } }, "additionalProperties": false }arguments 32 linesnomicheck_schema reads unknown never probed
Free. The JSON Schema Draft 7 of the `/liquidar` input, generated from the same zod that validates at runtime — there is no second source that could lie.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesnomicheck_info reads unknown never probed
Free. Summarizes the wrapper's OpenAPI (products, x402 prices, accepted networks) and performs the safety cross-check: it reads the `payTo` the 402 announces TODAY and compares it against the `walletAddress` of the agent card on the apex. Call it before signing any payment — if `cruce.coinciden` is not true, do not sign.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 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 idf73467ae7572de81.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f73467ae7572de81/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f73467ae7572de81?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.
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.
- ynt.codes ynt-labs
- nagual.ynt.codes nagual