Connect Tech Trigger Radar to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Find technical footprints and market demand without needing an account.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

How Vinkius works: one connection, every tool, in any AI
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Complete set · 6 capabilities

The complete Tech Trigger Radar capability set.

These are the exact actions your AI can choose when you ask it to work with Tech Trigger Radar.

Capability set01 / 02

01-03

3 capabilities in this set.

Part of 6 available through Tech Trigger Radar.

  1. 01

    Search suggestions

    This capability provides the exact search terms people use to find solutions. Your agent uses these frequency-ordered phrases to mirror prospect language in subject lines and ads.

  2. 02

    Subdomain watch

    This capability monitors public certificate logs for new subdomains. It acts as a trigger for when a target launches a new product, region, or portal.

  3. 03

    Demand pulse

    This capability measures the commercial intent behind specific keywords. It tells your agent if people are searching for alternatives or pricing, which signals active buying intent.

Capability set02 / 02

04-06

3 capabilities in this set.

Part of 6 available through Tech Trigger Radar.

  1. 04

    Domain age

    This capability reads the earliest observed TLS certificate for a domain. It provides a signal for brand-new product surfaces that have just appeared in public logs.

  2. 05

    Stack fingerprint

    This capability identifies a domain's hosting and mail systems through public DNS records. It provides raw records so your agent can reason about the tech stack directly.

  3. 06

    Trending now

    This capability pulls live trending searches for a specific region. It helps your agent find timely hooks for outreach based on current regional interest.

One connector, every AI

Tech Trigger Radar works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Tech Trigger Radar to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

997ms average. Fast in production.

Tech Trigger Radar is checked daily against the live service.

Daily averagePeak 997ms
Sep 25Today
Fastest day
988ms
Slowest day
997ms
14-day trend
Stable-1%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 6 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Tech Trigger Radar, so you can see the experience inside your AI.

It does not authenticate your account with Tech Trigger Radar. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Tech Trigger Radar Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_Ld0WCED3FBMsrpisFV4yBiADVDxipB8tDNOgJb0c/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Tech Trigger Radar capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "tech-trigger-radar-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_Ld0WCED3FBMsrpisFV4yBiADVDxipB8tDNOgJb0c/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? How to give Claude access to Tech Trigger Radar

See all the AI clients this connector works with ↑

Who it's for

Built for the work Tech Trigger Radar owners hand off.

This MCP is built for teams that rely on technical signals and market demand to drive their outbound efforts.

  • 01

    Outbound SDRs

    They hand off the task of finding new product launches and technical triggers to the agent.

  • 02

    Founders

    They use the demand pulse and trending data to validate market interest and timing.

  • 03

    Growth Marketers

    They use search suggestion data to craft high-converting ad copy and subject lines.

FAQ

Questions Tech Trigger Radar owners ask.

  • 01

    Do I need to create an account for the data sources?

    No. This MCP uses public certificate logs, DNS, and autocomplete endpoints that require no keys or accounts.

  • 02

    How accurate is the tech stack detection?

    The stack fingerprinting uses heuristics based on published DNS records. It provides the raw records so your agent can perform its own reasoning.

  • 03

    Is the subdomain data the exact launch date?

    No. The dates represent the first time a certificate was observed in the public log, which serves as a proxy for a new launch.

  • 04

    What happens if a data source is unavailable?

    If a source is rate-limited or slow, the MCP returns a message stating the source is unavailable. It will not return empty results that could be mistaken for a lack of data.

  • 05

    Can I use this with Claude or Cursor?

    Yes. This MCP works with any MCP-compatible client, including Claude, Cursor, and Windsurf.

  • 06

    Do I need an API key or an account?

    No. Every source is public: the certificate-transparency log, public DNS, the public autocomplete endpoint and the public trending feed. There is no credential anywhere in the chain. nothing to issue, rotate or store.

  • 07

    What exactly is a "new subdomain" signal?

    Every website that serves HTTPS issues a public certificate, and every certificate is recorded in the public transparency log. A subdomain whose certificate first appears inside your window is new public surface: a new product, region, portal or integration. The capability returns them newest first with their first-observed date. and says plainly that the date is an observation, not the exact deploy time.

  • 08

    Is the stack fingerprint a fact about the company?

    No. it is a labelled heuristic. The engine matches the domain's own published DNS records (CNAME, MX, TXT) against known provider patterns, so each detection means "very likely this provider", never "confirmed". Use it for targeting language. "you run X, we do Y". and lean on the raw records in the result when you want to reason further.

  • 09

    What happens when a source is slow or rate-limited?

    Certificate readings are cached for an hour, so repeating a scan minutes apart is free. When a source does not answer, the result carries an explicit "source unavailable" flag and a note to retry in a few minutes. it is never reported as "no data", because an unavailable reading and a genuine negative are different facts and mixing them up would mislead the outreach.

Connect Tech Trigger Radar to Claude, Cursor, ChatGPT & more