"radarr" matching MCP tools:

• create_certificate

  TLS Radar

  Start issuing a FREE 90-day Let's Encrypt certificate for a domain (no account required). Step 1 of 3. Pick a validation method with `challenge`: "dns-01" (default; publish a TXT record; covers apex + www) or "http-01" (serve a file over HTTP on port 80; issues the exact domain only). dns-01 with a DNS-provider API token is the most automatable; http-01 suits a server you control on port 80. Returns an order_id plus either dns_records (dns-01) or http_files (http-01) to put in place. Next: poll `check_certificate_propagation` until all_found, then call `finalize_certificate`. Strongly prefer the CSR path at finalize (the private key never leaves the user's machine). Issuing automatically offers the user ongoing monitoring by email once it completes - don't add a monitor manually afterward.

  Connector

• finalize_certificate

  TLS Radar

  Finalize and issue a certificate order in one call: validates the DNS challenges, waits for Let's Encrypt, and returns the issued cert. Step 3 of issuance - call after check_certificate_propagation reports all_found. STRONGLY PREFER passing csr_pem (generate the key + CSR locally with openssl so the private key never leaves the machine). Returns leaf_pem/chain_pem/fullchain_pem. If you must, pass a passphrase instead to get a PKCS#12 bundle - but a CSR is safer. If it replies "still validating", DNS hasn't fully propagated: re-check check_certificate_propagation and call again. Needs a locally-generated CSR (csr_pem) - requires a local shell with openssl. On a surface without one (e.g. a Claude.ai custom connector) this can't complete; it returns guidance to finish in Claude Code/Cowork or the web form. Scanning and monitoring work everywhere. On success the structuredContent carries a `handoff` object - relay `handoff.message` to the user and do NOT separately call add_monitor; the cert→monitoring handoff is automatic and server-side.

  Connector

• renew_certificate

  TLS Radar

  Renew a certificate by cloning a recent order (requires the original order_id; Beacon purges orders after ~24h). Returns a new order_id and fresh DNS TXT records - then poll check_certificate_propagation and call finalize_certificate. If you don't have an order_id (the usual case at 90-day renewal time), call create_certificate for the domain instead; that IS the renewal.

  Connector

• add_monitor

  TLS Radar

  Add a domain to ongoing certificate monitoring with expiry alerts. Requires authentication (the user runs /mcp once). If the plan's monitor limit is reached, the response's structuredContent carries a limit-reached payload - when relaying it, LEAD with `recommended_upgrade` (typically Starter, $9.99/mo), mention `also_available` tiers in a single closing line, and offer removing an existing monitor as the free alternative. Don't dump a full tier comparison; that's choice paralysis at the moment of action.

  Connector

• evidence_india

  LiquiLens — the Failure Radar

  Read the full Indian crisis record: 48 institutions replayed point-in-time from vetted public filings across two decades, with per-institution verdicts, lead times in months, uncertainty intervals and the rigor artifacts — misses and false alarms included, never trimmed. Takes no arguments. Use evidence_institution for one institution's complete replay.

  Connector

• evidence_europe

  LiquiLens — the Failure Radar

  Read the seven European case files replayed point-in-time through the unrecalibrated Indian lenses: Credit Suisse, Banco Popular, Northern Rock and Banco Espirito Santo (failed); Deutsche Bank and Monte dei Paschi (stressed survivors); UBS (control). Every figure is audited against the primary filing it cites. Without arguments, returns all seven verdict summaries; pass slug for one full case file with its per-quarter table. These are case studies with citations, deliberately not a cohort — there is no European recall percentage to quote.

  Connector

• incumbent_lookup

  PubSec Radar

  Use this to answer "who am I displacing and when?": a vendor name (plus optional agency scope) returns their current and recent awards with values and end dates, flagging awards that end within 12 months as displacement windows. Good queries use the vendor's registered name or a distinctive fragment, e.g. vendor="Booz Allen", agency="DHS". Federal only. Zero results ≠ no presence — check the caveats for name-matching tips.

  Connector

• register_beacon_order

  TLS Radar

  OBSOLETE - do not call. The cert→monitoring handoff is server-side now (issue via create_certificate, which records the order itself). This tool is kept only so old plugin versions that still call it don't error; it remains idempotent and harmless.

  Connector

• export_monitors

  TLS Radar

  Dump the user's monitors as a JSON structure suitable for backup, migration, or infrastructure-as-code workflows. Tokens and PII are NEVER included - only domain configuration.

  Connector

• agency_spend_profile

  PubSec Radar

  Use this to answer "what does this agency actually buy, and from whom?" before a first call: total contract obligations, 3-year trend, top 10 vendors, and top 10 NAICS categories for one fiscal year. Good queries name one agency, e.g. agency="HHS". Figures come from a daily snapshot of USAspending covering the current fiscal year plus a 3-year trend; freshness is stated in the response. Federal only. Read the coverage caveats — current-FY totals are partial-year and intel-agency spend is never published.

  Connector

• failure_radar_institution

  LiquiLens — the Failure Radar

  Read the full radar dossier for one Indian institution: per-quarter score and failure-PD trajectory with named drivers, RBI PCA/SAF headroom history, the funding-fragility read, forensic-screen evidence, and the market reading for listed names. Call failure_radar_board first to discover valid slugs; an institution without a vetted dossier is reported absent, never scored from memory.

  Connector

• evidence_markets

  LiquiLens — the Failure Radar

  Read the validation record's headline for each market: India (48-institution point-in-time backtest), United States (industry-wide watchlist backtest over 550 failures), and Europe (named audited case files, deliberately no cohort claim). Takes no arguments. Start here when asked whether LiquiLens is validated, then drill into evidence_india, evidence_us or evidence_europe for the full record behind each headline.

  Connector

• rbi_supervisory_tape

  LiquiLens — the Failure Radar

  Read the latest RBI enforcement and supervisory actions — monetary penalties, licence cancellations and supervisory directions — parsed from rbi.org.in press releases, newest first, each item carrying the RBI's own source URL. Takes no arguments. When no tape snapshot exists on the deployment, says so in a stated note instead of returning silent emptiness.

  Connector

• get_obligation

  compliance-radar

  Return full detail for a single obligation by id: what it is, who must file, the deadline, the penalty for missing it, and a link to the OFFICIAL government source with a dated 'verified as of'. INFORMATIONAL ONLY — not legal or tax advice.

  Connector

• get_certificate_status

  TLS Radar

  Return the current state of a certificate order (dns_pending, validating, ready, completed, failed) and per-authorization Let's Encrypt statuses. Use it to resume an interrupted issuance.

  Connector

• get_account

  TLS Radar

  Return the current user's plan, limits, and usage so the client can render upgrade nudges proactively.

  Connector

• import_monitors

  TLS Radar

  Create monitors from a JSON structure (typically produced by `export`). Skips domains the user is already monitoring; honors the plan's domain limit. Returns a per-domain status.

  Connector

• failure_radar_board

  LiquiLens — the Failure Radar

  Read the live Failure Radar board for India: one row per institution with a fresh vetted dossier — banks, small finance banks, co-operative banks, NBFCs, MFIs and HFCs. Each row carries a corpus-calibrated failure PD term structure (12/24/36 months), a disclosure score, RBI PCA/SAF action-zone status, a funding-fragility index, market-implied distance-to-default for listed names, and a watchlist tier assigned under a published rule. Takes no arguments. Call this first to discover institution slugs, then failure_radar_institution for one name's full dossier. Outputs are research screens, not credit ratings.

  Connector

• verify_published_record

  LiquiLens — the Failure Radar

  Independently verify the as-published record for a ledger stream: recompute the hash-chained point-in-time commitments, check signatures and anchors where enabled, server-side, and return the verifier's verdict verbatim — even when unflattering; that is the point. Use this to check whether the published early-warning track record is tamper-evident and intact.

  Connector

• find_expiring_contracts

  PubSec Radar

  Use this when prospecting or prepping a federal account and you want sales triggers: contracts at an agency that end soon, with the incumbent vendor, dollar values, and contracting office. Expiring contracts mean upcoming recompetes — the best time to displace an incumbent. Good queries name one agency and optionally a NAICS code, e.g. agency="DHS", naics_code="541512", window_days=90. Federal only (no state/local). Every response includes data-freshness and coverage caveats — read them; no data ≠ no spend.

  Connector