dap-foundry
Registry code: 475f3c82aea27cd4
Deterministic tools from DAP Foundry. Each tool is one JSON endpoint, and its answer is that endpoint's envelope: status computed or refused, the refusal code and message, the result, the inputs echoed and the artifact hash that answered. A refusal says what to send instead; nothing is guessed. compute-day-count-to-settlement costs $0.01 per computed answer under x402; the others are free. Full rules: https://foundry.dap.solutions/hub.md
- endpoint
- https://foundry.dap.solutions/mcp
- 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 dap-foundry live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is dap-foundry free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does dap-foundry have?
- 4 tools: convert-unix-timestamp-to-date, decode-base64-to-text, compute-day-count-to-settlement, diff-two-line-lists.
- Is dap-foundry 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 100%· all time 100%
last good check
of 4 tools
- unknown → live
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
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
convert-unix-timestamp-to-date unknown 2h ago
Unix timestamps to UTC dates in ISO 8601. text holds one or more timestamps, one per line: whole seconds or milliseconds, where a magnitude of 100000000000 or more is milliseconds. The answer is a CSV of input, unit and date. It refuses empty text, more than 1,048,576 bytes or 10,000 lines, and any line that is not digits with an optional leading minus inside the years 0001 to 9999. Free. The answer is the JSON envelope of https://foundry.dap.solutions/api/convert-unix-timestamp-to-date, byte for byte, with the artifact hash that answered. Full rules: https://foundry.dap.solutions/hub.md
{ "type": "object", "required": [ "text" ], "properties": { "text": { "type": "string", "description": "One or more Unix timestamps, one per line: whole seconds or milliseconds, digits with an optional leading minus, inside the years 0001 to 9999. At most 1,048,576 bytes of UTF-8 and 10,000 lines; a line break at the very end is not a line." } }, "additionalProperties": false }arguments 13 linesdecode-base64-to-text unknown 2h ago
Base64 to UTF-8 text. text holds standard base64: A to Z, a to z, 0 to 9, + and /, padding optional; white space is ignored. It refuses empty text, more than 1,048,576 bytes, the URL-safe alphabet, a length or padding that cannot be base64, and bytes that are not valid UTF-8. Free. The answer is the JSON envelope of https://foundry.dap.solutions/api/decode-base64-to-text, byte for byte, with the artifact hash that answered. Full rules: https://foundry.dap.solutions/hub.md
{ "type": "object", "required": [ "text" ], "properties": { "text": { "type": "string", "description": "Base64 that decodes to UTF-8 text: the letters A to Z and a to z, the digits 0 to 9, + and /, then one or two = of padding at the end, which may be left out but, when given, must make the length a multiple of four. A length that leaves one character over a multiple of four is refused. White space anywhere is ignored and not counted in the length. At most 1,048,576 bytes of UTF-8, white space included." } }, "additionalProperties": false }arguments 13 linescompute-day-count-to-settlement unknown never probed
Settlement date on the Payments Canada holiday calendar, and the accrual fraction under ACT/360, ACT/365F, 30/360, 30E/360 or ACT/ACT-ISDA. Send all seven inputs, including acknowledge no-ruling-v1 and a freshness_tolerance in whole days written P<n>D. It refuses rather than guesses: a missing acknowledgement or tolerance, a tolerance over the ratified ceiling, calendar data older than your tolerance, a trade date outside the calendar's coverage or not a business day, and any missing, unknown or malformed input. Costs $0.01 in USDC on Base per computed answer, under x402; a refusal is not charged. The answer is the JSON envelope of https://foundry.dap.solutions/api/compute-day-count-to-settlement, byte for byte, with the artifact hash that answered. Full rules: https://foundry.dap.solutions/hub.md
{ "type": "object", "required": [ "accrual_start", "trade_date", "settlement_lag", "calendar", "convention", "acknowledge", "freshness_tolerance" ], "properties": { "calendar": { "enum": [ "ca-payments-canada" ], "type": "string" }, "convention": { "enum": [ "ACT/360", "ACT/365F", "30/360", "30E/360", "ACT/ACT-ISDA" ], "type": "string" }, "trade_date": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "a business day on the calendar" }, "acknowledge": { "enum": [ "no-ruling-v1" ], "type": "string" }, "accrual_start": { "type": "string", "pattern": "^\\d{4}-\\d{2}-\\d{2}$", "description": "a real calendar date, the first day of the accrual period, counted" }, "settlement_lag": { "oneOf": [ { "type": "string", "pattern": "^[0-5]$" }, { "type": "integer", "maximum": 5, "minimum": 0 } ] }, "freshness_tolerance": { "type": "string", "pattern": "^P(0|[1-9][0-9]{0,3})D$", "description": "at most the ratified ceiling" } }, "additionalProperties": false }arguments 65 linesdiff-two-line-lists unknown 2h ago
Compare two lists of lines. text holds a line ---A---, then list A, then a line ---B---, then list B. The answer is a CSV of each distinct line, matched exactly as sent, marked only_a, only_b or both. It refuses empty text, more than 1,048,576 bytes or 50,000 lines, and a text without the two markers in that order. Free. The answer is the JSON envelope of https://foundry.dap.solutions/api/diff-two-line-lists, byte for byte, with the artifact hash that answered. Full rules: https://foundry.dap.solutions/hub.md
{ "type": "object", "required": [ "text" ], "properties": { "text": { "type": "string", "description": "Two lists of lines: a line ---A---, then list A, then a line ---B---, then list B, one item per line. At most 1,048,576 bytes of UTF-8 and 50,000 lines; a line break at the very end is not a line." } }, "additionalProperties": false }arguments 13 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 id475f3c82aea27cd4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/475f3c82aea27cd4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/475f3c82aea27cd4?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.
- bellwether.dap.solutions DAP Bellwether