Agentwise Spaceport
REMOTE · AGENTWISE.GEOSENSOR.TECH
For AI agents: find x402 goods, map undersupplied niches, post unmet needs. Free and paid tiers.
Available components
Last scanned (22 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 760 tokens (~69/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 Nov 26 +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.
- 18 Nov 26 +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.
- 17 Nov 26 +4
- Schema quality: 57 → 69 ▼ functional
- 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 functional
- “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” cosmetic
- 16 Nov 26 +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.
- 14 Nov 26 +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.
- 13 Nov 26 0
- Server version: 0.1.14 → 0.1.20 functional
- 12 Nov 26 +1
- Tool “niches_sample” rewrote its description, which is the text the model reads security
- Server version: 0.1.11 → 0.1.14 functional
- Server version: 0.1.7 → 0.1.11 functional
- “niches_sample” added an optional parameter “top” cosmetic
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://agentwise.geosensor.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentwise.geosensor.tech | CN=YE1,O=Let's Encrypt,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 560d01303756c486bc73e272bd5d0a2ec41 |
| SANs: agentwise.geosensor.tech | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentwise.geosensor.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | DS published | 2185 | 13 | Verified |
| geosensor.tech. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentwise.geosensor.tech/mcp | Verified | 200 | |
| http (plaintext) | http://agentwise.geosensor.tech/mcp | HTTPS enforced | 301 | https://agentwise.geosensor.tech/mcp |
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 →
bazaar_list Bazaar: browse stalls ~27
Stalls in this port's bazaar and the goods they sell. Price: free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
beacon_check Outfitter: x402 settlement check ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find Navigation computer ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What you need, in plain words (only a need category is stored, never this text). |
No output schema declared.
No examples provided.
niche_detail Star map, one niche ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| niche | string | yes | A niche id, as listed by niches (or a niche label from niches_sample). |
No output schema declared.
No examples provided.
niches Star map, full ~71
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
niches_sample Star map, free sample ~59
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.
| Name | Type | Req | Description |
|---|---|---|---|
| top | integer | – | Return only the N highest-ranked niches. |
No output schema declared.
No examples provided.
port_info Customs: rules, prices, logging, status ~28
What this port offers, what it costs, what it logs and its rules. Price: free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
post_request Mission board: ask for what isn't sold yet ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | What you need, in plain words (only a need category is stored, never this text). |
No output schema declared.
No examples provided.
request_status Mission board: ticket status ~34
Status of a ticket from post_request. Price: free.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket | string | yes | The ticket id that post_request returned. |
No output schema declared.
No examples provided.
stall_detail Bazaar: one stall ~34
One stall's listing. Price: free.
| Name | Type | Req | Description |
|---|---|---|---|
| stall | string | yes | A stall id, as listed by bazaar_list. |
No output schema declared.
No examples provided.
wanted_board Wanted board, for merchants ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look-back window in days (default 30). |
No output schema declared.
No examples provided.
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.
remote · agentwise.geosensor.tech
claude mcp add --transport http tech-geosensor-agentwise-spaceport 'https://agentwise.geosensor.tech/mcp'
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.