Recurrence Cloud Scheduler bronze
api.recurrence.cloud
“Recurring job scheduling as a service: create cron/human-readable schedules that deliver signed webhooks or invoke tools on registered MCP servers. Includes due delivery batching by event subject, run history and tool-catalog management.
https://api.recurrence.cloud/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 15 Dec 2026 as of our check on 10 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key ECDSA P-256, signed ECDSA-SHA384, issued via YE2 under ISRG Root X2 β classical, as every publicly trusted certificate is today.
Names on this certificate (1)
api.recurrence.cloud. - Connection
- TLS 1.3 Β· X25519MLKEM768 β post-quantum hybrid key exchange, agreed with our checker on 10 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 3 Nov 2026
View verification details
- Assurance
- bronze Bronze β agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- πΊπΈ US Β· OVH SAS (AS16276)
- Last checked
- 5d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks β the operator of api.recurrence.cloud controls every word below.
Create Scheduled Task
Create a recurring schedule in one call: recurrence (cron or human-readable) + delivery target (a signed webhook, or a tool invoked on a registered MCP server) + optional first event. One-shot, everything included.
- Schedule an hourly webhook ping to https://ops.example.com/hook
- Run the rotate_keys tool on my Ops MCP server every Monday at 09:00
Manage Schedules
Create, list, inspect, update, delete recurring schedules. Update accepts any combination of name, recurrence fields and delivery target changes.
Schedule Inspection
Dry-run the due-schedules check at a point in time (test_schedule_due) and review schedule definitions, events and registered MCP tool servers β read-only.
- When will my 'Nightly key rotation' schedule fire next?
Register MCP Tool Server
Register an external MCP server (Streamable HTTP) whose tools can then be invoked by schedules; imports the server's tool catalog on registration.
Manage Webhooks
Register and list webhook URLs; payload deliveries are HMAC-signed per event.
Browse Tenant
List apps and environments in the authenticated organization to orient an agent before creating schedules (whoami, list_apps, list_environments).
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- Recurrence Cloud β what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.3.0
- Auth schemes
- apiKey
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard pushNotifications streaming
- Agent card
- https://api.recurrence.cloud/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.