io.github.sntlperson/space-intelligence
REMOTE · MCP.SNTL.SPACE
Space company and market intelligence from SNTL Space.
Available components
Last scanned (4 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 (excellent).Pass
- 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. 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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
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 5 Nov 2026 · Probed https://mcp.sntl.space/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.sntl.space | CN=YR1,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | RSA 2048 | SHA256-RSA | 5ca5b88ca400c2f6d6a8b5e61d2aeddc732 |
| SANs: mcp.sntl.space | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.sntl.space. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| space. | present | 51168 | 13 | Verified |
| sntl.space. | absent | 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 |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.sntl.space/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.sntl.space/mcp | HTTPS enforced | 308 | https://mcp.sntl.space/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 →
check_coverage Check SNTL's coverage ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A company or topic, for example Isar Aerospace or orbital data centres. 3 to 100 characters. |
No output schema declared.
No examples provided.
check_research_status Check a research request ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | The receipt_id that submit_research_interest returned. Keep it private. |
No output schema declared.
No examples provided.
respond_to_research_offer Respond to SNTL's offer ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 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 | yes | The receipt_id that submit_research_interest returned. Keep it private. |
No output schema declared.
No examples provided.
submit_research_interest Ask SNTL a research question ~413
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 | yes | Your research question, 10 to 2,000 characters. Do not include contact details or personal information. |
| schemaVersion | string | yes | Always "1". |
| subjectType | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · mcp.sntl.space
claude mcp add --transport http sntlperson-space-intelligence 'https://mcp.sntl.space/mcp'
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.