"mongodb atlas" matching MCP tools:

• deltasignal_morning_brief

  DeltaSignal ATLAS-7

  Use this read-only composite workflow tool as the default first-pass DeltaSignal ATLAS-7 daily scan. It server-enforces the complete morning brief call plan: readiness, daily_changes, risk_distribution, top_stressed with limit 10, alpha_opportunities with limit 10, and alpha_opportunities_audit with limit 10. Parameters: optional output_mode=compact only; do not pass limit, offset, ticker, source_date, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it performs a bounded internal fan-out, has no destructive side effects, and preserves partial results if one required internal call fails. Use it for morning brief, daily brief, daily scan, current risk board, and newsroom first-pass requests; sell company-report or deep-brief issuer reports separately when the user wants drilldown explanation.

  Connector

• deltasignal_daily_change_evidence

  DeltaSignal ATLAS-7

  Use this read-only drilldown tool only when the user asks why one issuer or CIK was flagged in daily changes. It returns paginated raw CompanyFacts tag evidence for a specific ticker or CIK, plus page metadata and issuer identity. Parameters: ticker or cik is required; source_date is optional; limit defaults to 100 and is capped at 250; offset paginates the raw tag page. Behavior: read-only and idempotent; it performs one internal daily-changes read, filters evidence for one issuer/change, and has no destructive side effects. Do not use it for routine monitoring, Morning Brief, or Alpha Sweep unless the user explicitly asks for proof.

  Connector

• deltasignal_company_fundamentals

  DeltaSignal ATLAS-7

  Use this read-only tool to retrieve SEC XBRL-backed fundamentals for one crypto public company ticker. It returns filing period, entity identifiers, filing form, core financial values, provenance, and optional segment or related-party containers when requested. Parameters: ticker is required; period is optional YYYY-MM-DD; include_segments and include_related_party request additional containers when available and otherwise return availability metadata. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not modify SEC data, accounts, files, or wallets. Use it when the user asks for revenue, net income, assets, cash, liabilities, equity, SEC filing context, or fact provenance; use alpha_signals or covenant_stress for modeled signal interpretation.

  Connector

• deltasignal_top_stressed

  DeltaSignal ATLAS-7

  Use this read-only screening tool to rank the most stressed crypto public companies in the active DeltaSignal slice. It returns issuer rows sorted by stress, including ticker, period, risk tier, stress values, debt-coverage status, quality flags, linkbase provenance, live-price indicators, and pagination metadata. Parameters: limit is 1-100 and should usually be 5-20 for summaries; offset is only for pagination after a previous screen. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and never writes orders, files, accounts, or wallet state. Use it for portfolio triage, issuer watchlists, and deciding which companies deserve deeper covenant or alpha analysis; use covenant_stress with ticker for detail on one issuer.

  Connector

• deltasignal_daily_changes

  DeltaSignal ATLAS-7

  Use this read-only monitoring tool to retrieve the latest meaningful DeltaSignal daily change snapshot. It highlights tracked crypto filing deltas, newly discovered crypto issuers, source dates, computed timestamps, classification summary, and change statistics. Parameters: none; call it exactly as-is when the user asks what changed today or needs a monitoring summary. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write notifications, files, accounts, or wallet state. Use it for daily monitoring and freshness narratives; use readiness for service health and issuer-specific tools for detailed research on any ticker it mentions.

  Connector

• atlas_technique_search

  ContrastAPI

  Search the MITRE ATLAS catalog of AI/ML attack techniques by keyword, tactic, or maturity. Default response is SLIM (description truncated to 240 chars per row); pass include='full' for the verbose record. Pass exclude_id when chaining from atlas_technique_lookup to skip self in sibling-tactic searches. Use this to discover techniques matching a threat-model question, e.g. 'what techniques target LLM serving infrastructure?'. Drill into atlas_technique_lookup with any returned technique_id for the full description, ATT&CK bridge, and pivot hints. For broader cross-referencing: when a result has attack_reference_id, that bridges to D3FEND mitigations via d3fend_defense_for_attack. Free: 30/hr, Pro: 500/hr. Returns {query (echoed filters), total, results [{technique_id, name, description (truncated by default), tactics, inherited_tactics, maturity, attack_reference_id, subtechnique_of}], next_calls}.

  Connector

• deltasignal_alpha_opportunities_audit

  DeltaSignal ATLAS-7

  Use this read-only diagnostic tool to explain why the alpha-opportunity board includes, excludes, or demotes rows. It returns issuer-type, identity, quality-gate, and raw-alpha-versus-board-rank summaries from the same scoring universe used by deltasignal_alpha_opportunities. Parameters: limit is 1-100 for bounded samples; source_date replays a known YYYY-MM-DD slice; issuer_type narrows the audit to operating_company, etf_trust, fund_vehicle, foreign_issuer, unresolved_identifier, or all; include_rows=true attaches full publishable audit rows and should be used only for explicit debugging. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not change board scoring, payments, wallets, files, or account state. Use it after deltasignal_alpha_opportunities or deltasignal_alpha_sweep when the user asks why a high raw alpha row is missing, why ETF/trust/fund rows are excluded by default, why a row was demoted, or whether a screen is safe to summarize.

  Connector

• deltasignal_company_report

  DeltaSignal ATLAS-7

  Use this read-only composite workflow tool for the default full single-issuer DeltaSignal ATLAS-7 company report add-on. It server-enforces the complete company report call plan: readiness, company_fundamentals, alpha_signals, peer_ranking, covenant_stress, and SPECTRA field-map support for one normalized ticker. Parameters: ticker is required and normalized to uppercase; period, include_segments, include_related_party, and output_mode=compact are optional. SPECTRA is included when a field-map contract is available for the issuer. Behavior: read-only and idempotent; it performs six internal HTTPS reads, has no destructive side effects, rejects invalid tickers before fan-out, and preserves partial results if a required issuer leg fails. Use it when the user asks for a report, deep dive, issuer brief, or diligence package on one crypto public-company ticker, or when a Morning Brief top-stressed or alpha-screen row needs a separately sold explanation report; use low-level tools only for custom drilldowns.

  Connector

• deltasignal_readiness

  DeltaSignal ATLAS-7

  Use this read-only tool before analysis to verify that the DeltaSignal ATLAS-7 data plane is live, fresh, and safe to query. It returns service readiness, active source dates, issuer coverage, quality coverage, debt coverage, live-price status, market regime, and tower-coherence diagnostics. Parameters: none; call it exactly as-is when the user asks if DeltaSignal is ready or whether data freshness is acceptable. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, does not write external systems, and does not handle secrets or payments itself. Use it at the start of an agent workflow, after a deploy, or whenever results should be gated on freshness; use daily_changes for what changed and issuer tools for company-specific analysis.

  Connector

• deltasignal_top_stressed_natural

  DeltaSignal ATLAS-7

  Use this premium read-only Natural Language tool when the user wants the Top Stressed screen explained in human-readable Markdown. It renders compact ATLAS-7 Top Stressed evidence into an audit-grade brief while preserving returned ranks, stress values, quality flags, nulls, source dates, and caveats. Parameters: limit is 1-100, offset paginates, and style is professional, concise, trader, or detailed. Style changes tone and density only, not facts. Behavior: read-only and idempotent; it performs one HTTPS read against the Natural Language route, has no destructive side effects, and never executes trades, wallets, settlements, or writes. Use raw deltasignal_top_stressed for cheap structured JSON and this tool for premium human-facing summaries.

  Connector

• atlas_case_study_lookup

  ContrastAPI

  Look up a MITRE ATLAS case study — a documented real-world AI/ML attack incident. Each case study links a sequence of ATLAS techniques (techniques_used) to the incident. Default response is SLIM (description truncated to 240 chars); pass include='full' for the verbose narrative. Use this after atlas_technique_search to find which incidents have exercised a given technique. Drill into the full techniques_used array via bulk_atlas_technique_lookup in a single call (next_calls emits exactly that hint). Returns 404 when the id is not in the synced catalog. Free: 30/hr, Pro: 500/hr. Returns {case_study_id, name, description, techniques_used, next_calls}.

  Connector

• submit_sipflow_feedback

  Sipflow

  [cost: write (single MongoDB row) | rate-limited per IP: 3/min, 20/day] Send the Sipflow team feedback when something doesn't work, a vendor or RFC isn't covered, or a tool produced a wrong/incomplete answer. Categories: - docs_gap: search_sip_docs returned nothing useful, vendor missing, coverage incomplete - tool_bug: a tool errored, returned garbage, or behaved unexpectedly on a real input - wrong_answer: the answer it produced was incorrect for the SIP/VoIP question asked - feature_request: a new tool, dataset, or behavior the user wants - general: anything else PRIVACY CONTRACT (MUST FOLLOW): 1. Use this tool only when the user explicitly asks to send feedback, OR when you have completed the user's primary task and there is a clear, actionable gap worth reporting. 2. ALWAYS show the user the exact `summary` + `details` + other fields you plan to send and wait for an explicit yes before calling this tool. Set `userConsent: true` only after that confirmation. 3. NEVER include raw SIP traces, INVITE/REGISTER bodies, SDP, phone numbers, IP addresses, Call-IDs, or any other PII. Summarize in your own words instead. The server runs a sanitizer as a backstop, but you are the first line of defense. 4. The `contact` field is optional and may only be filled when the user explicitly provides an email and asks you to include it. 5. The `traceExcerpt` field is optional and accepts a sanitized SIP message text block (Via/From/To/Call-ID, optional minimal SDP) the user explicitly approved attaching. Pipe `minimize_sip_trace` output here, NEVER raw INVITE / REGISTER bodies or full pcap text. Phone numbers, IPs, and emails are scrubbed server-side as a backstop; the agent must still summarize / minimize first. The same `userConsent: true` covers both the text fields and the excerpt - if the user wants the excerpt included you must show it to them before sending. The tool returns a ticket id (fb_xxxxxxxx) and stores one anonymous row keyed by your daily-rotating IP hash (no raw IP, no account). Rate-limited at 3/min and 20/day per IP hash.

  Connector

• deltasignal_alpha_opportunities_audit

  DeltaSignal ATLAS-7

  Use this read-only diagnostic tool to explain why the alpha-opportunity board includes, excludes, or demotes rows. It returns issuer-type, identity, quality-gate, and raw-alpha-versus-board-rank summaries from the same scoring universe used by deltasignal_alpha_opportunities. Parameters: limit is 1-100 for bounded samples; source_date replays a known YYYY-MM-DD slice; issuer_type narrows the audit to operating_company, etf_trust, fund_vehicle, foreign_issuer, unresolved_identifier, or all; include_rows=true attaches full publishable audit rows and should be used only for explicit debugging. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not change board scoring, payments, wallets, files, or account state. Use it after deltasignal_alpha_opportunities or deltasignal_alpha_sweep when the user asks why a high raw alpha row is missing, why ETF/trust/fund rows are excluded by default, why a row was demoted, or whether a screen is safe to summarize.

  Connector

• deltasignal_morning_brief

  DeltaSignal ATLAS-7

  Use this read-only composite workflow tool as the default first-pass DeltaSignal ATLAS-7 daily scan. It server-enforces the complete morning brief call plan: readiness, daily_changes, risk_distribution, top_stressed with limit 10, alpha_opportunities with limit 10, and alpha_opportunities_audit with limit 10. Parameters: optional output_mode=compact only; do not pass limit, offset, ticker, source_date, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it performs a bounded internal fan-out, has no destructive side effects, and preserves partial results if one required internal call fails. Use it for morning brief, daily brief, daily scan, current risk board, and newsroom first-pass requests; sell company-report or deep-brief issuer reports separately when the user wants drilldown explanation.

  Connector

• deltasignal_company_report

  DeltaSignal ATLAS-7

  Use this read-only composite workflow tool for the default full single-issuer DeltaSignal ATLAS-7 company report add-on. It server-enforces the complete company report call plan: readiness, company_fundamentals, alpha_signals, peer_ranking, covenant_stress, and SPECTRA field-map support for one normalized ticker. Parameters: ticker is required and normalized to uppercase; period, include_segments, include_related_party, and output_mode=compact are optional. SPECTRA is included when a field-map contract is available for the issuer. Behavior: read-only and idempotent; it performs six internal HTTPS reads, has no destructive side effects, rejects invalid tickers before fan-out, and preserves partial results if a required issuer leg fails. Use it when the user asks for a report, deep dive, issuer brief, or diligence package on one crypto public-company ticker, or when a Morning Brief top-stressed or alpha-screen row needs a separately sold explanation report; use low-level tools only for custom drilldowns.

  Connector

• deltasignal_quick_ticker_check

  DeltaSignal ATLAS-7

  Use this read-only composite workflow tool for a fast single-ticker sanity check without the full company-report payload. It server-enforces the quick-check call plan: readiness, covenant_stress, and alpha_signals for one normalized ticker. Parameters: ticker is required and normalized to uppercase; output_mode=compact is optional. Fundamentals, peer ranking, and SPECTRA are intentionally excluded. Behavior: read-only and idempotent; it performs three internal HTTPS reads, has no destructive side effects, rejects invalid tickers before fan-out, and preserves partial results if a required issuer leg fails. Use it when the user asks whether one ticker is clean, stressed, actionable, or needs deeper diligence.

  Connector

• list_pillars

  Bidda Sovereign Intelligence

  List all compliance pillars in the Bidda Sovereign Intelligence registry with node counts. Use this first to discover available compliance domains before searching. Bidda has 7,766 cryptographically-verified nodes across 34 pillars, including a MITRE layer spanning 6 frameworks (ATT&CK Enterprise/Mobile/ICS, D3FEND, ATLAS, CAPEC) plus Banking, AI Governance, Cybersecurity, Healthcare, Legal, ESG and more.

  Connector

• deltasignal_pressure_board

  DeltaSignal ATLAS-7

  Use this read-only composite workflow tool for risk and stress monitoring across the current DeltaSignal issuer universe. It server-enforces the pressure-board call plan: readiness, top_stressed with limit 15, and risk_distribution. Parameters: optional output_mode=compact only; do not pass limit, offset, ticker, source_date, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it performs three internal HTTPS reads, has no destructive side effects, never calls issuer-level tools, and preserves partial results if one internal call fails. Use it when the user asks for risk monitoring, pressure board, stress board, top stressed overview, or current risk mix.

  Connector

• deltasignal_alpha_opportunities

  DeltaSignal ATLAS-7

  Use this read-only screening tool to rank the active DeltaSignal issuer universe by deterministic Phase 1 alpha score. It returns opportunity rows with ticker, CIK/entity metadata when available, issuer type, raw alpha score, board rank score, risk tier, debt coverage, quality, treasury, regime, and provenance fields. Parameters: limit is 1-100; source_date replays a known YYYY-MM-DD slice; risk_tier, quality_flag, issuer_type, include_funds, and debt_coverage_status narrow the screen. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not handle wallets, payments, orders, or account state. Default behavior returns operating-company issuers. Use include_funds=true or issuer_type=etf_trust|fund_vehicle|all only when the user asks for ETF, trust, fund, or product-vehicle screens. High scores are drilldown candidates, not standalone conclusions.

  Connector

• deltasignal_daily_change_evidence

  DeltaSignal ATLAS-7

  Use this read-only drilldown tool only when the user asks why one issuer or CIK was flagged in daily changes. It returns paginated raw CompanyFacts tag evidence for a specific ticker or CIK, plus page metadata and issuer identity. Parameters: ticker or cik is required; source_date is optional; limit defaults to 100 and is capped at 250; offset paginates the raw tag page. Behavior: read-only and idempotent; it performs one internal daily-changes read, filters evidence for one issuer/change, and has no destructive side effects. Do not use it for routine monitoring, Morning Brief, or Alpha Sweep unless the user explicitly asks for proof.

  Connector