Enhanced MCP server for Limitless Pendant with advanced conversation analysis, meeting detection, action item extraction, and comprehensive
Free
Nothing to run from here
Stx402 Agent is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
DEPRECATED: This package has moved to @aibtc/mcp-server. Run: npx @aibtc/mcp-server@latest --install
Quickstart
# 1 — run it from where its publisher ships it
npx -y stx402-agent
# 2 — ask your agent something
> DEPRECATED: This package has moved to @aibtc/mcp-server. Run: npx @aibtc/mcp-server@latest --install
Stx402 Agent is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
AIAll 2 servers
aibtcdev2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Stx402 Agent as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add stx402-agent-mcp -- npx -y stx402-agentReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
175 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Connect to your Pillar smart wallet. Opens the Pillar website - if you
Takes no parameters.
Example callreturns →
Disconnect from Pillar. Clears locally stored wallet address.
Takes no parameters.
Example callreturns →
Check if you
Takes no parameters.
Example callreturns →
Send sBTC from your Pillar smart wallet. Requires being connected first (use pillar_connect).
Takes no parameters.
Example callreturns →
Fund your Pillar smart wallet. Supports multiple methods:\n
Takes no parameters.
Example callreturns →
Add a backup admin address to your Pillar smart wallet for recovery purposes.
Takes no parameters.
Example callreturns →
Earn yield on your Bitcoin. Supply sBTC from your Pillar smart wallet to Zest Protocol.
Takes no parameters.
Example callreturns →
Configure auto-compound for your Pillar wallet.
Takes no parameters.
Example callreturns →
Close or reduce your leveraged sBTC position.
Takes no parameters.
Example callreturns →
Create or increase a leveraged sBTC position (up to 1.5x) on your Pillar smart wallet.
Takes no parameters.
Example callreturns →
View your Pillar wallet balance and Zest position.
Takes no parameters.
Example callreturns →
Create a new Pillar smart wallet. Opens the Pillar website to complete registration.
Takes no parameters.
Example callreturns →
Get your Pillar referral link to invite friends. Share this link and earn rewards when friends sign up.
Takes no parameters.
Example callreturns →
Invite a DCA partner by email or wallet address.
Takes no parameters.
Example callreturns →
View your DCA partners and weekly status.
Takes no parameters.
Example callreturns →
View the DCA streak leaderboard. Shows top partnerships by streak length, and highlights your entry if you have one.
Takes no parameters.
Example callreturns →
Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress
Takes no parameters.
Example callreturns →
Generate a new secp256k1 signing keypair for Pillar smart wallet direct operations.
Takes no parameters.
Example callreturns →
Unlock a signing key for Pillar direct operations.
Takes no parameters.
Example callreturns →
Lock the signing key, clearing sensitive data from memory.
Takes no parameters.
Example callreturns →
Show signing key info: pubkey, smart wallet, lock status, and all stored keys.
Takes no parameters.
Example callreturns →
Create or increase a leveraged sBTC position (up to 1.5x) on your Pillar smart wallet.
Takes no parameters.
Example callreturns →
Close or reduce your leveraged sBTC position. Agent-signed, no browser needed.
Takes no parameters.
Example callreturns →
Earn yield on your Bitcoin. Supply sBTC from your Pillar smart wallet to Zest Protocol.
Takes no parameters.
Example callreturns →
Send sBTC from your Pillar smart wallet to a recipient.
Takes no parameters.
Example callreturns →
Configure auto-compound for your Pillar wallet.
Takes no parameters.
Example callreturns →
View your Pillar smart wallet balances (STX, sBTC, aeUSDC) and Zest position.
Takes no parameters.
Example callreturns →
Withdraw sBTC collateral from Zest on the Pillar smart wallet.
Takes no parameters.
Example callreturns →
Add a backup admin address to your Pillar smart wallet for recovery purposes.
Takes no parameters.
Example callreturns →
Create a new Pillar smart wallet for agent direct operations.
Takes no parameters.
Example callreturns →
Invite a DCA partner by email or wallet address.
Takes no parameters.
Example callreturns →
View your DCA partners and weekly status.
Takes no parameters.
Example callreturns →
View the DCA streak leaderboard. Shows top partnerships by streak length, and highlights your entry if you have one.
Takes no parameters.
Example callreturns →
Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress
Takes no parameters.
Example callreturns →
Get a boost quote showing projected leverage, LTV, and swap details.
Takes no parameters.
Example callreturns →
Resolve a recipient before sending. Resolves BNS names (.btc) via backend,
Takes no parameters.
Example callreturns →
Stack STX from your Pillar smart wallet via Fast Pool or Stacking DAO.
Takes no parameters.
Example callreturns →
Revoke Fast Pool STX delegation from your Pillar smart wallet.
Takes no parameters.
Example callreturns →
Check stacking status for your Pillar smart wallet.
Takes no parameters.
Example callreturns →
Sign structured Clarity data using SIP-018 standard.
Takes no parameters.
Example callreturns →
Verify a SIP-018 signature and recover the signer
Takes no parameters.
Example callreturns →
Compute the SIP-018 message hash without signing.
Takes no parameters.
Example callreturns →
Sign a plain text message using the Stacks message signing format.
Takes no parameters.
Example callreturns →
Verify a Stacks message signature and recover the signer
Takes no parameters.
Example callreturns →
Sign a plain text message using Bitcoin message signing.
Takes no parameters.
Example callreturns →
Verify a Bitcoin message signature (BIP-137 or BIP-322) and recover or confirm the signer.
Takes no parameters.
Example callreturns →
Sign a raw 32-byte digest with Schnorr (BIP-340) using the wallet
Takes no parameters.
Example callreturns →
Verify a BIP-340 Schnorr signature over a 32-byte digest.
Takes no parameters.
Example callreturns →
Sign a Nostr event (NIP-01) using BIP-340 Schnorr.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Stop autonomous yield hunting. Stops the background process that monitors and deposits sBTC. Your existing Zest positions remain untouched.
Takes no parameters.
Example callreturns →
Get current yield hunter status. Shows: - Whether yield hunting is active - Current configuration - Statistics (checks run, deposits made) - Recent activity logs - Current Zest position
Takes no parameters.
Example callreturns →
Configure yield hunter settings. Adjust the deposit threshold, reserve, or check interval. Changes take effect on the next check cycle.
Takes no parameters.
Example callreturns →
Get the BTC balance for a Bitcoin address.
Takes no parameters.
Example callreturns →
Get current Bitcoin fee estimates for different confirmation targets.
Takes no parameters.
Example callreturns →
List all UTXOs (Unspent Transaction Outputs) for a Bitcoin address.
Takes no parameters.
Example callreturns →
Transfer BTC to a recipient address.
Takes no parameters.
Example callreturns →
Get cardinal UTXOs (safe to spend - no inscriptions or runes).
Takes no parameters.
Example callreturns →
Get ordinal UTXOs (contain inscriptions or runes - do not spend).
Takes no parameters.
Example callreturns →
Get all inscriptions owned by a Bitcoin address.
Takes no parameters.
Example callreturns →
Get market ticker data from Bitflow DEX. Returns price, volume, and liquidity data for all trading pairs. This endpoint does NOT require an API key. Note: Bitflow is only available on mainnet.
Takes no parameters.
Example callreturns →
Get all available tokens for swapping on Bitflow. Returns the list of tokens that can be swapped on Bitflow DEX. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
Takes no parameters.
Example callreturns →
Get possible swap target tokens for a given input token on Bitflow. Returns all tokens that can be received when swapping from the specified token. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
Takes no parameters.
Example callreturns →
Get a swap quote from Bitflow DEX. Returns the expected output amount and best route for swapping tokens. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
Takes no parameters.
Example callreturns →
Get all possible swap routes between two tokens on Bitflow. Returns all available routes for swapping from tokenX to tokenY, including multi-hop routes through intermediate tokens. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
Takes no parameters.
Example callreturns →
Execute a token swap on Bitflow DEX. Swaps tokenX for tokenY using Bitflow
Takes no parameters.
Example callreturns →
Get or create a Bitflow Keeper contract for automated swaps. Keeper contracts enable scheduled/automated token swaps. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
Takes no parameters.
Example callreturns →
Create an automated swap order via Bitflow Keeper. Creates a pending order that will be executed by the Keeper service. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
Takes no parameters.
Example callreturns →
Get details of a Bitflow Keeper order. Retrieves the status and details of a specific order. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
Takes no parameters.
Example callreturns →
Cancel a Bitflow Keeper order. Cancels a pending order before execution. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
Takes no parameters.
Example callreturns →
Get Bitflow Keeper user info and orders. Retrieves user
Takes no parameters.
Example callreturns →
Resolve a .btc domain name to its Stacks address.
Takes no parameters.
Example callreturns →
Get the BNS domain names owned by an address.
Takes no parameters.
Example callreturns →
Get detailed information about a BNS domain name.
Takes no parameters.
Example callreturns →
Check if a BNS domain name is available for registration.
Takes no parameters.
Example callreturns →
Get the registration price for a BNS domain name.
Takes no parameters.
Example callreturns →
List all BNS domains owned by an address.
Takes no parameters.
Example callreturns →
Register a BNS domain name in a single transaction using name-claim-fast.
Takes no parameters.
Example callreturns →
Preorder a BNS domain name (step 1 of 2-step registration).
Takes no parameters.
Example callreturns →
Register a BNS domain name after preorder is confirmed. This is step 2 of a 2-step process.
Takes no parameters.
Example callreturns →
Call a function on a Stacks smart contract. Signs and broadcasts the transaction. For typed arguments, use objects like {type:
Takes no parameters.
Example callreturns →
Deploy a Clarity smart contract to the Stacks blockchain.
Takes no parameters.
Example callreturns →
Check the status of a Stacks transaction by its txid.
Takes no parameters.
Example callreturns →
Call a read-only function on a smart contract (no signing required).
Takes no parameters.
Example callreturns →
Get a swap quote from ALEX DEX. Returns the expected output amount for swapping tokenX to tokenY. Use full contract IDs for tokens (e.g.,
Takes no parameters.
Example callreturns →
Execute a token swap on ALEX DEX. Swaps tokenX for tokenY using the ALEX AMM. Use full contract IDs for tokens. Note: ALEX DEX is only available on mainnet.
Takes no parameters.
Example callreturns →
Get liquidity pool information from ALEX DEX. Returns reserve balances and pool details for a token pair. Note: ALEX DEX is only available on mainnet.
Takes no parameters.
Example callreturns →
List all available trading pools on ALEX DEX. Discovers all token pairs that can be swapped directly. Returns pool ID, token pair, and factor (fee tier) for each pool. Use this to find which tokens can be swapped before calling alex_swap. Note: ALEX DEX is only available on mainnet.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Get user
Takes no parameters.
Example callreturns →
Supply assets to Zest Protocol (v0-4-market). Deposits assets and adds them as collateral in one atomic operation. The supplied assets earn yield AND provide borrowing power. You can use the asset symbol (e.g.,
Takes no parameters.
Example callreturns →
Withdraw assets from Zest Protocol (v0-4-market). Removes collateral and redeems for underlying assets in one atomic operation. You can use the asset symbol (e.g.,
Takes no parameters.
Example callreturns →
Borrow assets from Zest Protocol (v0-4-market). Borrows assets against your supplied collateral. Ensure you have sufficient collateral to maintain a healthy LTV. You can use the asset symbol (e.g.,
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Repay borrowed assets to Zest Protocol (v0-4-market). Repays borrowed assets plus accrued interest. You can use the asset symbol (e.g.,
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Execute an x402 API endpoint. Payment is handled automatically. Supported sources: - x402.biwas.xyz (default): Use path like
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Register a new agent identity on-chain using ERC-8004 identity registry.
Takes no parameters.
Example callreturns →
Get agent identity information from ERC-8004 identity registry.
Takes no parameters.
Example callreturns →
Submit feedback for an agent using ERC-8004 reputation registry.
Takes no parameters.
Example callreturns →
Get aggregated reputation summary for an agent from ERC-8004 reputation registry.
Takes no parameters.
Example callreturns →
Request third-party validation for an agent using ERC-8004 validation registry.
Takes no parameters.
Example callreturns →
Get the status of a validation request using ERC-8004 validation registry.
Takes no parameters.
Example callreturns →
Get validation summary for an agent using ERC-8004 validation registry.
Takes no parameters.
Example callreturns →
⛔ DEPRECATED — do not use. The sponsored (relay) inbox send has been removed.
Takes no parameters.
Example callreturns →
List all NFTs owned by an address.
Takes no parameters.
Example callreturns →
Get metadata for a specific NFT (SIP-016).
Takes no parameters.
Example callreturns →
Transfer an NFT (SIP-009) to a recipient address.
Takes no parameters.
Example callreturns →
Get the current owner of a specific NFT.
Takes no parameters.
Example callreturns →
Get information about an NFT collection.
Takes no parameters.
Example callreturns →
Get the transfer history of NFTs in a collection.
Takes no parameters.
Example callreturns →
Get the current weather in a location
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Get list of popular OpenRouter models with capabilities and context lengths. Use this to choose the right model for your use case. For latest pricing, check openrouter.ai/models
Takes no parameters.
Example callreturns →
Get the current weather in a location
Takes no parameters.
Example callreturns →
Get the current weather in a location
Takes no parameters.
Example callreturns →
Get the wallet
Takes no parameters.
Example callreturns →
Calculate the total cost (in satoshis) for creating an inscription.
Takes no parameters.
Example callreturns →
Create a Bitcoin inscription - STEP 1: Broadcast commit transaction.\n\n
Takes no parameters.
Example callreturns →
Complete a Bitcoin inscription - STEP 2: Broadcast reveal transaction.\n\n
Takes no parameters.
Example callreturns →
Get inscription content from a Bitcoin reveal transaction.
Takes no parameters.
Example callreturns →
Get current STX fee estimates for different priority levels.
Takes no parameters.
Example callreturns →
Get detailed account information including nonce and balance.
Takes no parameters.
Example callreturns →
Get transaction history for an account.
Takes no parameters.
Example callreturns →
Get information about a specific block.
Takes no parameters.
Example callreturns →
Get pending transactions in the mempool.
Takes no parameters.
Example callreturns →
Get information about a smart contract including its ABI.
Takes no parameters.
Example callreturns →
Get events emitted by a smart contract.
Takes no parameters.
Example callreturns →
Get the current status of the Stacks network.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Get the sBTC balance for a wallet address.
Takes no parameters.
Example callreturns →
Transfer sBTC tokens to a recipient address. sBTC uses 8 decimals (same as Bitcoin). Example: To send 0.001 sBTC, use amount
Takes no parameters.
Example callreturns →
Initiate an sBTC peg-out to a Bitcoin L1 address. Locks (amount + maxFee) of sBTC in the sBTC protocol and creates a withdrawal request. Signers later process the request and send BTC on L1.
Takes no parameters.
Example callreturns →
Alias for sbtc_initiate_withdrawal. Initiates an sBTC peg-out request to BTC L1.
Takes no parameters.
Example callreturns →
Check status of an sBTC withdrawal request by requestId or initiating txid.
Takes no parameters.
Example callreturns →
Alias for sbtc_withdrawal_status. Check the status of an sBTC peg-out (withdrawal) request.
Takes no parameters.
Example callreturns →
Get information about how to deposit BTC to receive sBTC.
Takes no parameters.
Example callreturns →
Get sBTC peg information including total supply and peg ratio.
Takes no parameters.
Example callreturns →
Deposit BTC to receive sBTC on Stacks L2. This builds, signs, and broadcasts a Bitcoin transaction to the sBTC deposit address. After confirmation, sBTC tokens are minted to your Stacks address. The transaction uses your wallet
Takes no parameters.
Example callreturns →
Check the status of an sBTC deposit transaction from Emily API.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Save a Hiro API key to ~/.aibtc/config.json for authenticated Hiro API requests. Authenticated requests get higher rate limits than public (unauthenticated) requests. Get a free API key at https://platform.hiro.so/
Takes no parameters.
Example callreturns →
Check whether a Hiro API key is configured. Shows the key source (stored file or environment variable) and a masked preview.
Takes no parameters.
Example callreturns →
Remove the stored Hiro API key from ~/.aibtc/config.json. If HIRO_API_KEY is set in the environment, that will still be used as a fallback.
Takes no parameters.
Example callreturns →
Point all Stacks API requests at a custom node instead of the default Hiro API. Use this if you run your own stacks-blockchain-api node (default port 3999) or use a third-party provider. The URL should serve the same /v2/ and /extended/v1/ endpoints as api.hiro.so. Example: http://localhost:3999
Takes no parameters.
Example callreturns →
Show the current Stacks API URL being used for blockchain queries. Indicates whether it
Takes no parameters.
Example callreturns →
Remove the custom Stacks API URL and revert to the default Hiro API (api.mainnet.hiro.so or api.testnet.hiro.so).
Takes no parameters.
Example callreturns →
Check the currently running MCP server version and compare with the latest published version on npm. Use this to detect if you
Takes no parameters.
Example callreturns →
Get current Proof of Transfer (PoX) cycle information.
Takes no parameters.
Example callreturns →
Check if an address is currently stacking STX.
Takes no parameters.
Example callreturns →
Lock STX for stacking to earn BTC rewards. Requires a Bitcoin address (hash) for receiving rewards.
Takes no parameters.
Example callreturns →
Extend an existing stacking lock period.
Takes no parameters.
Example callreturns →
Get the balance of any SIP-010 token for a wallet address. Supports well-known tokens by symbol: sBTC, USDCx, ALEX, DIKO Or use the full contract ID: address.contract-name
Takes no parameters.
Example callreturns →
Transfer any SIP-010 token to a recipient address. Supports well-known tokens by symbol: sBTC, USDCx, ALEX, DIKO Or use the full contract ID.
Takes no parameters.
Example callreturns →
Get metadata for a SIP-010 token (name, symbol, decimals, supply).
Takes no parameters.
Example callreturns →
List all fungible tokens owned by an address.
Takes no parameters.
Example callreturns →
Get the top holders of a SIP-010 token.
Takes no parameters.
Example callreturns →
Transfer STX tokens to a recipient address. Signs and broadcasts the transaction. Example: To send 2 STX, use amount
Takes no parameters.
Example callreturns →
Broadcast a pre-signed Stacks transaction to the network.
Takes no parameters.
Example callreturns →
Get the agent
Takes no parameters.
Example callreturns →
Get the STX balance for a wallet address.
Takes no parameters.
Example callreturns →
Create a new wallet for the agent with a generated BIP39 24-word mnemonic. The wallet is encrypted locally and stored in ~/.aibtc/. IMPORTANT: Save the mnemonic securely - it will only be shown once!
Takes no parameters.
Example callreturns →
Import an existing wallet for the agent using a BIP39 mnemonic phrase. The wallet is encrypted locally and stored in ~/.aibtc/.
Takes no parameters.
Example callreturns →
Unlock the agent
Takes no parameters.
Example callreturns →
Lock the agent
Takes no parameters.
Example callreturns →
List all wallets available for the agent to use.
Takes no parameters.
Example callreturns →
Switch to a different wallet. Note: The new wallet will need to be unlocked before use.
Takes no parameters.
Example callreturns →
Permanently delete a wallet. WARNING: This cannot be undone! Make sure you have backed up your mnemonic.
Takes no parameters.
Example callreturns →
Export the mnemonic phrase for a wallet. WARNING: Only use this in a secure environment! Anyone with the mnemonic can access your funds.
Takes no parameters.
Example callreturns →
Change the password for a wallet
Takes no parameters.
Example callreturns →
Set how long the agent
Takes no parameters.
Example callreturns →
Get the agent
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Stx402 Agent costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 99 / 100
Release 3.0.2 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest15ea7e5db3803316f41cde9bad16b6261655e1b7cdf736e651ee5f526b98e1ee
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (1 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| stx402_migration_notice | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest15ea7e5db3803316
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 3.0.2 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
3.0.2
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Stx402 Agent in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.