_ registry / mcp + a2a streamable-http · checked 3h ago

402cron

https://402cron.com

Registry code: de2a558ba29e5885

api record

Scheduled HTTP delivery for autonomous agents, paid with x402. Management tools need `Authorization: Bearer <management token>` — the token is issued ONCE when you buy, and there is no OAuth and no account. Start with `get_pricing`: it returns the payment requirements and the buy URL for each pack. Pay over plain HTTP with your x402 client; the response carries your token. You need your own public https:// endpoint that can echo a one-time verification challenge.

endpoint
https://402cron.com/mcp
door code
315a71759c659c6b
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 it live, free and safe measured by this hub
Is 402cron live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is 402cron free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does 402cron have?
16 tools: run_task_now, create_task, update_task, delete_task, restore_task, verify_destination, delete_destination, resume_task, ….
Is 402cron 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.4%

90 days 99.3%· all time 99.4%

latency
1,888ms

last good check

priced tools
0

of 16 tools

_ answered our checks, 90 days 1811 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· endpoint unreachable (timeout after 20000ms); card still served
  • degraded → live
_ what it is for
topic
infrastructure & devops
used for
  • schedule recurring http requests
  • register a webhook destination
  • pause or resume a scheduled task
  • run a scheduled task now
takes → gives
data → data
tools
6 reads10 changes data
_ 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 3 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
18

distinct

settlements
217

last 2026-11-10

received on chain
8.25 USDC

concentrated, shared-payto

_ what it can do 16 tools
3 open2 auth-required 11 never probed 5 of 16 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.

  • get_pricing reads open 6h ago

    What a delivery costs, which packs exist, and the exact x402 payment requirements for each. Balance is counted in DELIVERIES, not money, and packs never expire. Call this before buying.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_docs reads open 6h ago

    One section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit `section` to get the whole document.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "section": {
      "enum": [
        "quickstart",
        "verification",
        "headers",
        "signature",
        "notice",
        "errors",
        "billing",
        "limits"
      ],
      "type": "string",
      "description": "Which section to return. Omit for all of it."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • get_service_status reads open 11h ago

    Whether the service is currently selling, on which network, and if not — why not. This is configuration, not liveness: the full health endpoint is at /health.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_destinations reads auth-required 11h ago

    The URLs you have claimed and whether each is verified. The signing secrets are never shown again.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_tasks reads auth-required 11h ago

    Your tasks and their state. Needs your management token as an Authorization header on this connection.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "after": {
      "type": "string",
      "description": "Cursor from a previous page."
    },
    "limit": {
      "type": "integer",
      "description": "How many to return."
    },
    "state": {
      "type": "string",
      "description": "Filter by state: live (default), all, or one exact state such as active or paused_by_client."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • run_task_now changes data unknown never probed

    Deliver immediately, outside the schedule. THIS COSTS ONE CREDIT per attempt, exactly like a scheduled firing, and a timeout or unreachable host is retried up to three times — so one call can cost up to three credits. Use it to test a destination.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Task id (UUID), as returned by create_task or list_tasks."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • create_task changes data unknown never probed

    Register a schedule against a destination you have already verified. Idempotent on "name": the same name updates the existing task instead of creating a second one. Creating costs nothing; each delivery ATTEMPT costs one credit.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "cron",
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The https:// destination. It must already be registered and verified — see register_destination."
    },
    "body": {
      "description": "The body we send. Stored in the clear, so it must not carry credentials. A non-string is serialized as JSON."
    },
    "cron": {
      "type": "string",
      "description": "5 fields, UTC only, one minute at the finest. Operators: * a-b a,b */n a-b/n. Names: SUN-SAT (day), JAN-DEC (month). Macros: @yearly @annually @monthly @weekly @daily @midnight @hourly. Day-of-week is 0-6 with 0 = Sunday; 7 also means Sunday. Write days as names (MON-FRI). Numbers differ between schedulers: Quartz, AWS EventBridge and Cloudflare number Sunday as 1, we and croniter as 0. Translated for you: \"?\". \"?\" as a whole day-of-month or day-of-week field becomes \"*\". A NUMERIC day-of-week next to \"?\" is refused, because \"?\" means the expression was written where Sunday is 1. Refused: Quartz L, Quartz W, Quartz #, six fields (seconds), seven fields (year), @reboot, @every, CRON_TZ= prefixes, time zones of any kind — each with a code saying what to send instead."
    },
    "name": {
      "type": "string",
      "description": "Your name for the task. Unique among your live tasks; creating with an existing name updates it."
    },
    "method": {
      "type": "string",
      "description": "HTTP method of the delivery. Default POST. GET and HEAD carry no body."
    },
    "headers": {
      "type": "object",
      "description": "Headers we send with the delivery. Stored ENCRYPTED at rest — put credentials here, never in the body."
    },
    "timeoutMs": {
      "type": "integer",
      "description": "How long we wait for your server, 250-2000 ms. Answer 202 and do the work behind it."
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
  • update_task changes data unknown never probed

    Change the schedule, destination, method, timeout, headers or body of an existing task. Omit a field to leave it unchanged — sending null is refused, because "unchanged" and "cleared" must not look the same. State is NOT editable here: use pause_task and resume_task.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Task id (UUID), as returned by create_task or list_tasks."
    },
    "url": {
      "type": "string",
      "description": "The https:// destination. It must already be registered and verified — see register_destination."
    },
    "body": {
      "description": "The body we send. Stored in the clear, so it must not carry credentials. A non-string is serialized as JSON."
    },
    "cron": {
      "type": "string",
      "description": "5 fields, UTC only, one minute at the finest. Operators: * a-b a,b */n a-b/n. Names: SUN-SAT (day), JAN-DEC (month). Macros: @yearly @annually @monthly @weekly @daily @midnight @hourly. Day-of-week is 0-6 with 0 = Sunday; 7 also means Sunday. Write days as names (MON-FRI). Numbers differ between schedulers: Quartz, AWS EventBridge and Cloudflare number Sunday as 1, we and croniter as 0. Translated for you: \"?\". \"?\" as a whole day-of-month or day-of-week field becomes \"*\". A NUMERIC day-of-week next to \"?\" is refused, because \"?\" means the expression was written where Sunday is 1. Refused: Quartz L, Quartz W, Quartz #, six fields (seconds), seven fields (year), @reboot, @every, CRON_TZ= prefixes, time zones of any kind — each with a code saying what to send instead."
    },
    "name": {
      "type": "string",
      "description": "Your name for the task. Unique among your live tasks; creating with an existing name updates it."
    },
    "method": {
      "type": "string",
      "description": "HTTP method of the delivery. Default POST. GET and HEAD carry no body."
    },
    "headers": {
      "type": "object",
      "description": "Headers we send with the delivery. Stored ENCRYPTED at rest — put credentials here, never in the body."
    },
    "timeoutMs": {
      "type": "integer",
      "description": "How long we wait for your server, 250-2000 ms. Answer 202 and do the work behind it."
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • delete_task changes data unknown never probed

    Move the task to the recycle bin. It stops firing immediately and can be restored for 30 days with restore_task; after that it is unrecoverable. Credits already spent are not refunded.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Task id (UUID), as returned by create_task or list_tasks."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • restore_task changes data unknown never probed

    Bring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Task id (UUID), as returned by create_task or list_tasks."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • verify_destination changes data unknown never probed

    Verification is one request from us to the exact URL you registered: POST, headers X-402cron-Challenge: <value> and X-402cron-Event: verify, JSON body {"challenge":"<value>"}. Reply within 5 seconds, without a redirect, with a body that is the bare value or {"challenge":"<value>"}; we read the first 512 bytes and do not check the HTTP status (2xx is fine). Then call POST /api/destinations/{id}/verify within 15 minutes of registering. A fixed-response webhook cannot pass: you need an endpoint you can program. Registering a URL that is still pending issues a new challenge and a new signing secret every time — the old secret immediately stops verifying deliveries; a verified URL is left untouched unless you add ?rotate=1. The daily verification allowance (10 per destination, 40 per client, UTC day) does not reset on re-registration. Until this passes, no task may point at the destination.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "integer",
      "description": "Destination id, as returned by register_destination."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • delete_destination changes data unknown never probed

    Remove a claimed URL. Refused while a task still points at it — delete the task first.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "integer",
      "description": "Destination id, as returned by register_destination."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • resume_task changes data unknown never probed

    Start firing again on the schedule. Refused if your balance is empty — buy deliveries first.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Task id (UUID), as returned by create_task or list_tasks."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • pause_task changes data unknown never probed

    Stop firing until you resume. Nothing is charged while a task is paused.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Task id (UUID), as returned by create_task or list_tasks."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • register_destination changes data unknown never probed

    Claim an https:// URL you control. We answer with a challenge and a SIGNING SECRET that is shown ONCE and never again — store it before you do anything else; it is what lets you verify that a delivery really came from us. The permission covers that path and everything beneath it, nothing above. Verification is one request from us to the exact URL you registered: POST, headers X-402cron-Challenge: <value> and X-402cron-Event: verify, JSON body {"challenge":"<value>"}. Reply within 5 seconds, without a redirect, with a body that is the bare value or {"challenge":"<value>"}; we read the first 512 bytes and do not check the HTTP status (2xx is fine). Then call POST /api/destinations/{id}/verify within 15 minutes of registering. A fixed-response webhook cannot pass: you need an endpoint you can program. Registering a URL that is still pending issues a new challenge and a new signing secret every time — the old secret immediately stops verifying deliveries; a verified URL is left untouched unless you add ?rotate=1. The daily verification allowance (10 per destination, 40 per client, UTC day) does not reset on re-registration.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "The https:// URL you control."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • get_task reads unknown 6h ago

    A single task: schedule, destination, state, next run, and how many failures in a row it carries.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Task id (UUID), as returned by create_task or list_tasks."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
_ try it over mcp 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 de2a558ba29e5885.

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