Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

Available components

0 this week 56 Trust /100

Last scanned (18 hours ago)

Scores higher than 52% of PyPI servers

Category Developer Tools

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability51
  • 29% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2343 tokens (~90/item across 26 items; 15 tools + 11 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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

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.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 5 Nov 26 41

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed pypi/aadc-mcp@0.2.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 31 packages
Packages resolved 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~1,696 tokens

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 →

Tool Tokens
ask_session ~70

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.

NameTypeReqDescription
max_linesinteger––
requeststringyes–
session_idstringyes–

No output schema declared.

No examples provided.

check_environment ~117

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

close_session ~25

End a live session and free its process.

NameTypeReqDescription
session_idstringyes–

No output schema declared.

No examples provided.

get_example ~29

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

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

inspect_tape ~242

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.

NameTypeReqDescription
max_linesinteger––
requeststringyes–
tape_idstringyes–

No output schema declared.

No examples provided.

list_examples ~83

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_sessions ~25

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tapes ~33

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

load_tape ~54

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.

NameTypeReqDescription
pathstringyes–

No output schema declared.

No examples provided.

open_session ~214

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.

NameTypeReqDescription
args–––
pathstringyes–
python–––
timeout_sinteger––

No output schema declared.

No examples provided.

replay ~243

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.

NameTypeReqDescription
assignmentsstringyes–
outstringyes–
path_recordedboolean––
tape_idstringyes–

No output schema declared.

No examples provided.

replay_session ~119

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.

NameTypeReqDescription
assignmentsstringyes–
outstringyes–
path_recordedboolean––
session_idstringyes–

No output schema declared.

No examples provided.

run_example ~65

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.

NameTypeReqDescription
namestringyes–
timeout_sinteger––

No output schema declared.

No examples provided.

set_source_root ~135

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.

NameTypeReqDescription
compiled_prefixstringyes–
local_dirstringyes–
tape_idstringyes–

No output schema declared.

No examples provided.

trace_script ~242

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.

NameTypeReqDescription
args–––
outputs–––
pathstringyes–
python–––
timeout_sinteger––
workdir–––

No output schema declared.

No examples provided.

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.

pypi · aadc-mcp

# add to Claude Code
claude mcp add com-matlogica-aadc-mcp -- uvx aadc-mcp
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.