Stellar Agent Search

Name: Stellar Agent Search
Author: berkingurcan

by berkingurcanversion 0.1.0i★ –iRuns on your computer

Registry nameio.github.berkingurcan/stellar-agent-search

Install

Overview

Description from the maker (original English)

Discover and rank Stellar 8004 agents with a read-only MCP server and fail-closed contract probes.

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 on your computer
Transport: stdio
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 your computer with your user’s permissions (files, network, apps).
You fill in yourself: STELLAR_NETWORK, EXPLORER_BASE_URL, STELLAR_RPC_URL, VERIFY_ONCHAIN

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

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

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "stellar-agent-search": {
      "command": "npx",
      "args": [
        "-y",
        "stellar-agent-search"
      ],
      "env": {
        "STELLAR_NETWORK": "your-value",
        "EXPLORER_BASE_URL": "your-value",
        "STELLAR_RPC_URL": "your-value",
        "VERIFY_ONCHAIN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add stellar-agent-search --env STELLAR_NETWORK=your-value --env EXPLORER_BASE_URL=your-value --env STELLAR_RPC_URL=your-value --env VERIFY_ONCHAIN=your-value -- npx -y stellar-agent-search

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "stellar-agent-search": {
      "command": "npx",
      "args": [
        "-y",
        "stellar-agent-search"
      ],
      "env": {
        "STELLAR_NETWORK": "your-value",
        "EXPLORER_BASE_URL": "your-value",
        "STELLAR_RPC_URL": "your-value",
        "VERIFY_ONCHAIN": "your-value"
      }
    }
  }
}

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": {
    "stellar-agent-search": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "stellar-agent-search"
      ],
      "env": {
        "STELLAR_NETWORK": "your-value",
        "EXPLORER_BASE_URL": "your-value",
        "STELLAR_RPC_URL": "your-value",
        "VERIFY_ONCHAIN": "your-value"
      }
    }
  }
}

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.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

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

Values you fill in

STELLAR_NETWORK env
Stellar network to target: mainnet | testnet. testnet also requires EXPLORER_BASE_URL — the default explorer indexes mainnet only, and the server refuses to start on the mismatched pair.
EXPLORER_BASE_URL env
Override the stellar-8004 explorer API base URL.
STELLAR_RPC_URL env
Override the Soroban RPC URL used for the bounded Reputation-contract probe.
VERIFY_ONCHAIN env
Set to 'false' to skip the bounded contract probe; reputation fields remain Explorer-declared either way.

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

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

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

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account berkingurcan, 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
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5670 servers in this category
Published to the registry more recently than 26% of the other 5670 servers in this category
Basic checks equal to or better than 100% of the other 5670 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 Stellar Agent Search 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 on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

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. You also need Node.js on your computer.

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 yesterday

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 21 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 2 months ago

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.

stellar-agent-search

A read-only discovery layer on top of the [stellar-8004](https://stellar8004.com) registry — the ERC-8004-style Identity/Reputation/Validation contracts on Stellar mainnet.

It adds no contracts and forks nothing: it exposes the existing on-chain registry to MCP clients, keeps indexed reputation explicitly declared-vs-verified, and proves the full agent-finds-agent loop with recorded mainnet transactions.

npm · GitHub · Docs · Evidence package

npm	MCP Registry	Remote endpoint	Mainnet proof
✅ `0.1.0`	✅ published & verified	⏳ not deployed yet	✅ x402 payment · feedback

There are two official interfaces, not two copies of the stack. TypeScript applications, registration, and signed writes use the canonical @trionlabs/stellar8004 SDK from trionlabs/stellar-8004; MCP clients and terminal discovery use this package, which exact-pins that SDK internally. The upstream repo's restricted Supabase Studio /mcp is database-operator tooling behind SSH/IP controls, not an agent-registry MCP and must never be exposed as this runtime. See the integration boundary.

A read-only, keyless MCP server (and human CLI) that lets an AI agent — or you — discover, rank, and vet on-chain [stellar-8004](https://stellar8004.com) agents on Stellar mainnet, then prepare an x402 (USDC pay-per-call) payment. One binary speaks the Model Context Protocol over stdio to Claude Code / Cursor / Windsurf / Cline / VS Code, and doubles as a plain-terminal tool. A separate Cloudflare Worker implementation exposes the same surface over stateless Streamable HTTP, but that remote endpoint is not live yet; use the local stdio transport until its deployment canary passes.

npx -y stellar-agent-search@0.1.0 find "a paid web scraper with a good reputation"

AI agents: read [AGENTS.md](AGENTS.md) first. It routes each goal to the right document: using the

tools, integrating from code, building a service other agents can find and pay

(provider guide), or changing this repo. Link index:

llms.txt · machine-readable schemas: mcp-surface.json.

Why this exists: declared data vs. what the chain read can prove

Off-chain agent directories (A2A cards, the MCP Registry, OASF, NANDA) list self-declared agents. That is exactly where the trust gap lives. A 2026 study of the ERC-8004 ecosystem (arXiv 2606.26028) found that only 3–15% of registrations have a live endpoint, and 59–91% of "reviewers" are Sybils.

stellar-8004 is the only non-EVM ERC-8004 implementation we are aware of running on mainnet (66 agents on Stellar mainnet as of July 2026; get_registry_stats returns the current count). No published survey enumerates non-EVM deployments — the study above restricts itself to Ethereum, BSC and Base, "the three chains with the highest registration and feedback volume" — so read that as unrefuted, not as proven. This server adds something a directory listing cannot give you: a bounded Reputation-contract reachability probe. The current path calls get_clients_paginated once with a six-slot observation window. The contract exposes no authoritative client count/cursor, and expired client-index entries create holes, so even an empty or short page cannot prove that no later live client exists. Calling get_summary over that set would manufacture a false match or mismatch; this release therefore does not call it and verifies no reputation fields. An attempted, reachable probe returns unavailable with reason client-set-exhaustion-unprovable; verifiedFields is empty and average, feedback count, and unique clients all remain unverified. verified/partial/mismatch are reserved for a future authoritative aggregate. The full status set remains verified | partial | mismatch | unavailable | skipped. Self-declared marketing text (name, description, service labels, feedback tags) remains untrusted data, never instructions (see Security).

That fail-closed boundary — plus a versioned declared-evidence heuristic — is the product. Normalized Explorer quality is multiplied by fixed evidence strength (0.4 × capped volume + 0.6 × effective breadth). Effective unique clients cannot exceed feedback rows, and repeated rows per declared client are capped. These are cost-of-manipulation proxies, not chain verification, proof of personhood, or Sybil resistance.

What it exposes

All three MCP primitives, all read-only:

Tools

Tier	Tool	What it does
0 · SOW	`find_agent`	Natural-language discovery → ranked candidates
	`rank_agent`	Rank an explicit id set or a query, full 3-axis declared-reputation breakdown + bounded chain reachability
	`get_agent_profile`	Deep profile: identity, capabilities, declared reputation + contract-probe limits, recent feedback, unverified A2A projection
	`list_services`	Self-declared x402/MPP endpoint candidates; liveness, ownership, conformance, and payment stay unverified
1 · complete-core	`list_agents`	Paginated, filterable listing, ranked
	`leaderboard`	Top agents in a bounded scan (client-side 3-axis rank + coverage)
	`resolve_agent`	Any handle (id / stellar:…#id / owner G-address) → canonical identifiers
	`get_agents_by_owner`	Current owner API page (up to 20 agents) with explicit continuation coverage
	`get_agent_feedback`	Recent on-chain reviews (sanitized, labeled)
	`verify_reputation`	Fail-closed Reputation-contract reachability probe; no current fields are verified
	`get_agent_card`	Derived, unverified A2A-shaped projection + x402 hint; not protocol-conformance proof
	`get_registry_stats`	Exact-count queries + capped sampled metrics, with definitions and coverage
	`get_registry_health`	Per-registry indexer staleness
2 · provider network	`get_provider_manifest`	A Provider Standard v1 provider's prices in USDC, network, payee and result retention; its binding to the on-chain registration and wallet; conformance badges from trusted validators

Full per-tool reference (inputs, outputs, defaults): [docs/tools.md](docs/tools.md).

Resources — `stellar8004://` (pinnable context)

registry · leaderboard · health · agent/{id} · agent/{id}/card · agent/{id}/feedback · agent/{id}/reputation · owner/{address}. Each returns a dual JSON + rendered-markdown payload.

Prompts — slash workflows

/find-and-vet-agent (flagship) · /vet-agent · /compare-agents · /prepare-x402-call · /explore-registry. prepare-x402-call lays out the exact x402 flow and stops before signing — this server holds no keys.

Quickstart

One-command MCP setup (Claude Code):

npx -y stellar-agent-search@0.1.0 setup --client claude --scope user --handshake

This downloads the package, registers a version-pinned npx -y stellar-agent-search@0.1.0 mcp stdio launch through Claude Code's own CLI, then performs a real MCP initialize + tools/list handshake. It is idempotent: rerun with --check --handshake to verify without changing config, or use --dry-run to preview the registration. Cursor and Codex examples, config paths, and scope limitations are in [docs/getting-started.md](docs/getting-started.md). Manual configs for other clients remain in [docs/integration.md](docs/integration.md).

Optionally install the skill first — the usage guide your agent reads before it calls anything:

npx skills add berkingurcan/stellar-agent-search --skill mcp

Terminal (human CLI):

npx -y stellar-agent-search@0.1.0 find "web scraper" --x402       # discover

npx -y stellar-agent-search@0.1.0 profile 10 # full profile for agent 10 npx -y stellar-agent-search@0.1.0 rank "scraping agents" --json # rank + fail-closed contract-probe status, machine-readable npx -y stellar-agent-search@0.1.0 services --x402 # declared paid-endpoint candidates npx -y stellar-agent-search@0.1.0 doctor # self-check: env, explorer, RPC, bounded read path npx -y stellar-agent-search@0.1.0 setup --client cursor --scope project --dry-run # preview client config

New here? Start with [docs/getting-started.md](docs/getting-started.md).

Remote endpoint status

The intended hosted URL is https://mcp.stellar8004.com/mcp. The Worker, transport tests, routing, and hardening are implemented, but the route has not been deployed: /mcp currently falls through to the landing site and returns 404. Deployment remains deliberately blocked until the Cloudflare rate-limit namespace is replaced from its sentinel value and a live canary proves that the original caller identity is preserved through the Service Binding. Do not configure a remote MCP client against that URL yet.

The landing page and MCP runtime are separate Workers. The assets-only landing Worker owns the mcp.stellar8004.com custom domain; exact /mcp and /healthz zone routes will send only those two paths to the runtime Worker. The runtime reads the existing stellar8004-web API through a Cloudflare Service Binding. It does not connect to Supabase, hold a service-role key, or create a second indexer. See [docs/architecture.md](docs/architecture.md) and [docs/stellar8004-integration.md](docs/stellar8004-integration.md).

Configuration

All configuration is via environment variables (canonical for MCP mode); CLI flags override them (precedence: flag → env → default).

Env var	Default	Purpose
`STELLAR_NETWORK`	`mainnet`	`mainnet` or `testnet`. With no other data source set, `testnet` reads its newest agents straight from the Identity contract, see below
`EXPLORER_BASE_URL`	`https://stellar8004.com` on mainnet	Explorer HTTP API base. Indexes mainnet only, so testnet never falls back to it
`REGISTRY_AGENT_IDS`	—	Registry mode over an allowlist: comma-separated agent ids (at most 50) read straight from the Identity contract, no explorer. Not combinable with `EXPLORER_BASE_URL` or `REGISTRY_SCAN_LIMIT`
`REGISTRY_SCAN_LIMIT`	`50` on testnet	Registry mode over the newest agents: how many (1–50) of the most recently registered agents lists and searches read. Testnet's default source; set it on mainnet to use it there instead of the explorer. Not combinable with `EXPLORER_BASE_URL` or `REGISTRY_AGENT_IDS`

| TRUSTED_VALIDATORS | — | Comma-separated G… or C… addresses (at most 20) of the verifiers whose Validation Reg

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

Stellar Agent Search

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

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

stellar-agent-search

Why this exists: declared data vs. what the chain read can prove

What it exposes

Tools

Resources — stellar8004:// (pinnable context)

Prompts — slash workflows

Quickstart

Remote endpoint status

Configuration

Resources — `stellar8004://` (pinnable context)