# io.github.sntlperson/space-intelligence (remote · mcp.sntl.space)

Space company and market intelligence from SNTL Space.

- Trust score: 86/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.sntl.space`: 86/100 (this document), [markdown](https://verifymcp.io/servers/sntlperson-space-intelligence/mcp.md), [page](https://verifymcp.io/servers/sntlperson-space-intelligence/mcp)

## Channel facts

- Endpoint: `https://mcp.sntl.space/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## 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-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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 (excellent).
  - Context-footprint check failed: tool/resource definitions use about 935 tokens (~233/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 io.github.sntlperson/space-intelligence MCP server?

io.github.sntlperson/space-intelligence is a hosted endpoint at https://mcp.sntl.space/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 sntlperson-space-intelligence 'https://mcp.sntl.space/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sntlperson-space-intelligence": {
      "url": "https://mcp.sntl.space/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sntlperson-space-intelligence": {
      "type": "http",
      "url": "https://mcp.sntl.space/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sntlperson-space-intelligence]
url = "https://mcp.sntl.space/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sntlperson-space-intelligence": {
      "type": "remote",
      "url": "https://mcp.sntl.space/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sntlperson-space-intelligence --url 'https://mcp.sntl.space/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sntlperson-space-intelligence:
    url: "https://mcp.sntl.space/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sntlperson-space-intelligence": {
      "Transport": "http",
      "Url": "https://mcp.sntl.space/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sntlperson-space-intelligence -t streamable-http -u 'https://mcp.sntl.space/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sntlperson-space-intelligence": {
      "type": "http",
      "url": "https://mcp.sntl.space/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-05 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 86, +1)

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

### 2026-11-02 (score 85, +1)

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

### 2026-10-31 (score 84, +1)

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

### 2026-10-29 (score 83, +1)

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

### 2026-10-26 (score 82, +1)

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

### 2026-10-24 (score 81, +1)

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

### 2026-10-22 (score 80, +1)

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

## MCP tools (4)

### `submit_research_interest` (~413 tokens)

Ask SNTL a research question

Ask SNTL one research question about a space company or market, and choose the product. answer (€12.50 to 31 December 2026, then €25): accepted or declined automatically. brief (€250, two to five pages) or map (€999, a segment mapped): SNTL accepts or declines the scope; on acceptance a fixed-price quote follows; delivered within 7 (brief) or 14 (map) days of payment. Nothing is owed until payment. Keep the receipt and return with check_research_status. Collection notice: https://sntl.space/enquiry-privacy. Do not include contact details or personal information.

Input parameters:

- `budget` (object): Optional: what you are prepared to spend, in minor units (cents) with a three-letter currency code. Prices are fixed by product.
- `companyName` (string): The company the question is about, when subjectType is space_company.
- `consentToStore` (boolean, required): Must be true: SNTL stores the request to answer it. Collection notice: https://sntl.space/enquiry-privacy.
- `maximumAgeDays` (integer): How recent the sources must be, in days (0 to 3,650).
- `outputFormat` (string, required): The form of the reply, whichever product you choose.
- `product` (string): What you are buying: answer (one question, answered with cited sources), brief (two to five pages) or map (a segment mapped). Optional; without it the request is an answer, priced as one.
- `question` (string, required): Your research question, 10 to 2,000 characters. Do not include contact details or personal information.
- `schemaVersion` (string, required): Always "1".
- `subjectType` (string, required): space_company for a question about one company; space_market for a market, segment or trend.
- `topics` (array): Up to five short topics that narrow the question, for example launch or earth observation.

### `check_research_status` (~90 tokens)

Check a research request

Retrieve the proposed scope, price offer, payment details, operator decision or research response using your receipt_id. Keep the receipt private. Use respond_to_research_offer to confirm or correct a proposed scope, or accept or decline an unexpired quote. If no response is available, try again later.

Input parameters:

- `receipt_id` (string, required): The receipt_id that submit_research_interest returned. Keep it private.

### `respond_to_research_offer` (~222 tokens)

Respond to SNTL's offer

Respond using your private receipt_id. confirm_scope or correct_scope requires a proposed scope; correct_scope, for an Answer only, also requires correction text (for a Brief or Map, send a changed question as a new request). accept_quote or decline_quote requires an unexpired quote; decline_quote may include a budget counter-offer. Acceptance records your choice of offer: no work starts and nothing is owed until payment. Use check_research_status before responding. Do not include contact details or personal information in a correction.

Input parameters:

- `action` (string, required): confirm_scope or correct_scope answers a proposed scope; accept_quote or decline_quote answers an unexpired quote.
- `budget` (object): For decline_quote: an optional counter-offer, in minor units (cents) with a three-letter currency code.
- `correction` (string): For correct_scope on an Answer: what to change in the proposed scope, 1 to 2,000 characters.
- `receipt_id` (string, required): The receipt_id that submit_research_interest returned. Keep it private.

### `check_coverage` (~97 tokens)

Check SNTL's coverage

Free. Check whether SNTL already holds verified material on a space company or topic before asking a question. Returns counts only: verified claims and market signals that match, the date of the newest, and the names matched. No content is returned; to receive research, use submit_research_interest.

Input parameters:

- `query` (string, required): A company or topic, for example Isar Aerospace or orbital data centres. 3 to 100 characters.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sntlperson-space-intelligence/mcp#diagnostics

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 85
- 2026-11-02: 85
- 2026-11-01: 84
- 2026-10-31: 84
- 2026-10-30: 83
- 2026-10-29: 83
- 2026-10-28: 82
- 2026-10-27: 82
- 2026-10-26: 82
- 2026-10-25: 81
- 2026-10-24: 81
- 2026-10-23: 80
- 2026-10-22: 80
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-11: 75
- 2026-10-10: 74
- 2026-10-07: 73
- 2026-10-06: 72

## Common questions

### What is the io.github.sntlperson/space-intelligence MCP server?

io.github.sntlperson/space-intelligence is an MCP server listed in the public MCP registry as io.github.sntlperson/space-intelligence. Space company and market intelligence from SNTL Space. This page covers its hosted endpoint (https://mcp.sntl.space/mcp).

### Is the io.github.sntlperson/space-intelligence MCP server safe to use?

io.github.sntlperson/space-intelligence scores 86 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 io.github.sntlperson/space-intelligence MCP server expose?

io.github.sntlperson/space-intelligence exposes 4 tools: submit_research_interest, check_research_status, respond_to_research_offer, check_coverage. Their descriptions and schemas cost roughly 822 tokens of context every time the server is loaded.

### Does the io.github.sntlperson/space-intelligence MCP server require authentication?

No. We connected to io.github.sntlperson/space-intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.sntlperson/space-intelligence MCP server still maintained?

io.github.sntlperson/space-intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.sntl.space/mcp
- Website: https://sntl.space/
- Changelog RSS feed: https://verifymcp.io/servers/sntlperson-space-intelligence/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sntlperson-space-intelligence/mcp.json
- HTML version of this page: https://verifymcp.io/servers/sntlperson-space-intelligence/mcp