Vector (Apex Fusion)

Name: Vector (Apex Fusion)
Author: Apex-Fusion

by Apex-Fusionversion 0.1.0i★ –iRuns in the cloud

Registry nameio.github.Apex-Fusion/vector

Install

Overview

Description from the maker (original English)

24 keyless tools for AI agents on Vector, the Apex Fusion eUTXO L2: wallets, contracts, registry.

PopNx MCP’s three pillars

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

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

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.

Connection: Runs in the cloud
Transport: Streamable HTTP, SSE
Category: Search & AI memory

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

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.vector.{network}.apexfusion.org/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Run this in your terminal

claude mcp add --transport http vector 'https://mcp.vector.{network}.apexfusion.org/mcp'

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

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

{
  "mcpServers": {
    "vector": {
      "url": "https://mcp.vector.{network}.apexfusion.org/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.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vector": {
      "type": "http",
      "url": "https://mcp.vector.{network}.apexfusion.org/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:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.vector.{network}.apexfusion.org/mcp

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

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 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Apex-Fusion, which owns the repo
… 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 applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
– Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
… 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 Search & AI memoryi

More stars than 0% of the other 7258 servers in this category
Published to the registry more recently than 28% of the other 7258 servers in this category
Basic checks equal to or better than 100% of the other 7258 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 Vector (Apex Fusion) 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.1.0) reached the registry 3 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: Context7, Codebase Memory, Exa

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

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.

Vector MCP Server

MCP (Model Context Protocol) server for Vector - the Apex Fusion eUTXO L2. Enables AI agents (Claude, GPT, Gemini, or any MCP client) to interact with Vector natively: query balances, send transactions, deploy and interact with smart contracts, manage on-chain agent identities, and submit protocol improvement proposals.

Built on Ogmios + Koios - no Blockfrost dependency.

Vector mainnet is live. Full guides: Vector AI documentation.

Hosted servers - no install

Hosted instances run on both networks. The 63 tools described below are the code of this release; each hosted instance serves them once the release deploys there (testnet automatically on push to main, mainnet on a deliberate cutover dispatch):

Network	Endpoint
Mainnet	`https://mcp.vector.mainnet.apexfusion.org/mcp`
Testnet	`https://mcp.vector.testnet.apexfusion.org/mcp`

**Deployment status: both networks are current with the non-custodial migration, and only

with that.** Both hosted instances run the completed migration: testnet since the

2026-07-31 morning merges (auto-deployed from main), mainnet since a deliberate cutover

deploy the same day (see

docs/architecture/non-custodial-split.md, section

11, "Rollout", for the full history). This does not mean a hosted instance serves every

tool listed below: the marketplace and reputation tools are newer than those deploys, and an instance

serves them only once the release that adds them has deployed there (until then its tool

list is shorter than the one below; a client's tool list shows what an instance serves right

now). Both hosted instances are open access - no bearer token is required to connect.

Callers are admitted anonymously with per-IP rate limiting.

That is an access-control property, and it is separate from custody: neither instance

accepts a mnemonic from any caller, with or without a token. Self-hosted deployments can

still gate access with MCP_AUTH_TOKENS - see Configuration.

Transport: Streamable HTTP only, as of 2.0.0. The legacy SSE pair (/sse +

/messages), deprecated by the MCP spec (2026-07-28 revision), was removed in this release -

those paths now answer 404. Every client connects to /mcp, the endpoint the table above

lists. This is a breaking change for SSE clients: reconnect with --transport http and the

/mcp URL (below). The server also answers any-origin CORS (browser MCP clients are

first-class callers) and exposes an unauthenticated GET /health liveness probe.

This describes the code - each hosted instance serves it once this release deploys there

(testnet automatically on push to main, mainnet on a deliberate cutover dispatch).

Connect from Claude Code in one command. No token needed for the hosted instances.

claude mcp add --transport http vector-mcp https://mcp.vector.mainnet.apexfusion.org/mcp

Swap in the testnet host to connect to testnet instead. Self-hosting (below) gives every caller open access to your own instance unless you set MCP_AUTH_TOKENS.

**Security notice: the non-custodial migration is complete, in this codebase and on both

hosted instances, as of the 2026-07-31 cutover deploy.** No tool in this repository accepts a

mnemonic, private key, or any other key material. Every build_* tool constructs an unsigned

transaction from a wallet *address* only, and every signing operation happens locally on your

own machine, through the local signer companion. Broadcast the signed result with

vector_submit_transaction - your seed phrase never leaves your machine, and no server

running this release ever holds one. This is enforced mechanically in the code, not just by

convention: the builder's custody boundary test scans every source file for key-material

vocabulary against an allowlist that is now empty and pinned at size zero, so a future change

cannot silently reintroduce a mnemonic parameter without failing that test by name.

This describes this release and the 2026-07-31 deploy specifically - a later deploy is a

separate operational action, not automatically covered by this notice; see the deployment

status note above and

docs/architecture/non-custodial-split.md for the

full rollout history.

Self-hosting instructions are below.

Local signer (non-custodial path)

packages/signer is a local MCP server that holds your key and signs transactions locally instead of handing your mnemonic to a shared host. It has no network access by default: stdio transport only, no Provider, no egress, so a key given to it never reaches a shared server or your model provider. One optional, read-only setting (VECTOR_SIGNER_OGMIOS_URL) lets it look up the inputs a transaction spends, so that its spend limit counts only what its own inputs fund. Five tools: vector_signer_get_address, vector_signer_get_public_key, vector_signer_decode_transaction, vector_signer_sign (also for a transaction that other keys signed first), vector_signer_get_spend_limits.

In this codebase, this signer is the single signing point for every family the builder exposes. The full non-custodial flow is live in this release for all of them: vector_signer_get_address → build_* → vector_signer_sign → vector_submit_transaction → vector_await_transaction. No step in that chain puts a mnemonic in front of a server running this code, or your model provider, for any tool. The build → submit → await half is E2E-proven on Vector testnet across the wallet/tx, smart-contract, agent-registry, and self-improvement families, including the first keyless-built proposal submission the deployed self-improvement module validator has ever accepted; see packages/signer/README.md for exactly what that testing does and does not exercise on the signer's side. This describes the code, not every deployment of it - see the deployment status note above.

See packages/signer/README.md for configuration, tools, and known limitations.

Features

Wallet & queries - balances, UTxOs, and transaction history for any address (no key material)
Keyless transaction building - build unsigned AP3X/token/multi-output transactions and contract interactions; sign locally, broadcast via submit
Smart contracts - deploy Plutus/Aiken validators, lock and spend UTxOs at script addresses (keyless)
Agent identity - resolve did:vector DIDs through the identity gateway, read an agent's profile by DID (canonical or legacy form), and discover agents with listed adverts through the marketplace indexer
Identity registry (did:vector) - keyless builders for every record action (register, also subagents; adopt a legacy record; update; change controller; suspend and unsuspend; revoke; retire; reclaim; successor; recovery; end subagents), attestations, delegations and vaults; every build returns the unsigned transaction and the key hashes that must sign it, and each key holder signs in turn. The legacy registry writes (register, update, transfer) are retired; a legacy record that does not adopt can still deregister
Self-Improvement Module - browse, submit, critique, and endorse improvement proposals on the Module-6 deployment of the identity registry (the agent is a did:vector agent whose record is Active); every write tool is keyless
Agents marketplace, both sides - hire a supplier (escrow post, accept, reclaim, send a job, check its receipt) and list one (advert post, update and retire in the identity layout; one retire for both layouts; the legacy-layout Post is refused from the escrow switch on), keyless
Reputation self-stake - the current Module-3 deployment takes no new stakes, so the two stake tools refuse (see Reputation)
Safety controls - per-identity rate limiting; spend limits for every family are enforced by the local signer, per user - the server holds no spend-limit state of its own
Streamable HTTP transport - the modern MCP transport at /mcp, with any-origin CORS for browser clients and an unauthenticated GET /health probe (the legacy SSE pair was removed in 2.0.0)

MCP Tools (63)

Wallet & Queries

Tool	Description
`vector_get_balance`	Get AP3X and token balances for any address
`vector_get_utxos`	List UTxOs for an address
`vector_get_transaction_history`	Get transaction history for an address

Transactions

Each build tool here and under Smart Contracts lists the key hashes that must sign the transaction (the wallet key, and any key that the transaction names as a required signer) before the unsigned CBOR, and as required_signers in its JSON block, as the identity and marketplace tools do. The ledger refuses a transaction that is submitted without these signatures.

Tool	Description
`vector_build_send_apex`	Build an unsigned AP3X transfer (keyless - sign with the local signer)
`vector_build_send_tokens`	Build an unsigned native-token transfer (keyless)
`vector_build_transaction`	Build an unsigned multi-output transaction (keyless, never submits)
`vector_dry_run`	Simulate a transaction without submitting - validate it and show its fee (the fee that a given transaction declares, or the fee of the transaction built from outputs)
`vector_submit_transaction`	Broadcast an already-signed transaction (for example one signed by the local signer)
`vector_await_transaction`	Wait for a submitted transaction to be confirmed on-chain

Smart Contracts

Tool	Description
`vector_build_deploy_contract`	Build an unsigned deployment of a Plutus V1/V2/V3 or Aiken validator (keyless)
`vector_build_interact_contract`	Build an unsigned lock or spend at a script address, with a redeemer (keyless)

Agent Identity

Tool	Description
`vector_resolve_did`	Resolve a `did:vector` DID (canonical or legacy form, optional `versionId`/`versionTime`) through the identity gateway; returns the HTTP status and the DID resolution result unchanged (no wallet needed)
`vector_get_agent_profile`	Get an agent's profile by DID: a canonical DID through the identity gateway (profile, effective status, keys, record output; the registration time is the block time of the transaction that first minted the identifier), a legacy DID from the legacy registry (no wallet needed)
`vector_discover_agents`	Discover agents with a listed advert, from the marketplace indexer; filter by capability (no wallet needed)
`vector_build_deregister_agent`	Build an unsigned deregistration of a legacy record that does not adopt - burns its token and returns the deposit (keyless)

Identity Registry (14)

Every tool below is keyless: it builds an unsigned transaction and lists every key hash that must sign it (controller, listed keys, parties, the wallet). Each key holder signs in turn with vector_signer_sign; then one vector_submit_transaction. The server needs the identity deployment values (see Configuration).

Tool	Description
`vector_build_identity_register`	Register a new agent (or, with `parent`, a subagent): mints the identity token named from a seed output of your wallet, so the DID is known before signing; at least one Accountable Party; deposit of at least 10 AP3X
`vector_build_identity_adopt`	Move a legacy record into the identity registry under the same identifier (allowlist proof against the published root; the legacy owner signs)

| vector_build_identity_update | Change the profile, listed ke

Only the beginning is shown; read the rest in the repo

Vector (Apex Fusion)

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Vector MCP Server

Hosted servers - no install

Local signer (non-custodial path)

Features

MCP Tools (63)

Wallet & Queries

Transactions

Smart Contracts

Agent Identity

Identity Registry (14)