BD quantoracle
63 deterministic quantitative finance calculations via MCP. Options pricing, Greeks, implied volatility, exotic derivatives, risk metrics, portfolio optimization, Monte Carlo simulation, statistics, crypto/DeFi, macro/FX, time value of money.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureData and analyticsAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 7
✓ No critical or high findings
Medium and low: 7
-
low Secrets in code
secret-high-entropy-tokendist/index.js:10High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const WALLET = process.env.WALLET_ADDRESS || "0xC9…af6";
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:228High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…l1I+R1H7…G3i/cYFJ…fIw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:262High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…XcW+/GvMN…kxZ/opySAZMrc+9LY/WyjA…InQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:279High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…qEP+UeRV…fdw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:313High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Fnw/+3lVx…cQS+Yu6w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:415High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…UzV+AA46…P4O+ng17CA==",
detector -
low Secrets in code
secret-high-entropy-tokensrc/index.ts:17High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const WALLET = process.env.WALLET_ADDRESS || "0xC9…af6";
quoted
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (quantoracle) differs from the folder (quantoracle-mcp)
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Execution cost. Instruction body is 665 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 242: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: suspicious
This finance MCP is not clearly malicious, but it needs Review because local use sends financial inputs to QuantOracle’s remote API without clear per-tool disclosure.
LLM: suspicious (high) · VirusTotal: · 29 May 2026