DAP Foundry
REMOTE · FOUNDRY.DAP.SOLUTIONS
Tools that refuse rather than guess: settlement day counts, Unix timestamps, base64, line diffs.
Available components
Last scanned (48 minutes ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 775 tokens (~193/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compute-day-count-to-settlement” rewrote its description, which is the text the model reads security
- Tool “convert-unix-timestamp-to-date” rewrote its description, which is the text the model reads security
- Tool “decode-base64-to-text” rewrote its description, which is the text the model reads security
- Tool “diff-two-line-lists” rewrote its description, which is the text the model reads security
- Schema quality: 280 → 193 ▲ functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://foundry.dap.solutions/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=foundry.dap.solutions | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 721657c5f47a8bbd0efcfc8d01a709ec |
| SANs: foundry.dap.solutions | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of foundry.dap.solutions. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| solutions. | present | 23131 | 8 | Verified |
| dap.solutions. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foundry.dap.solutions/mcp | Verified | 200 | |
| http (plaintext) | http://foundry.dap.solutions/mcp | HTTPS enforced | 301 | https://foundry.dap.solutions/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compute-day-count-to-settlement Compute day count to settlement ~168
Use when you need a Canadian settlement date or accrual fraction. Rolls a trade date forward on the Payments Canada calendar and counts the accrual under ACT/360, ACT/365F, 30/360, 30E/360 or ACT/ACT-ISDA. $0.01 USDC on Base per answer via x402; a refusal is free.
| Name | Type | Req | Description |
|---|---|---|---|
| accrual_start | string | yes | a real calendar date, the first day of the accrual period, counted |
| acknowledge | string | yes | – |
| calendar | string | yes | – |
| convention | string | yes | – |
| freshness_tolerance | string | yes | at most the ratified ceiling |
| settlement_lag | – | yes | – |
| trade_date | string | yes | a business day on the calendar |
No output schema declared.
No examples provided.
convert-unix-timestamp-to-date Convert Unix timestamp to date ~138
Use when you need Unix timestamps as dates. Converts one or more timestamps, seconds or milliseconds, one per line, to UTC dates in ISO 8601 as a CSV. $0.01 USDC on Base per answer via x402; a refusal is free.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | 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 li… |
No output schema declared.
No examples provided.
decode-base64-to-text Decode base64 to text ~184
Use when you need to read base64 as text. Decodes standard base64 to UTF-8 text and refuses anything that is not valid base64 or not valid UTF-8, rather than guess. $0.01 USDC on Base per answer via x402; a refusal is free.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | 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 mu… |
No output schema declared.
No examples provided.
diff-two-line-lists Diff two line lists ~131
Use when you need to compare two lists of lines. Marks each distinct line only_a, only_b or both, matched exactly as sent, as a CSV. $0.01 USDC on Base per answer via x402; a refusal is free.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | 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. |
No output schema declared.
No examples provided.
How do I install the DAP Foundry MCP server?
DAP Foundry is a hosted endpoint at https://foundry.dap.solutions/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · foundry.dap.solutions
claude mcp add --transport http solutions-dap-foundry 'https://foundry.dap.solutions/mcp'
What is the DAP Foundry MCP server?
DAP Foundry is an MCP server listed in the public MCP registry as solutions.dap/foundry. Tools that refuse rather than guess: settlement day counts, Unix timestamps, base64, line diffs. This page covers its hosted endpoint (https://foundry.dap.solutions/mcp).
Is the DAP Foundry MCP server safe to use?
DAP Foundry scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DAP Foundry MCP server expose?
DAP Foundry exposes 4 tools: compute-day-count-to-settlement, convert-unix-timestamp-to-date, decode-base64-to-text, diff-two-line-lists. Their descriptions and schemas cost roughly 621 tokens of context every time the server is loaded.
Does the DAP Foundry MCP server require authentication?
No. We connected to DAP Foundry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DAP Foundry MCP server still maintained?
DAP Foundry is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.