Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Stellar Agent Search

NPM · STELLAR-AGENT-SEARCH · SCANNED SEP 20

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

0 this week 96 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 13 of 60 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to berkingurcan/stellar-agent-search). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 52 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2089 tokens (~130/item across 16 items; 13 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Stellar Agent Search MCP server?

Stellar Agent Search runs locally as an npm package, launched with npx -y stellar-agent-search. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · stellar-agent-search

# add to Claude Code
claude mcp add berkingurcan-stellar-agent-search -- npx -y stellar-agent-search
// .cursor/mcp.json
{
  "mcpServers": {
    "berkingurcan-stellar-agent-search": {
      "command": "npx",
      "args": [
        "-y",
        "stellar-agent-search"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "berkingurcan-stellar-agent-search": {
      "command": "npx",
      "args": [
        "-y",
        "stellar-agent-search"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add berkingurcan-stellar-agent-search -- npx -y stellar-agent-search
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "berkingurcan-stellar-agent-search": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "stellar-agent-search"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add berkingurcan-stellar-agent-search --command npx --arg -y --arg stellar-agent-search
# ~/.hermes/config.yaml
mcp_servers:
  berkingurcan-stellar-agent-search:
    command: "npx"
    args: ["-y", "stellar-agent-search"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "berkingurcan-stellar-agent-search": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "stellar-agent-search"
      ]
    }
  }
}
# add to Vellum
assistant mcp add berkingurcan-stellar-agent-search -t stdio -c npx -a -y stellar-agent-search
// mcp.json
{
  "mcpServers": {
    "berkingurcan-stellar-agent-search": {
      "command": "npx",
      "args": [
        "-y",
        "stellar-agent-search"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1
    • Stability: 0.97 → pass security
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 13 Sept 26 +1
    • Stability: 0.97 → pass security
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.

  • 7 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/stellar-agent-search@0.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo berkingurcan/stellar-agent-search
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/berkingurcan/stellar-agent-search/.github/workflows/publish.yml@refs/tags/v0.1.0
Rekor log index 2286341491
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:99141254e626f12eb212126ded9cb5ab52ec049a5e672bd221197c664b41cb617c1ce7696c758ceeab2373a5f6270278955ca5417d03dd55069174282

Background: How many MCP packages publish verified provenance →

Dependencies 60 packages
Packages resolved 60
Stale 13
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,756 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_agent ~247

Natural-language discovery of on-chain Stellar (stellar-8004) agents. Returns a ranked list with capability/reputation signals. Use rank_agent for per-axis breakdowns and get_agent_profile for full detail. Agent names/descriptions are self-declared (unverified) and live only in each row's labeled `selfDeclared` slot.

NameTypeReqDescription
hasServicesbooleanWhen present, require owner-declared service endpoint candidates.
limitinteger
minExplorerScorenumberMinimum upstream v1 Explorer total_score in protocol units; not local rank.
minScorenumberDeprecated ambiguous input; rejected. Use minExplorerScore.
mppbooleanWhen present, require MPP micropayment support.
querystringyesNatural-language description, e.g. 'a paid web scraper with a good reputation'.
sortBystring
truststringRequire a trust model.
verifybooleanProbe the Reputation contract for the top results (slower; current probe verifies no reputation fields).
x402booleanWhen present, require x402 (USDC pay-per-call) support.
NameTypeReqDescription
agentsarrayyes
countnumberyes
coverageobjectyes
interpretedQueryobjectyes

No examples provided.

get_agent_card ~116

Unverified A2A-shaped projection from indexed Stellar 8004 metadata. It is not an agent-published AgentCard and proves neither A2A conformance nor endpoint ownership. Owner-authored metadata and service candidates are isolated under `card.selfDeclared`.

NameTypeReqDescription
agentyesNumeric agent id, numeric string, or a full stellar:{network}:{identity}#{id} handle.
verifybooleanAttempt the bounded Reputation-contract reachability probe; it does not verify reputation fields, A2A conformance, or endpoints.
NameTypeReqDescription
cardobjectyes
conformancestringyes
notestringyes

No examples provided.

get_agent_feedback ~102

Recent Explorer-indexed on-chain feedback for one agent (client-authored, untrusted → returned in a labeled `selfDeclared` slot, sanitized). Revoked entries are hidden unless includeRevoked is set.

NameTypeReqDescription
agentyesNumeric agent id, numeric string, or a full stellar handle.
includeRevokedboolean
limitinteger
pageinteger
tagstringFilter by feedback tag.
NameTypeReqDescription
agentIdnumberyes
countnumberyes
coverageobjectyes
feedbackobjectyes
pagenumberyes
stellarIdstringyes
summaryobjectyes

No examples provided.

get_agent_profile ~152

Full profile for one agent: typed identity, capabilities, declared scores, a rank breakdown, bounded Reputation-contract reachability status, recent feedback, the canonical stellar:{network}:{identity}#{id} handle, and an explicitly unverified derived A2A-shaped projection. The current probe verifies no reputation fields. No A2A conformance or endpoint ownership is implied; self-declared text is confined to labeled `selfDeclared` slots.

NameTypeReqDescription
agentyesNumeric agent id, numeric string, or a full stellar:{network}:{identity}#{id} handle.
feedbackLimitinteger
verifybooleanAttempt the bounded Reputation-contract probe (default on; current probe verifies no reputation fields).
NameTypeReqDescription
agentCardobjectyes
feedbackCoverageobjectyes
profileobjectyes
recentFeedbackobjectyes
verificationobjectyes

No examples provided.

get_agents_by_owner ~85

List the owner endpoint's current page (up to 20 agents), ranked by the 3-axis engine. Coverage explicitly reports whether more owner rows exist. Self-declared text lives in each row's labeled `selfDeclared` slot.

NameTypeReqDescription
limitinteger
ownerstringyesOwner account (Stellar G-address).
verifyboolean
NameTypeReqDescription
agentsarrayyes
countnumberyes
coverageobjectyes
ownerstringyes

No examples provided.

get_registry_health ~57

Per-registry indexer health: last indexed ledger and staleness for the identity, reputation, and validation indexers. Staleness weakens the freshness of Explorer-declared data; it does not make a bounded contract read exhaustive.

Input schema present but exposes no named parameters.

NameTypeReqDescription
anyStalebooleanyes
indexerobjectyes
networkstringyes
statusstringyes

No examples provided.

get_registry_stats ~40

Explorer v1 registry counts plus sampled metrics, with explicit metric definitions, 5,000-agent sample cap, non-global distribution warning, and snapshot limitations.

Input schema present but exposes no named parameters.

NameTypeReqDescription
agentsWithMppyes
agentsWithServicesintegeryes
agentsWithX402integeryes
averageFeedbackScorenumberyes
coverageobjectyes
limitationsarrayyes
metricDefinitionsobjectyes
networkstringyes
protocolDistributionobjectyes
totalAgentsintegeryes
totalFeedbacksintegeryes
totalUniqueClientsintegeryes
totalValidationsintegeryes
trustDistributionobjectyes

No examples provided.

leaderboard ~178

Top-ranked agents in a bounded registry scan (or filter), by the 3-axis engine, with per-axis `breakdown`. On-chain verification of the top rows is optional. Coverage states whether the scan exhausted the filtered set; self-declared text lives in each row's labeled `selfDeclared` slot.

NameTypeReqDescription
hasServicesboolean
limitinteger
minExplorerScorenumberMinimum upstream v1 Explorer total_score in protocol units; not local rank.
minScorenumberDeprecated ambiguous input; rejected. Use minExplorerScore.
mppbooleanWhen present, require indexed MPP support.
truststring
verifybooleanProbe the Reputation contract for the top results; current probe verifies no reputation fields.
x402boolean
NameTypeReqDescription
agentsarrayyes
countnumberyes
coverageobjectyes

No examples provided.

list_agents ~181

Paginated, filterable listing of registered agents, ranked by the 3-axis engine. Filter by x402/mpp/hasServices/trust/minExplorerScore. Self-declared text lives in each row's labeled `selfDeclared` slot.

NameTypeReqDescription
hasServicesboolean
limitinteger
minExplorerScorenumberMinimum upstream v1 Explorer total_score in protocol units; not local rank.
minScorenumberDeprecated ambiguous input; rejected. Use minExplorerScore.
mppbooleanWhen present, require indexed MPP support.
pageinteger
sortBystring
truststring
verifybooleanProbe the Reputation contract for the top results; current probe verifies no reputation fields.
x402boolean
NameTypeReqDescription
agentsarrayyes
countnumberyes
coverageobjectyes
pagenumberyes
paginationobjectyes

No examples provided.

list_services ~203

Catalog of self-declared service endpoint candidates, each with its owning agent's indexed owner-declared capability/trust signals and ranked score. Filter by x402/mpp/trust/minExplorerScore/search. No endpoint is probed for liveness, ownership, protocol conformance, or payment behavior. Service labels/endpoints are unverified and live in each row's labeled `selfDeclared` slot.

NameTypeReqDescription
limitinteger
minExplorerScorenumberMinimum upstream v1 Explorer total_score in protocol units; not local rank.
minScorenumberDeprecated ambiguous input; rejected. Use minExplorerScore.
mppbooleanWhen present, only MPP micropayment services.
pageinteger
searchstringFree-text filter over agent name/description.
truststring
x402booleanWhen present, only x402 (USDC pay-per-call) services.
NameTypeReqDescription
countnumberyes
coverageobjectyes
pagenumberyes
servicesarrayyes

No examples provided.

rank_agent ~216

Rank an explicit agent set or a query's candidates using the deterministic declared-evidence policy: normalized indexed average × fixed evidence strength (0.4 capped volume + 0.6 breadth). Owner-declared capability fields add zero. On-chain checks are evidence metadata and never inflate rank. Every row carries a full per-axis `breakdown` and a declared-vs-verified `verification` block. Provide EITHER agentIds OR query.

NameTypeReqDescription
agentIdsarrayExplicit agent ids to rank (maximum 50 on this transport). Provide EITHER agentIds OR query, not both.
limitinteger
querystringNatural-language query whose candidates are ranked. XOR with agentIds.
sortBystring
verifybooleanAttempt the bounded Reputation-contract probe (default on; current probe verifies no reputation fields).
weightsobjectDeprecated and rejected when supplied. The v1 policy fixes evidence weights at volume=0.4 and breadth=0.6.
NameTypeReqDescription
agentsarrayyes
countnumberyes
coverageobject
evidenceWeightsobjectyes
rankVersionstringyes

No examples provided.

resolve_agent ~90

Resolve any agent reference (id, numeric string, stellar handle, or owner G-address) to the canonical typed identifiers (numeric id + stellar + CAIP-2). Owner addresses expand the current owner API page (up to 20); coverage reports whether more rows may exist.

NameTypeReqDescription
refyesAgent id, numeric string, stellar:{network}:{identity}#{id} handle, or owner G-address.
NameTypeReqDescription
agentsarrayyes
countnumberyes
coverageobject
kindstringyes
networkstringyes
owneryes

No examples provided.

verify_reputation ~89

Fail-closed reputation observation for one agent. The current Reputation contract has no authoritative client-set count/cursor and expired index entries can create holes, so the server performs one bounded reachability read but does not call get_summary or claim a diff. Current attempted checks return unavailable with explicit scope; skipped means not attempted.

NameTypeReqDescription
agentyesNumeric agent id, numeric string, or a full stellar handle.
NameTypeReqDescription
agentIdnumberyes
stellarIdstringyes
verificationobjectyes
verifiedbooleanyes

No examples provided.

Common questions

What is the Stellar Agent Search MCP server?

Stellar Agent Search is an MCP server listed in the public MCP registry as io.github.berkingurcan/stellar-agent-search. Discover and rank Stellar 8004 agents with a read-only MCP server and fail-closed contract probes. This page covers its npm package (stellar-agent-search).

Is the Stellar Agent Search MCP server safe to use?

Stellar Agent Search scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Stellar Agent Search MCP server expose?

Stellar Agent Search exposes 13 tools: find_agent, rank_agent, get_agent_profile, list_services, list_agents, and 8 more. Their descriptions and schemas cost roughly 1,756 tokens of context every time the server is loaded.

Is the Stellar Agent Search MCP server still maintained?

Stellar Agent Search is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Stellar Agent Search MCP server under?

Stellar Agent Search declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.