An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Stack Testing Protocol Designer to your AI

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. Automate your emission testing protocol design and EPA compliance.

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.

A futuristic MCP client docking bay
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.

Curated set · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Stack Testing Protocol.

  1. 01

    Determine test duration

    Calculates the minimum time you need to run a test to hit your target mass.

  2. 02

    Get sampling strategy

    Finds the best vertical location within a stack for sampling.

  3. 03

    Validate protocol compliance

    Checks your proposed testing protocol against specific regulatory requirements.

  4. 04

    Calculate traverse points

    Determines the exact number and placement of sampling points across the stack diameter.

Real work

What teams actually run

01

Protocol Generation

Create a full testing plan by providing stack diameter and upstream disturbance data.

02

Field Setup Planning

Get the exact number of traverse points needed before arriving at the stack.

03

Compliance Auditing

Run a proposed protocol through the validation capability to check for regulatory gaps.

04

Resource Scheduling

Use the duration capability to estimate how much time a crew needs on site for a specific test.

One connector, every AI

Stack Testing Protocol 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.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

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

You don't need a client to put Stack Testing Protocol 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

870ms average. Fast in production.

Stack Testing Protocol is checked daily against the live service.

Daily averagePeak 1035ms
Oct 3Today
Fastest day
654ms
Slowest day
1035ms
14-day trend
Slowing+19%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 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 Stack Testing Protocol, so you can see the experience inside your AI.

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

Stack Testing Protocol Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_8bGLZqKp6u5l9Y4rM1ySbRYOA5FyHWky3hh6SmwT/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 — Stack Testing Protocol capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "stack-testing-protocol-designer-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_8bGLZqKp6u5l9Y4rM1ySbRYOA5FyHWky3hh6SmwT/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? Set up Stack Testing Protocol in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Stack Testing Protocol owners hand off.

This MCP is built for environmental professionals who need to generate accurate, compliant testing plans quickly.

  • 01

    Environmental Engineers

    They hand off stack dimensions and target parameters to the AI to generate protocols.

  • 02

    Field Technicians

    They use the calculated traverse points and sampling locations to set up equipment.

  • 03

    Compliance Officers

    They use the validation capability to double check that protocols meet EPA standards.

FAQ

Questions Stack Testing Protocol owners ask.

  • 01

    Does this MCP follow EPA standards?

    Yes, the capabilities are designed to ensure protocols meet EPA standards for isokinetic sampling and flow profiles.

  • 02

    Can I use this with Claude or Cursor?

    Yes, you can connect this MCP to any MCP-compatible client like Claude, Cursor, or Windsurf.

  • 03

    What kind of stack data do I need to provide?

    You typically need to provide stack diameter, upstream disturbance distances, target mass, and flow rates.

  • 04

    How does it handle traverse points?

    The calculate_traverse_points capability determines both the number of points and their specific locations across the stack diameter.

  • 05

    Can it help with field scheduling?

    Yes, by using the determine_test_duration capability, you can find the minimum time required to complete a test.

  • 06

    How does the capability ensure isokinetic compliance?

    The calculate_traverse_points capability specifically accounts for isokinetic requirements to ensure the sampling nozzle velocity matches the stack gas velocity.

  • 07

    Can I validate my protocol against EPA Method 5?

    Yes, you can use validate_protocol_compliance to check your calculated parameters against specific EPA Method IDs.

  • 08

    What inputs are needed for sampling location?

    To use get_sampling_strategy, you need the stack diameter and the distances to the nearest upstream and downstream disturbances.

Explore

More in Engineering

Suggestions

Connect Stack Testing Protocol to Claude, Cursor, ChatGPT & more