# MatLogica AADC: AAD, Greeks and the AADC Tracer (pypi · aadc-mcp)

AAD from your coding agent: exact Greeks with MatLogica AADC, and a price traced to its source line

- Trust score: 56/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `aadc-mcp`: 56/100 (this document), [markdown](https://verifymcp.io/servers/com-matlogica-aadc-mcp/aadc-mcp.md), [page](https://verifymcp.io/servers/com-matlogica-aadc-mcp/aadc-mcp)

## Channel facts

- Registry: `pypi`
- Package: `aadc-mcp`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (Proprietary) isn't a recognized OSI-approved license.
  - Actively maintained (last published 15 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 51/100
  - 29% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2343 tokens (~90/item across 26 items; 15 tools + 11 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the MatLogica AADC: AAD, Greeks and the AADC Tracer MCP server?

MatLogica AADC: AAD, Greeks and the AADC Tracer runs locally as a PyPI package, launched with uvx aadc-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-matlogica-aadc-mcp -- uvx aadc-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-matlogica-aadc-mcp": {
      "command": "uvx",
      "args": [
        "aadc-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-matlogica-aadc-mcp": {
      "command": "uvx",
      "args": [
        "aadc-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-matlogica-aadc-mcp -- uvx aadc-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-matlogica-aadc-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "aadc-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-matlogica-aadc-mcp --command uvx --arg aadc-mcp
```

### Hermes

```yaml
mcp_servers:
  com-matlogica-aadc-mcp:
    command: "uvx"
    args: ["aadc-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-matlogica-aadc-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "aadc-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-matlogica-aadc-mcp -t stdio -c uvx -a aadc-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-matlogica-aadc-mcp": {
      "command": "uvx",
      "args": [
        "aadc-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 56, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-05 (score 41)

First indexed and scored.

## MCP tools (15)

### `check_environment` (~117 tokens)

What this interpreter can do with AADC and the Tracer, measured: installed packages and versions, platform,
licence (one sentence naming the edition the engine runs as and what it permits; tell the user), an engine
self-test (record, replay, reverse: dz/dx = 6 at x = 3), a tracing self-test (one traced QuantLib call must
attribute leaves to QuantLib's C++), and findings with the pip command that fixes each.
Call it first; call it again after installing anything.

### `trace_script` (~242 tokens)

Run a Python script with tracing on and keep the record (tape) it leaves. The script needs no changes: it runs
in its own directory with AADC_TRACE=1, so every calculation through aadc types or an AADC-built library such as
aadc-quantlib-tracing is recorded with its source coordinates. Returns tape_id, the script's stdout and stderr,
the engine's census (frozen branch sites, outputs) and stats. A script that records itself and ends with
f.save_tape() writes to AADC_TRACE_OUT; mark its first line with 'mode=explicit'.
outputs: optional AADC_TRACE_OUTPUTS entries, e.g. ['value=123.45'] or ['pricer.py:42'], to name the program's
results on the tape. python: another interpreter to run under (the one where the user's packages live).
This runs the user's own code on the user's own machine; it is not a sandbox.

Input parameters:

- `args`
- `outputs`
- `path` (string, required)
- `python`
- `timeout_s` (integer)
- `workdir`

### `inspect_tape` (~242 tokens)

Ask the tape one question in the engine's own grammar and get its text answer plus the parsed header.
Verbs: 'stats' | 'leaves [kind=input|constant] [by=leaf] [limit=N]' | 'branches order=margin [limit=N]' |
'sites [file=NAME] [limit=N]' | 'at FILE:LINE [context=N]' (source with the recorded values; hash=ok means the
file shown is the one compiled) | 'find value=X' (where a printed number was computed) | 'origin #N' (the formula
behind a value) | 'uses #N' | 'cone #N' (which leaves can move a value, by derivative or only by a branch) |
'source root=COMPILED=LOCAL' (map compiled paths to a local source tree) | 'replay ...' (prefer the replay tool).
Ids are #N from earlier answers. A malformed request answers status=error in the header, never an exception.

Input parameters:

- `max_lines` (integer)
- `request` (string, required)
- `tape_id` (string, required)

### `replay` (~243 tokens)

Re-evaluate the tape at new inputs without re-running the model. assignments: '#12=101' or '#12=101,#15=0.21'
(leaf ids from 'leaves kind=input' or 'leaves by=leaf'); out: the output id from 'find value=<printed price>'.
survives=true: the recorded path holds and value is exact (equal to a fresh run to the last digit).
survives=false: WITHHELD; flipped names the decision (file:line, decided true -> false) and unchecked the
conversions the tape cannot check. There is no value to quote in that case. A tape read back from a file keeps
no operand for a counted conversion, so on most QuantLib tapes a replay is withheld with unchecked naming the
line (often errorfunction.cpp:200); say so and re-run the script at the new inputs for the price.
path_recorded=true returns the recorded path's value labelled as such, for comparison only.

Input parameters:

- `assignments` (string, required)
- `out` (string, required)
- `path_recorded` (boolean)
- `tape_id` (string, required)

### `set_source_root` (~135 tokens)

Map the compiled source prefix recorded on the tape (for aadc-quantlib-tracing 1.41 it is
/project/work/QLAADC/ql) to a local directory holding that source, so 'at FILE:LINE' and 'origin' can show the
code. Later answers say hash=ok when the local file is the one the library was compiled from and hash=MISMATCH
when it is not; a mismatch is reported, never silent. Remembered for this tape.

Input parameters:

- `compiled_prefix` (string, required)
- `local_dir` (string, required)
- `tape_id` (string, required)

### `load_tape` (~54 tokens)

Register an existing .tape file written earlier (by trace_script, by a script's own save_tape(), or downloaded
from a report) and return its tape_id and stats.

Input parameters:

- `path` (string, required)

### `list_tapes` (~33 tokens)

The tapes this server holds: id, file, size, the script that produced each, and the source roots applied.

### `open_session` (~214 tokens)

Run a Python script that records itself (aadc.Functions, start_recording with marked inputs, stop_recording)
and keep its process alive, so later questions are answered by the object that recorded. Returns session_id, the
script's stdout, which Functions object was kept, and its stats. Why: a record read back from a file cannot
re-check a counted conversion, so 'replay' on it is often withheld; in the recording process the same replay is
exact (the same digits as pricing again). Use it for what-ifs and sensitivities on a script with marked inputs;
for an unmodified script use trace_script. The script's save_tape() to AADC_TRACE_OUT also registers a tape.
Idle sessions close themselves after AADC_MCP_SESSION_IDLE_S seconds (default 1800). This runs the user's own
code on the user's own machine.

Input parameters:

- `args`
- `path` (string, required)
- `python`
- `timeout_s` (integer)

### `ask_session` (~70 tokens)

The same question grammar as inspect_tape (stats, leaves, branches, sites, at, find, origin, uses, cone,
source), answered by the live recording of an open_session.

Input parameters:

- `max_lines` (integer)
- `request` (string, required)
- `session_id` (string, required)

### `replay_session` (~119 tokens)

Replay the live recording at new inputs. assignments: '#0=101' (leaf ids from ask_session 'leaves kind=input
by=leaf'); out: the id marked OUTPUT from 'find value=<printed price>'. survives=true means the recorded path holds
and value is exact to the last digit; survives=false is WITHHELD with the decision named (flipped) and no value.

Input parameters:

- `assignments` (string, required)
- `out` (string, required)
- `path_recorded` (boolean)
- `session_id` (string, required)

### `close_session` (~25 tokens)

End a live session and free its process.

Input parameters:

- `session_id` (string, required)

### `list_sessions` (~25 tokens)

The live sessions this server holds: id, script, start time, questions answered.

### `list_examples` (~83 tokens)

Bundled scripts to start from: plain AADC (any platform), and unmodified QuantLib pricers that
aadc-quantlib-tracing records (Linux x86-64, macOS arm64). mode=auto scripts are traced as they are; mode=explicit scripts
record themselves and print sensitivities. Each is a starting point to copy and edit.

### `get_example` (~29 tokens)

The source of one bundled example, to read, copy or adapt.

Input parameters:

- `name` (string, required)

### `run_example` (~65 tokens)

Copy one bundled example into the server's working folder, run it with tracing on and return its tape_id,
its printed output and the tape's stats. Then question the tape with inspect_tape and replay.

Input parameters:

- `name` (string, required)
- `timeout_s` (integer)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-matlogica-aadc-mcp/aadc-mcp#diagnostics

## Score history

- 2026-11-21: 56
- 2026-11-20: 56
- 2026-11-19: 56
- 2026-11-18: 56
- 2026-11-17: 56
- 2026-11-16: 56
- 2026-11-15: 56
- 2026-11-14: 56
- 2026-11-13: 56
- 2026-11-12: 56
- 2026-11-11: 56
- 2026-11-10: 56
- 2026-11-09: 56
- 2026-11-08: 56
- 2026-11-07: 56
- 2026-11-06: 56
- 2026-11-05: 41

## Common questions

### What is the MatLogica AADC: AAD, Greeks and the AADC Tracer MCP server?

MatLogica AADC: AAD, Greeks and the AADC Tracer is an MCP server listed in the public MCP registry as com.matlogica/aadc-mcp. AAD from your coding agent: exact Greeks with MatLogica AADC, and a price traced to its source line. This page covers its PyPI package (aadc-mcp).

### Is the MatLogica AADC: AAD, Greeks and the AADC Tracer MCP server safe to use?

MatLogica AADC: AAD, Greeks and the AADC Tracer scores 56 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 MatLogica AADC: AAD, Greeks and the AADC Tracer MCP server expose?

MatLogica AADC: AAD, Greeks and the AADC Tracer exposes 15 tools: check_environment, trace_script, inspect_tape, replay, set_source_root, and 10 more. Their descriptions and schemas cost roughly 1,696 tokens of context every time the server is loaded.

### Is the MatLogica AADC: AAD, Greeks and the AADC Tracer MCP server still maintained?

MatLogica AADC: AAD, Greeks and the AADC Tracer is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the MatLogica AADC: AAD, Greeks and the AADC Tracer MCP server under?

MatLogica AADC: AAD, Greeks and the AADC Tracer declares the Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

### What did VerifyMCP test on the MatLogica AADC: AAD, Greeks and the AADC Tracer MCP server?

VerifyMCP ran 14 checks on MatLogica AADC: AAD, Greeks and the AADC Tracer, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about MatLogica AADC: AAD, Greeks and the AADC Tracer: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/aadc-mcp/
- Socket report: https://socket.dev/pypi/package/aadc-mcp
- Website: https://matlogica.com/products/aadc-tracer
- Changelog RSS feed: https://verifymcp.io/servers/com-matlogica-aadc-mcp/aadc-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-matlogica-aadc-mcp/aadc-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-matlogica-aadc-mcp/aadc-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-matlogica-aadc-mcp/aadc-mcp
