DueWall
Read-only MCP server for DueWall - tokenized private credit data: DLI index, DCR reference rate, debt calendar events, upcoming maturities, human-verified liquidity terms, pools, and claim-vs-observed verification verdicts. Bitcoin-anchored, evidence-linked, CC-BY.
Documentation
duewall-adapters
Open-source extraction adapters and CC-BY data snapshots for DueWall — the debt calendar, daily data & event alerts for tokenized credit, built for the RWA (real-world asset) data ecosystem.
Why this exists — everyone publishes TVL and APY for tokenized credit; nobody publishes when it comes due. Chains only record history: Maple's public API lists 266 loans, all matured, zero forward maturities visible on-chain. The forward-looking layer lives in documents — factsheets and loan agreements. These adapters read them, with per-field source links and human verification, to restore the liability time-axis that TradFi investors expect.
Public on-chain APIs only show settled history. When a tokenized private-credit loan matures, when a fund's redemption window opens, what the lockup terms are — that lives in documents (loan agreements, fund factsheets), not in chain state. Example: Maple's public API lists 266 loans, all matured; zero future maturities are visible on-chain.
DueWall builds the forward-looking calendar by reading those documents. This repository contains the parts we open:
runtime/ universal adapter runtime — one engine set (chain/rest/graphql);
honesty rules & verification hooks live here (MIT)
profiles/ declarative per-issuer configs (JSON Schema v1.3) — adding an
issuer = a data file, not code
adapters/ legacy per-issuer adapters (MIT) — kept for provenance;
new issuers go through profiles
data-snapshots/ periodic CC-BY snapshots of the structured output
tools/ snapshot builder, profile/adapter validators
docs/ event schema, profile spec, contribution guide
Coverage grades (A / B / M)
Every record on duewall.com — and every row in the API and snapshots — carries a
coverage grade (grade field). Grades describe data completeness, never
credit quality:
| Grade | Meaning | Currently |
|---|---|---|
| A | Terms human-verified against issuer factsheets & published (structured terms + fund page) | JTRSY, JAAA, SPXA, NYHB, SIEM, all Centrifuge pools |
| B | Events covered by machine adapters with source links; structured terms pending human verification | Maple, Goldfinch, Ondo, OpenEden, Credix, Pareto |
| M | Below the TVL bar for a dedicated adapter; monitored for promotion | Midas RWA, VanEck VBILL, Clearpool |
Rules: an event-level record can never exceed the grade of the entity it belongs
to; unmatched rows default to B (machine-collected, source-linked). New
issuers enter at B and move to A only after a factsheet pass in human
verification. The grade registry lives in
tools/build_snapshots.py (COVERAGE_GRADES) and
is kept in sync with the pipeline. Full policy: duewall.com/coverage/.
Why open?
- Auditability — every datapoint on duewall.com links back to its source. The adapters show exactly how each field was extracted, so you don't have to trust us: verify us.
- Coverage is communal — one issuer adapter per module. Contributing an adapter for an issuer we don't cover yet extends the calendar for everyone.
- Citation-friendly — data snapshots are CC-BY 4.0: use them in research, newsletters, dashboards. Cite and link; that's the whole price.
One runtime, many profiles (summary)
New issuers are declarative profiles (JSON), not code: a profile says where
the data lives (contract addresses / API endpoints) and how fields map to
schema v1.3 events (maturity · liquidity_window · rate_decision · resolutions); the runtime owns transport, honesty rules (no guessed dates,
mandatory source_url, status: draft until human-checked) and the
human-verification overrides. See
docs/PROFILE_SPEC.md and the pilots:
profiles/pareto_credit.json (on-chain),
profiles/maple_loans.json (GraphQL),
profiles/defillama_rwa.json (REST).
The legacy adapters in adapters/ stay runnable for provenance;
genuinely new semantics (a protocol that doesn't fit any profile) are engine
changes, reviewed by maintainers — never crammed into config flags.
Quickstart
Just want the data? (no code required) — grab the latest CSV from
data-snapshots/ (coverage rules: duewall.com/coverage/)
and cite per
data-snapshots/CITATION.md. Python client on
PyPI: pip install duewall (pypi.org/project/duewall,
zero dependencies). Or load the CSVs directly:
import pandas as pd
terms = pd.read_csv("data-snapshots/2026-11-05/terms.csv")
events = pd.read_csv("data-snapshots/2026-11-05/events.csv")
# every row links back to its source document; `grade` = coverage grade (A/B/M)
print(events[["token", "event_type", "date", "status", "grade", "source_url"]].head())
Want to refresh the data yourself? — run an adapter against its public source (standard library only, no key required):
python adapters/maple_loans.py --out events_maple.jsonl
# -> 266 loans -> events_maple.jsonl | future-dated: 0
Free public API (no key required)
The full dataset behind this repo is also served as static JSON at https://duewall.com/api/v1/ — CORS-enabled, CC-BY 4.0:
curl https://duewall.com/api/v1/events.json # all events (schema v1.2), each with a coverage grade
curl https://duewall.com/api/v1/terms.json # liquidity terms per fund (grade included)
curl https://duewall.com/api/v1/pools.json # pool NAV + TVL/APY snapshot
curl https://duewall.com/api/v1/meta.json # version, counts, license
Docs: https://duewall.com/api/ · Schema: docs/SCHEMA.md
Data snapshots
See data-snapshots/ — CSV/JSON, one directory per snapshot
date. License: CC-BY 4.0 (code in this repo: MIT). Citation formats in
data-snapshots/CITATION.md.
Bitcoin-anchored — every published manifest carries its own MANIFEST.ots
(OpenTimestamps): anyone can verify, without trusting us, that this data existed at its
stated date, unaltered. Daily internal snapshots are hash-chained (each day binds the
previous anchor) and served free via the
public API — including a daily on-chain NAV/price
series per pool token (/api/v1/price_history.json).
Source-document hashes — FACTSHEETS.json in each snapshot lists the sha256 of every
issuer factsheet PDF that legal_doc events were extracted from, together with the official
source URL. We do not redistribute the documents (publisher copyright); download from the
issuer gateway and verify the hash. Those hashes are covered by the same MANIFEST.ots
Bitcoin proof.
Contributing
Read docs/CONTRIBUTING.md. In short: one issuer =
one profile (a JSON data file — no code to review, CI validates schema + runs
it and checks every emitted event, then auto-merges when green). Public sources
only; nothing guessed; the first events land in human verification before they
publish.
Links
- Live site & weekly digest: https://duewall.com
- Fund/issuer pages with structured terms: https://duewall.com/centrifuge.html
- Analysis: Why on-chain data can't tell you when tokenized credit matures
License
MCP server (for AI agents)
Two ways to connect — same 8 tools, same daily snapshots:
1. Remote endpoint (no install, recommended): POST https://duewall.com/mcp
— key-less read-only JSON-RPC (protocol 2025-06-18), CORS-enabled. In Claude
Desktop / Claude Code / Cursor, add it as a remote MCP server with that URL.
That's it.
2. Local stdio server: runtime/mcp_server.py — for clients that prefer a
local process:
pip install "mcp>=1,<3" # 1.x and 2.x both supported
python runtime/mcp_server.py # stdio transport
Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"duewall": {
"command": "python",
"args": ["/path/to/duewall-adapters/runtime/mcp_server.py"]
}
}
}
Tools: get_dli, get_dcr, get_events, get_upcoming_maturities,
get_terms, get_pools, get_verification, get_verification_log.
Tools: get_dli (index), get_dcr (SSR rate), get_events (filterable, newest
first), get_upcoming_maturities(days) (the forward-looking liability layer),
get_terms (human-verified liquidity terms), get_pools (TVL/APY snapshot).
Same rules as the site: CC-BY data, per-record source links, grade A = human-verified,
B = machine-collected, M = mixed, honest dashes where the chain does not answer.
Optional env DUEWALL_API_KEY_FILE points to a file holding a free API key
(1,000 req/day, https://duewall.com/account). Not investment advice.
Interface policy (dual protocol): REST is the source of truth — metering, API keys and
the commercial tier live there. This MCP server is a key-less read-only discovery surface
for agents, reading the same public snapshots (zero data fork). Verification request and
report-ordering flows are Web processes and will not be MCP-ified: agents get read-only
verdict data (get_verification), humans get the process on duewall.com.