Skip to content

space-intelligence MCP server

io.github.sntlperson/space-intelligencesntlpersonstreamable-httpv0.2.1Scanned

Space company and market intelligence from SNTL Space.

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the space-intelligence MCP server can do

The space-intelligence MCP server is published by the GitHub account sntlperson. It has 4 tools. It can create or change data (3 tools: submit_research_interest, respond_to_research_offer and check_coverage), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 0.2.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • check_coverageFree.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check SNTL's coverage
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • respond_to_research_offerRespond using your private receipt_id.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Respond to SNTL's offer
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • submit_research_interestAsk SNTL one research question about a space company or market, and choose the product.No findings

    Why it is in this group

    • The name "submit_research_interest" says "submit": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Ask SNTL a research question
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • check_research_statusRetrieve the proposed scope, price offer, payment details, operator decision or research response using your receipt_id.No findings

    Why it is in this group

    • The name "check_research_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a research request
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.sntl.space/mcp: tools/list returned 4 tools to an anonymous client, including submit_research_interest (write), respond_to_research_offer (write), check_coverage (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.2.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http space-intelligence https://mcp.sntl.space/mcp
claude mcp add --transport http space-intelligence https://mcp.sntl.space/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__space-intelligence__check_research_status"
    ],
    "ask": [
      "mcp__space-intelligence__submit_research_interest",
      "mcp__space-intelligence__respond_to_research_offer",
      "mcp__space-intelligence__check_coverage"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as space-intelligence. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.sntlperson/space-intelligence/verify?hash=fd6cc04bfedd745ca4969b8822032d95d015faeafbdc9cf4fe15dd64533165e7" | jq -e '.changed == false'

Pinned hash fd6cc04bfedd, from Nov 21, 2026, 03:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.sntlperson/space-intelligence/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.sntlperson/space-intelligence
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.sntlperson/space-intelligence.svg)](https://radar.anlyon.com/servers/io.github.sntlperson/space-intelligence)

Source: MCP Registry. Synced Oct 21, 2026, 18:49 UTC.

space-intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the space-intelligence MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the space-intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the space-intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the space-intelligence MCP server have?

4 tools: 3 write, 1 read. submit_research_interest, respond_to_research_offer, check_coverage and check_research_status.

Does the space-intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the space-intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the space-intelligence MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.