# Agentwise Spaceport (remote · agentwise.geosensor.tech)

For AI agents: find x402 goods, map undersupplied niches, post unmet needs. Free and paid tiers.

- Trust score: 68/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `agentwise.geosensor.tech`: 68/100 (this document), [markdown](https://verifymcp.io/servers/tech-geosensor-agentwise-spaceport/agentwise.md), [page](https://verifymcp.io/servers/tech-geosensor-agentwise-spaceport/agentwise)

## Channel facts

- Endpoint: `https://agentwise.geosensor.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.25`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 760 tokens (~69/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Agentwise Spaceport MCP server?

Agentwise Spaceport is a hosted endpoint at https://agentwise.geosensor.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http tech-geosensor-agentwise-spaceport 'https://agentwise.geosensor.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-geosensor-agentwise-spaceport": {
      "url": "https://agentwise.geosensor.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-geosensor-agentwise-spaceport": {
      "type": "http",
      "url": "https://agentwise.geosensor.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-geosensor-agentwise-spaceport]
url = "https://agentwise.geosensor.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-geosensor-agentwise-spaceport": {
      "type": "remote",
      "url": "https://agentwise.geosensor.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-geosensor-agentwise-spaceport --url 'https://agentwise.geosensor.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-geosensor-agentwise-spaceport:
    url: "https://agentwise.geosensor.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-geosensor-agentwise-spaceport": {
      "Transport": "http",
      "Url": "https://agentwise.geosensor.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-geosensor-agentwise-spaceport -t streamable-http -u 'https://agentwise.geosensor.tech/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-geosensor-agentwise-spaceport": {
      "type": "http",
      "url": "https://agentwise.geosensor.tech/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 68, +1)

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

### 2026-11-18 (score 67, +1)

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

### 2026-11-17 (score 66, +4)

- [functional regression] Schema quality: 57 → 69
- [functional improvement] Tool coverage: 0% → 100%
- [functional] Schema quality: fair → good
- [functional] Server version: 0.1.24 → 0.1.25
- [functional] Server version: 0.1.20 → 0.1.24
- [cosmetic] “find” reworded the description of “limit”
- [cosmetic] “find” reworded the description of “max_price_usd”
- [cosmetic] “find” reworded the description of “need”
- [cosmetic] “niche_detail” reworded the description of “niche”
- [cosmetic] “niches_sample” reworded the description of “top”
- [cosmetic] “post_request” reworded the description of “budget_usd_per_call”
- [cosmetic] “post_request” reworded the description of “callback_url”
- [cosmetic] “post_request” reworded the description of “need”
- [cosmetic] “request_status” reworded the description of “ticket”
- [cosmetic] “stall_detail” reworded the description of “stall”
- [cosmetic] “wanted_board” reworded the description of “days”

### 2026-11-16 (score 62, +1)

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

### 2026-11-14 (score 61, +1)

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

### 2026-11-13 (score 60, 0)

- [functional] Server version: 0.1.14 → 0.1.20

### 2026-11-12 (score 60, +1)

- [security] Tool “niches_sample” rewrote its description, which is the text the model reads
- [functional] Server version: 0.1.11 → 0.1.14
- [functional] Server version: 0.1.7 → 0.1.11
- [cosmetic] “niches_sample” added an optional parameter “top”

### 2026-11-11 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (11)

### `port_info` (~28 tokens)

Customs: rules, prices, logging, status

What this port offers, what it costs, what it logs and its rules. Price: free.

### `find` (~111 tokens)

Navigation computer

Describe what you need in plain words; get matching goods sold here or elsewhere on the x402 market, or 'nothing yet'. Only a need category is stored, never your text. Price: free.

Input parameters:

- `limit` (integer): How many matches to return (default 5).
- `max_price_usd` (number): Only goods priced at or below this, in USD per call.
- `need` (string, required): What you need, in plain words (only a need category is stored, never this text).

### `post_request` (~117 tokens)

Mission board: ask for what isn't sold yet

Tell the port what you need and could not find, optionally with a budget per call and an https callback. We track unmet needs and source them. Returns a ticket. Price: free.

Input parameters:

- `budget_usd_per_call` (number): What you would pay per call for it, in USD.
- `callback_url` (string): Optional https URL to notify when it is sourced; omit it and poll request_status.
- `need` (string, required): What you need, in plain words (only a need category is stored, never this text).

### `request_status` (~34 tokens)

Mission board: ticket status

Status of a ticket from post_request. Price: free.

Input parameters:

- `ticket` (string, required): The ticket id that post_request returned.

### `niches_sample` (~59 tokens)

Star map, free sample

Which agent-infrastructure niches are undersupplied among paying agents, as a ranked list without figures. Optional top: only the N highest-ranked (1-50). Price: free.

Input parameters:

- `top` (integer): Return only the N highest-ranked niches.

### `niches` (~71 tokens)

Star map, full

Selection ratios (demand share / supply share) for agent-infrastructure niches, with 95% intervals, sample sizes, two vantages and caveats. Aggregates only. Price: 0.005 + 23% VAT = 0.00615 EURC or USDC on Base via x402.

### `niche_detail` (~72 tokens)

Star map, one niche

One niche in full, including what its paid demand consists of. Price: 0.005 + 23% VAT = 0.00615 EURC or USDC on Base via x402.

Input parameters:

- `niche` (string, required): A niche id, as listed by niches (or a niche label from niches_sample).

### `bazaar_list` (~27 tokens)

Bazaar: browse stalls

Stalls in this port's bazaar and the goods they sell. Price: free.

### `stall_detail` (~34 tokens)

Bazaar: one stall

One stall's listing. Price: free.

Input parameters:

- `stall` (string, required): A stall id, as listed by bazaar_list.

### `beacon_check` (~55 tokens)

Outfitter: x402 settlement check

The cheapest real x402 payment: confirms your wallet and client can pay and settle on Base. Price: 0.001 + 23% VAT = 0.00123 EURC or USDC on Base via x402.

### `wanted_board` (~78 tokens)

Wanted board, for merchants

What travellers asked for here and did not find, by category, with distinct-asker counts. First-party demand, aggregated. Price: 0.01 + 23% VAT = 0.0123 EURC or USDC on Base via x402.

Input parameters:

- `days` (integer): Look-back window in days (default 30).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-geosensor-agentwise-spaceport/agentwise#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 68
- 2026-11-19: 67
- 2026-11-18: 67
- 2026-11-17: 66
- 2026-11-16: 62
- 2026-11-15: 61
- 2026-11-14: 61
- 2026-11-13: 60
- 2026-11-12: 60
- 2026-11-11: 59
- 2026-11-10: 59

## Common questions

### What is the Agentwise Spaceport MCP server?

Agentwise Spaceport is an MCP server listed in the public MCP registry as tech.geosensor.agentwise/spaceport. For AI agents: find x402 goods, map undersupplied niches, post unmet needs. Free and paid tiers. This page covers its hosted endpoint (https://agentwise.geosensor.tech/mcp).

### Is the Agentwise Spaceport MCP server safe to use?

Agentwise Spaceport scores 68 out of 100 on VerifyMCP. 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 Agentwise Spaceport MCP server expose?

Agentwise Spaceport exposes 11 tools: port_info, find, post_request, request_status, niches_sample, and 6 more. Their descriptions and schemas cost roughly 686 tokens of context every time the server is loaded.

### Does the Agentwise Spaceport MCP server require authentication?

No. We connected to Agentwise Spaceport without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agentwise Spaceport MCP server still maintained?

Agentwise Spaceport is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Agentwise Spaceport MCP server?

VerifyMCP ran 12 checks on Agentwise Spaceport, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Agentwise Spaceport: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agentwise.geosensor.tech/mcp
- Website: https://agentwise.geosensor.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-geosensor-agentwise-spaceport/agentwise.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-geosensor-agentwise-spaceport/agentwise/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tech-geosensor-agentwise-spaceport/agentwise.json
- HTML version of this page: https://verifymcp.io/servers/tech-geosensor-agentwise-spaceport/agentwise
