Instxnt

io.github.EricSpencer00Published by GitHub account EricSpencer00v0.4.0Updated Oct 24, 2026

Create instxnt.xyz storefronts through Claude: add products, connect Stripe, go live.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant create and manage instxnt.xyz storefronts, including adding products and connecting Stripe.

What you can do
This server exposes instxnt.xyz storefront creation and management to an assistant. Based on the description, it can create storefronts, add products, and connect Stripe so a shop can go live. No tool list is published, so the exact operations available are not documented here.
When to use it
Worth considering if you sell through instxnt.xyz and want an assistant to set up or update a storefront, add products, or wire up Stripe without using the dashboard manually.
Requirements
An instxnt API key, supplied as the INSTXNT_API_KEY environment variable; the key is obtained from the instxnt dashboard. An optional INSTXNT_API_URL variable overrides the default API endpoint. It can run as a remote endpoint or as a local npm package over stdio, so Node.js is needed for the local option.
Before you install
The server requires the secret INSTXNT_API_KEY, which grants access to your instxnt account. It can create storefronts, add products, and connect Stripe, so it changes live commerce data and may involve payment processing; review actions before they run. The remote endpoint sends your requests to a third-party service.

Installation

In SourceWeft

  1. Open Instxnt in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.EricSpencer00%2Finstxnt/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "instxnt": {
      "type": "http",
      "url": "https://mcp.instxnt.xyz/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.4.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.