SacrosanctSpace MCP server
ai.s-space/sacrosanct-spaces-space.aistreamable-httpv1.0.0Scanned
Buy per-use Spaces (small paid tools) on s-space.ai with USDC on Base. No account needed.
5 tools: 2 do something that can't be undone and 3 only 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
2 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 SacrosanctSpace MCP server can do
The SacrosanctSpace MCP server is published by s-space.ai, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (prepare_purchase and complete_purchase), but cannot delete data. 3 tools only read.
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, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.0.0.
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.
5 tools
Can't be undone 2Claude Code: ask
complete_purchaseAfter paying with prepare_purchase.payment_plan, submit the mined transaction hash with the payment_id, purchase_ticket, and commerce_scope.No findings
Why it is in this group
- The name "complete_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it After paying with prepare_purchase.payment_plan, submit the mined transaction hash with the payment_id, purchase_ticket, and commerce_scope. Verifies the payment on-chain, then executes the purchased function and returns its result.
prepare_purchasePrepare a guest per-call purchase: returns the authoritative price split, payment_id, purchase_ticket, reissued commerce_scope, and payment_plan.No findings
Why it is in this group
- The name "prepare_purchase" says "purchase": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Prepare a guest per-call purchase: returns the authoritative price split, payment_id, purchase_ticket, reissued commerce_scope, and payment_plan. Pay by sending payment_plan.calls (to/value/data verbatim) from the buyer wallet as ONE atomic batch transaction on Base Mainnet — the platform call's data carries the required payment_id stamp; separate or re-encoded transfers are refused and not refunded.
Only reads 3Show 3 read-only tools
get_purchase_statusRecover a purchase after a dropped connection: reports whether a (payment_id, tx_hash) pair was already consumed.No findings
Why it is in this group
- The name "get_purchase_status" says "get": a word for reading.
Description, as the server wrote it Recover a purchase after a dropped connection: reports whether a (payment_id, tx_hash) pair was already consumed.
get_service_detailsGet a service's functions, inputs, price, purchase model, and the commerce_scope needed to buy.No findings
Why it is in this group
- The name "get_service_details" says "get": a word for reading.
Description, as the server wrote it Get a service's functions, inputs, price, purchase model, and the commerce_scope needed to buy. Refuses account-bound models with ACCOUNT_REQUIRED.
search_servicesSearch the live SacrosanctSpace marketplace.No findings
Why it is in this group
- The name "search_services" says "search": a word for reading.
Description, as the server wrote it Search the live SacrosanctSpace marketplace. Returns published service cards (creator, slug, title, summary, model, price in USDC per call). Only publicly listed Spaces appear.
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.
Looked at Nov 14, 2026, 12:20 UTC, unchanged since Nov 7, 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
- 2
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://s-space.ai/mcp: tools/list returned 5 tools to an anonymous client, including prepare_purchase (irreversible), complete_purchase (irreversible)
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.
Tools1 changed.~1 changedView diff
- Changed:search_servicesOnly readsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http sacrosanct-space https://s-space.ai/mcpclaude mcp add --transport http sacrosanct-space https://s-space.ai/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__sacrosanct-space__search_services",
"mcp__sacrosanct-space__get_service_details",
"mcp__sacrosanct-space__get_purchase_status"
],
"ask": [
"mcp__sacrosanct-space__prepare_purchase",
"mcp__sacrosanct-space__complete_purchase"
],
"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 sacrosanct-space. 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/ai.s-space/sacrosanct-space/verify?hash=9465df47eb462460cfae1597bdb88bf3ff7f1eee25aca3794055c2e1bd325ab5" | jq -e '.changed == false'Pinned hash 9465df47eb46, from Nov 20, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.s-space/sacrosanct-space/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.s-space/sacrosanct-space)Source: MCP Registry. Synced Nov 6, 2026, 10:17 UTC.
SacrosanctSpace MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SacrosanctSpace MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 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 SacrosanctSpace MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SacrosanctSpace MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: prepare_purchase and complete_purchase.
What tools does the SacrosanctSpace MCP server have?
- 5 tools: 2 irreversible, 3 read. prepare_purchase, complete_purchase, search_services, get_service_details and get_purchase_status.
Does the SacrosanctSpace MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SacrosanctSpace MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SacrosanctSpace MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.