EVIDIQ Cadence
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@EVIDIQ Cadenceschedule a monitor to check my site's uptime every 5 minutes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
EVIDIQ Cadence is the fleet's temporal layer. AI agents don't have a future — they exist only for the duration of a request. Cadence sells time as a service: register a deadline, a reminder, a retry ladder, or a standing check, and Cadence wakes the agent at the right moment and hands back a signed receipt proving the wake-up was delivered.
Scheduling engine — one-shot, recurring (interval or cron), retry ladders, expirations with lead time, standing monitors and verification watches, and multi-step workflows with escalations.
MCP server — 18 tools (8 free, 10 paid) that turn a schedule spec into a durable, attested job:
schedule_*+reschedule/resume/attestfor money,validate/estimate/poll_due/verify_receipt/get_job/pause/cancel/capabilitiesfor free.
Launch status: Phase 2 — live and paid. Deployed at
https://mcp.evidiq.dev/cadence/mcp(port 3018), the x402 gate is on, and the first real paid call has settled on X Layer. Registered on OKX.AI as Agent #10405 with all 18 tools; listing under review. All 18 tools were verified live end-to-end through the OpenClaw agent (glm-5.2) — evidence indocs/live-test/.polldelivery is proven with EIP-191 receipts that verify against the fleet signer,webhookis implemented, anda2aremains unadvertised: no real firing has yet been observed arriving at a buyer agent's inbox, and no capability is listed here that has not been watched working.
What it does
Durable scheduling — One-shot, recurring (interval/cron), retry ladders, and expirations with configurable lead time; jobs survive container restarts (SQLite on a mounted volume).
Standing monitors — Recurring call to any target MCP tool plus a condition; fires only when the condition trips — the engine behind recurring revenue for the rest of the fleet.
Workflow chains — Ordered steps, each with its own deadline; a step that misses its deadline fires an escalation instead of silently stalling.
EIP-191 receipts — Every firing carries a signed receipt (JCS SHA-256 digest over the closed field set) plus an
idempotencyKey— at-least-once, never exactly-once, never early; late firings are marked with their delay.Attestation —
attest_executionbundles a job's whole firing history into a signed attestation, anchored on 0G.Free lifecycle —
pause_jobandcancel_jobcost nothing; stopping is always free, and a cancelled or expired job is a terminal state with a receipt — silence is never an outcome.
Related MCP server: synai-relay
Route to Cadence when
Use Cadence when a task must happen after the response ends: re-check a counterparty every six hours, retry a flaky upstream in six hours, renew a subscription on a date, watch an x402 challenge expiry with lead time, or keep a workflow moving when the agent is gone.
A natural chain: cadence_capabilities → validate_schedule → estimate_cost → schedule_monitor → poll_due → verify_receipt → attest_execution.
Proven on-chain
x402 Payment Settlement (X Layer, chain 196)
Tool | Amount | Settlement tx | Result |
|
|
|
Flow: HTTP 402 challenge → EIP-3009 signature → transferWithAuthorization (gasless for
the payer) → tool executes. Reproduce the quote with
onchainos payment quote https://mcp.evidiq.dev/cadence/mcp --method POST --tool schedule_job;
without --tool the CLI takes its discovery branch and returns the tool catalogue with an
empty accepts, which is correct behaviour and not an error.
0G Storage Anchoring (0G mainnet, chain 16661)
Anchor tx | Storage root | Verified |
|
|
OKX.AI Marketplace Registration
Property | Value |
Agent ID |
|
Agent Name |
|
Listing Status |
|
Registration Tx | |
OKX Agent URL | |
Agent Wallet |
|
Communication Addr |
|
Report Signer |
|
Services Registered | 18 Tools (10 Paid: $0.005–$0.03, 8 Free: $0.00) |
Eighteen MCP tools
Paid scheduling & attestation tools
Tool | USDT0 | Purpose |
|
| One-shot: run at an absolute timestamp or after a delay; payload returned verbatim on firing. |
|
| Fixed interval or cron expression, with optional end date and max-fires cap. |
|
| Backoff ladder (e.g. 1m, 10m, 1h, 6h) that stops on the first acknowledged delivery. |
|
| Watch a deadline and fire before it lapses, with configurable lead time. |
|
| Recurring call to a target MCP tool plus a condition; fires only when the condition trips. |
|
| Convenience wrapper over |
|
| Ordered chain of steps with per-step deadlines and escalations. |
|
| Change the time, interval, backoff, or payload of an existing job. |
|
| Return a paused job or series to active, keeping its history and |
|
| Signed bundle of a job's whole firing history, anchored on 0G. |
Free preflight and lifecycle tools
Tool | Purpose |
| Catalog: 18 tools, pricing, delivery modes actually proven, timing guarantees. |
| Parse and validate a schedule spec — cron, timezone, lead time, backoff — without creating anything. |
| Exact USDT0 price for a proposed schedule. |
| Read a job's spec, state, history, and pending deliveries. |
| Fetch due deliveries for a |
| Recompute the JCS digest and EIP-191-verify the signature against the fleet signer. |
| Freeze a recurring job; history and |
| Terminal cancel with a signed closing receipt; stopping is always free. |
Architecture
flowchart TB
agent["<b>AI agent / dev</b><br/>MCP client"]
request{"Tool call<br/>free or paid?"}
agent -->|POST /cadence/mcp| request
free["Free preflight & lifecycle<br/>capabilities · validate · estimate<br/>get_job · poll_due · verify_receipt<br/>pause · cancel"]
gate["x402 v2 gate<br/>EIP-3009 exact · pay per schedule<br/>402 unpaid · settles on X Layer"]
xlayer[("X Layer<br/>USD₮0 · eip155:196")]
request -->|free helper| free
request -->|paid schedule| gate
gate -. verify and settle .-> xlayer
subgraph cadence["EVIDIQ Cadence trust boundary"]
direction TB
store["1. Job store + ticker<br/>SQLite · mounted volume · lease claiming"]
engine["2. Schedule engine<br/>one-shot · recurring · retry · expiration"]
monitor["3. Monitor engine<br/>target MCP call + condition trip"]
receipt["4. EIP-191 receipt<br/>JCS SHA-256 digest · signature · idempotencyKey"]
deliver["5. Delivery<br/>poll · webhook"]
attest["6. Attestation + anchor<br/>firing-history bundle · EIP-191 signed"]
store --> engine --> monitor
monitor --> receipt
engine --> receipt
receipt --> deliver
receipt --> attest
end
og[("0G Storage<br/>Merkle root · upload tx<br/>chain 16661")]
free --> store
gate --> engine
attest -. best effort .-> og
og -. root + tx .-> response
response["<b>MCP response</b><br/>jobId + spec + receipt + attestation<br/>anchoring: anchored / failed"]
classDef client fill:#312e81,stroke:#a78bfa,color:#ffffff,stroke-width:2px;
classDef payment fill:#052e16,stroke:#4ade80,color:#ffffff,stroke-width:2px;
classDef core fill:#0f172a,stroke:#38bdf8,color:#ffffff,stroke-width:2px;
classDef output fill:#4c1d95,stroke:#c4b5fd,color:#ffffff,stroke-width:2px;
class agent,request client;
class free,gate,xlayer,og payment;
class store,engine,monitor,receipt,deliver,attest core;
class response output;
style cadence fill:#0f172a,stroke:#38bdf8,color:#e0f2fe,stroke-width:2px;Verification Log
All 18 tools tested live via the OpenClaw agent (glm-5.2) against https://mcp.evidiq.dev/cadence/mcp; raw run + HTML report + screenshot in docs/live-test/. This capture was taken in Phase 1 with X402_BYPASS=1, which is why the paid tools answer 200 below: the point of that run was to prove every tool's behaviour, not the gate. The gate was verified separately once it was switched on — see the Phase 2 block after the log.
Free Tools (HTTP 200)
cadence_capabilities → 200 ✓
validate_schedule → 200 ✓ (recurring ok; monitor without targetUrl rejected)
estimate_cost → 200 ✓
get_job → 200 ✓
poll_due → 200 ✓ (signed receipts + idempotencyKeys)
verify_receipt → 200 ✓ (digestValid + signatureValid, signer recovered)
pause_job → resume_job → 200 ✓
cancel_job → 200 ✓ (closing receipt signed)
Paid Tools (200 here because this run had the bypass on — see the Phase 2 block below)
schedule_job → 200 ✓ (fired in 5s, receipt signed)
schedule_recurring → 200 ✓
schedule_retry → 200 ✓
schedule_expiration → 200 ✓
schedule_monitor → 200 ✓
schedule_verification → 200 ✓
schedule_workflow → 200 ✓
reschedule_job → 200 ✓
resume_job → 200 ✓
attest_execution → 200 ✓ (digest + signature + firing history + 0G anchored)
HEAD /mcp → 402 · empty body (no hang) ✓
Empty POST /mcp → usage JSON ✓ · free tools answer bare {} ✓
Live receipt verification (curl, full signature)
digestValid: true ✓
signatureValid: true ✓
expectedSigner == recoveredSigner == 0x8a3c7524Aaed081825aC88eC7f4cCECFc583ee7D ✓Phase 2 — the gate, measured after the bypass was removed
Re-probed from outside once X402_BYPASS was deleted from the container environment and
the service redeployed. Every assertion below was observed, not inferred:
empty POST (with content-type) → 402
POST without content-type → 415
HEAD /mcp → 402, no hang
all 10 paid tools, bare {} → 402
schedule_job schedule_recurring schedule_retry schedule_expiration
schedule_monitor schedule_verification schedule_workflow
reschedule_job resume_job attest_execution
all 8 free tools, bare {} → 200 with content
cadence_capabilities estimate_cost validate_schedule verify_receipt
get_job poll_due pause_job cancel_job
onchainos payment quote --tool schedule_job → 0.005 USDT0, hasBalance true
onchainos payment pay → settled, tool executed
fleet sweep across all 17 services → broken_entries=0Live test through the OpenClaw agent (glm-5.2)
The Cadence skill was exercised end-to-end by the OpenClaw agent:
the agent read the skill, discovered the MCP server, and called all 18 tools in one run
against https://mcp.evidiq.dev/cadence/mcp. Full run output in docs/live-test/evtest3-out.json.

Use it from any agent
# Read the public Skill document
curl -s https://mcp.evidiq.dev/cadence/skill.md
# Inspect current x402 pricing discovery
curl -s https://mcp.evidiq.dev/cadence/x402
# Connect remote MCP server (OpenClaw)
openclaw mcp add evidiq-cadence --transport streamable-http --url https://mcp.evidiq.dev/cadence/mcp
# Connect remote MCP server (Claude Code)
claude mcp add --transport http evidiq-cadence https://mcp.evidiq.dev/cadence/mcpSelf-host
docker build -t evidiq-cadence:latest .
docker run -d --env-file .env -p 3018:3018 evidiq-cadence:latest
# Endpoint: http://localhost:3018/mcpLicense
EVIDIQ owns and licenses its original Cadence code under MIT. Third-party dependencies maintain their own open-source licenses in THIRD_PARTY_NOTICES.md.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenanceA hosted remote MCP server that lets your AI agent schedule tasks for later — reminders, delayed webhook callbacks, and recurring jobs. Read-only by design.Last updated5MIT
- Alicense-qualityDmaintenanceAn MCP server enabling AI agents to browse, claim, submit, and manage paid tasks on the SYNAI Relay agent-to-agent task protocol, with on-chain USDC settlement via x402.Last updatedMIT
- Alicense-qualityAmaintenanceMCP server for scheduling tasks with cron-like recurring jobs, one-time tasks, priority queues, retry logic, and job dependencies.Last updatedMIT
- Alicense-qualityBmaintenanceMCP server for agent-native and human-accessible payments using MPP and x402 protocols, enabling payment flows from CLI or agent hosts.Last updated5MIT
Related MCP Connectors
Workflow diagnostics, capability routing, and x402 settlement for MCP-compatible agents.
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
A paid remote MCP for agent memory MCP, built to return verdicts, receipts, usage logs, and audit-re
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/evidiq/evidiq-cadence-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server