Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Issue Agent Passports and verify agent authority before value moves. Signed verification records.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
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:
https://flint.network/mcpRun this in your terminal
claude mcp add --transport http agent-transaction-control https://flint.network/mcpPaste 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.
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:
https://flint.network/mcpMenu 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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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
The registry name was verified against the domain flint.network (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.
The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 5 months ago.
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.
In the same category: Spec Driven Development, Remote Desktop Commander, Zoo MCP
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server that provides access to the Zoo API for various CAD operations and tools.
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.
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.
This repository is the FLINT plugin for Claude Code and Cowork. It bundles two things:
https://flint.network/mcp that exposes FLINT's agent-verification tools. Nothing to run locally, no account required to start.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.
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.
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 skill runs this loop; you can also call the tools directly.
issue_agent_passport. Free, hybrid-signed, returns a public verifiable URL. Agent name or id is enough.issue_authorization_record. Binds the agent to a scope (what, how much, to whom).verify_agent_authority. Returns a four-state verdict: allow, step-up, review, or block.submit_transaction_outcome. Feeds the cross-merchant reputation signal and leaves a retained record.The connector exposes ten tools:
| Tool | Purpose |
|---|---|
issue_agent_passport | Issue a free, hybrid-signed passport for an agent; returns a public verifiable URL. |
get_agent_passport | Fetch an existing passport and its current state. |
create_flint_trust_manifest | Produce a portable trust manifest for an agent. |
generate_authorization_scope | Build a scope describing what an agent is permitted to do. |
issue_authorization_record | Bind an agent to an authorization before a spend. |
update_agent_mandate | Update the standing mandate that governs an agent's authority. |
verify_agent_authority | Verify authority and integrity at transaction time; returns the four-state verdict. |
lookup_agent_reputation | Check an agent's cross-merchant reputation before a higher-risk deal. |
submit_transaction_outcome | Record the outcome after completion, dispute, or review. |
validate_agent_commerce_readiness | Score how ready an agent or flow is to transact. |
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.
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
MIT. See LICENSE.