Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Agent Transaction Control

by thefraudfatherversion 0.2.1i★ –iRuns in the cloud
Registry namenetwork.flint/agent-transaction-control

Install

Overview

Description from the maker (original English)

Issue Agent Passports and verify agent authority before value moves. Signed verification records.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://flint.network/mcp

Run this in your terminal

claude mcp add --transport http agent-transaction-control https://flint.network/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-transaction-control": {
      "url": "https://flint.network/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agent-transaction-control": {
      "type": "http",
      "url": "https://flint.network/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://flint.network/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain flint.network (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32497 servers in this category
  • Published to the registry more recently than 14% of the other 32497 servers in this category
  • Basic checks equal to or better than 100% of the other 32497 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Agent Transaction Control safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Zoo MCP

by KittyCAD

An MCP server that provides access to the Zoo API for various CAD operations and tools.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

FLINT Cross-Domain Agent Passport

Know Your Agent at transaction time. Verify an AI agent's integrity and authority with FLINT before it moves money, and keep a signed record of what was checked.


What this is

This repository is the FLINT plugin for Claude Code and Cowork. It bundles two things:

  1. The FLINT remote connector — a hosted MCP server at https://flint.network/mcp that exposes FLINT's agent-verification tools. Nothing to run locally, no account required to start.
  2. The `verify-agent-integrity` skill — a guided workflow that runs the verify-before-pay loop for you, so the assistant confirms an agent is authorized and uncompromised before it spends.

FLINT is the neutral verification network for AI agents that transact. It does not issue agents and it does not move money. It verifies, at the moment value moves, that the specific agent asking to pay is the one it claims to be, is still inside the authority it was granted, and has not been taken over. Every check returns a clear verdict and a signed record the counterparty keeps as evidence.

Why it exists

AI agents are being handed spending authority across stablecoin and card rails. The fraud and identity stack was built for humans: a device, a session, an account the institution itself issued and could watch. An agent transacting directly against an API has none of that, and the counterparty it transacts with did not issue it. Proving the human is real does not tell you the agent acting for them right now is authorized and uncompromised. That is the layer FLINT verifies.

Install

As a plugin (Claude Code or Cowork):

/plugin marketplace add thefraudfather/flint-plugin

/plugin install flint@flint-network

This installs both the remote connector and the verify-agent-integrity skill.

Connector only (any MCP-compatible client):

Point your client at the FLINT remote server. The connection is a single entry:

{

"mcpServers": { "flint": { "type": "streamable-http", "url": "https://flint.network/mcp" } } }

Or connect from flint.network/connect.

The verify-before-pay loop

The skill runs this loop; you can also call the tools directly.

  1. Issue a passport for the agent — issue_agent_passport. Free, hybrid-signed, returns a public verifiable URL. Agent name or id is enough.
  2. Authorize the intended action before any spend — issue_authorization_record. Binds the agent to a scope (what, how much, to whom).
  3. Verify at the moment of execution — verify_agent_authority. Returns a four-state verdict: allow, step-up, review, or block.
  4. Record the result after completion, dispute, or review — submit_transaction_outcome. Feeds the cross-merchant reputation signal and leaves a retained record.

Tools

The connector exposes ten tools:

ToolPurpose
issue_agent_passportIssue a free, hybrid-signed passport for an agent; returns a public verifiable URL.
get_agent_passportFetch an existing passport and its current state.
create_flint_trust_manifestProduce a portable trust manifest for an agent.
generate_authorization_scopeBuild a scope describing what an agent is permitted to do.
issue_authorization_recordBind an agent to an authorization before a spend.
update_agent_mandateUpdate the standing mandate that governs an agent's authority.
verify_agent_authorityVerify authority and integrity at transaction time; returns the four-state verdict.
lookup_agent_reputationCheck an agent's cross-merchant reputation before a higher-risk deal.
submit_transaction_outcomeRecord the outcome after completion, dispute, or review.
validate_agent_commerce_readinessScore how ready an agent or flow is to transact.

How verification works

At the transaction handshake, FLINT runs six locked verification layers:

Principal Identity (the human or organization the agent acts for), Agent Identity (the specific agent it claims to be), Wallet Provenance (the funding source is what it should be), Authorization Scope (the action falls inside the authority granted), Environment Identity (the agent is running where its history says it runs), and Cross-Merchant Reputation (how the agent has behaved across the network).

Each verification returns one of four verdicts — allow, step-up, review, block — and a signed verification record. Records are hybrid-signed with both a classical and a post-quantum signature, so the evidence holds as cryptography evolves.

Learn more

About

FLINT is built by KillChain, Inc. (d/b/a FLINT Network). FLINT is rail-agnostic and neutral by design: it verifies the agent so identity providers can keep proving the human and the rails can keep moving the money.

Questions or partnership: contact@flint.network

License

MIT. See LICENSE.

Ask PopNx