SoChain
REMOTE · SOCHAIN.COM
Live Bitcoin, Litecoin, Dogecoin and Zcash data: balances, transactions, blocks, fees, prices.
Available components
Last scanned (20 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Crypto and Web3
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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2703 tokens (~135/item across 20 items; 20 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 Management6
- Stability check failed: schema churn in the 7 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.
- 17 Oct 26 −1
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “contact_support” was removed ▼ security
- Tool “get_account_info” was removed ▼ security
- Tool “get_bucket_balance” was removed ▼ security
- Tool “get_bucket_transactions” was removed ▼ security
- Schema quality: 3300 → 2703 ▲ functional
- Tool “get_address_poisoning” now declares an output schema ▲ functional
- Tool “get_address_rank” now declares an output schema ▲ functional
- Tool “get_address_summary” now declares an output schema ▲ functional
- Tool “get_balance” now declares an output schema ▲ functional
- Tool “get_balance_history” now declares an output schema ▲ functional
- Tool “get_best_block_hash” now declares an output schema ▲ functional
- Tool “get_block” now declares an output schema ▲ functional
- Tool “get_chart” now declares an output schema ▲ functional
- Tool “get_counterparties” now declares an output schema ▲ functional
- Tool “get_latest_blocks” now declares an output schema ▲ functional
- Tool “get_network_info” now declares an output schema ▲ functional
- Tool “get_price” now declares an output schema ▲ functional
- Tool “get_rich_list” now declares an output schema ▲ functional
- Tool “get_transaction” now declares an output schema ▲ functional
- Tool “get_transaction_counts” now declares an output schema ▲ functional
- Tool “get_transaction_status” now declares an output schema ▲ functional
- Tool “get_transactions” now declares an output schema ▲ functional
- Tool “get_unspent_outputs” now declares an output schema ▲ functional
- Tool “is_valid_address” now declares an output schema ▲ functional
- Tool “search” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Destructive annotations: 100 → pass functional
- “get_chart” reworded the description of “interval” cosmetic
- “get_chart” reworded the description of “series” cosmetic
- “search” reworded the description of “query” cosmetic
- 16 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 73
First indexed and scored.
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 22 Oct 2026 · Probed https://sochain.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sochain.com | CN=YE1,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5a16e3a5e8913df44b248b02d3bc41a05b3 |
| SANs: *.sochain.com, sochain.com | ||||||
| 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 secure
Validation of sochain.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sochain.com. | present | 2371 | 13 | Verified |
| sochain.com. | Verified address RRset verified with the apex keys |
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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sochain.com/mcp | Verified | 200 | |
| http (plaintext) | http://sochain.com/mcp | HTTPS enforced | 301 | https://sochain.com/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 →
get_address_poisoning Address Poisoning Check ~131
Whether an address was targeted by address poisoning: look-alike addresses that sent it dust, imitating an address it really paid or was paid by, so a careless copy from its history pays the scammer. Each finding names the look-alike, whom it imitates and the real payment.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| limit | integer | – | Findings, default 50, newest first. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| building | boolean | yes | – |
| findings | array | yes | – |
No examples provided.
get_address_rank Address Rank ~80
Where an address stands among the largest holders (exact within the top 10,000) and its share of the supply.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| balance | string | yes | – |
| rank | integer|null | yes | – |
| rank_limit | integer | yes | – |
| share_of_supply | number|null | yes | – |
No examples provided.
get_address_summary Address Summary ~74
Totals for an address: balance, total received, and how many transactions sent and received.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed_balance | string | yes | – |
| confirmed_received | string | yes | – |
| first_active | object|null | – | – |
| last_active | object|null | – | – |
| txs_received | integer | yes | – |
| txs_sent | integer | yes | – |
| txs_total | integer | yes | – |
| unconfirmed_balance | string | yes | – |
No examples provided.
get_balance Address Balance ~164
Confirmed and unconfirmed balance of an address; with height or time, its confirmed balance at that point (for example at the end of a year).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| height | integer | – | Optional: the confirmed balance at the end of this block instead. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| time | string | – | Optional: the confirmed balance at this time instead (a date means the end of that day): unix seconds, a date like 2025-12-31 (UTC) or a timestamp like 2025-12-31T23:59:59Z. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| block_hash | string|null | – | – |
| confirmed | string | yes | – |
| height | integer|null | – | – |
| time | integer|null | – | – |
| tip_height | integer | – | – |
| unconfirmed | string | – | – |
No examples provided.
get_balance_history Address Balance History ~218
An address's confirmed balance by day, week or month, with what came in and went out in each and how many transactions did each. Without an API key at most 2,000 points (daily: the most recent days unless from says otherwise); with one, 20,000.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| from | string | – | Optional start: unix seconds, a date like 2025-12-31 (UTC) or a timestamp like 2025-12-31T23:59:59Z. |
| interval | string | – | Default day. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| to | string | – | Optional end (a date means its last second): unix seconds, a date like 2025-12-31 (UTC) or a timestamp like 2025-12-31T23:59:59Z. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| exact_resolution | boolean | – | – |
| external_available | boolean | – | – |
| interval | string | yes | – |
| points | array | yes | – |
| resolution_blocks | integer | – | – |
| tx_counts_available | boolean | – | – |
No examples provided.
get_best_block_hash Best Block Hash ~51
The hash of the newest block.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
No examples provided.
get_block Block ~95
A block by height or hash: time, transactions, size, reward, fees, miner.
| Name | Type | Req | Description |
|---|---|---|---|
| block | string | yes | Block height (number) or 64-character block hash. |
| currency | string | – | Optional: prices in this currency instead of USD. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| bits | string | – | – |
| confirmations | integer | yes | – |
| difficulty | string | – | – |
| fees | string | – | – |
| hash | string | yes | – |
| height | integer | yes | – |
| is_orphan | boolean | – | – |
| kinds | object | – | – |
| max_fee_rate | integer|null | – | – |
| median_fee_rate | integer|null | – | – |
| merkleroot | string | – | – |
| min_fee_rate | integer|null | – | – |
| next_block_hash | string|null | – | – |
| nonce | integer|string | – | – |
| num_txs | integer | yes | – |
| previous_block_hash | string|null | – | – |
| price | object|null | – | – |
| reward | string | – | – |
| size | integer | – | – |
| time | integer | yes | – |
| txs | array | – | – |
| value_out | string | – | – |
| version | integer | – | – |
| weight | integer | – | – |
No examples provided.
get_chart Chart Series ~318
A chart series: tx_count, fees_total, fees_median, block_size, difficulty, hashrate, supply, price_usd, tx_per_min, block_interval, mempool_txs, mempool_bytes, pool_share, holder_share, new_addresses, active_addresses, transfers, lookalikes, on LTC and LTCTEST mweb_pool (coins in MWEB) and mweb_flows (peg-ins and peg-outs), and on ZEC and ZECTEST zcash_pools (the value in each Zcash pool). Intervals: block (last 1,000 blocks), hour (90 days), day (full history), minute (last hour; tx_per_min and mempool series only).
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Optional, price_usd only: the price in this currency instead of USD. |
| from | integer | – | Optional start: block height for the block interval, else unix time. |
| interval | string | yes | Each point's span: block (the last 1,000 blocks), minute (the last hour), hour (90 days) or day (the full history). |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| series | string | yes | The series, as listed above: mweb_pool and mweb_flows on Litecoin only, zcash_pools on Zcash only. |
| to | integer | – | Optional end, same units as from. |
| Name | Type | Req | Description |
|---|---|---|---|
| interval | string | yes | – |
| points | array | yes | – |
| series | string | yes | – |
No examples provided.
get_counterparties Address Counterparties ~89
Who an address moved significant amounts to and from lately (the window the poisoning check watches), newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| limit | integer | – | Rows, default 50. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| building | boolean | – | – |
| counterparties | array | yes | – |
| from_height | integer | – | – |
| window_blocks | integer | – | – |
No examples provided.
get_latest_blocks Latest Blocks ~74
The ten newest blocks with their size, transaction count, reward and miner.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Optional: prices in this currency instead of USD. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | yes | – |
No examples provided.
get_network_info Network Info & Mempool ~68
Current height, hashrate, and the mempool: waiting transactions, size, and projected next blocks with fee rates.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| best_block_hash | string | yes | – |
| block_count | integer | yes | – |
| hashrate | string | – | – |
| mempool | object | yes | – |
No examples provided.
get_price Price ~98
The price in USD (or another currency): the current price, or the UTC-day opening price for a past unix time.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Optional: prices in this currency instead of USD. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| unix_time | integer | – | Optional unix time for a historical price. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | integer | – | – |
| currency | string | yes | – |
| value | string | yes | – |
No examples provided.
get_rich_list Rich List ~127
The largest holders: the top 1,000 addresses by confirmed balance, with each one's share of the supply, transactions, first and last activity, and change over 24 hours and 7 days.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| page | integer | – | Page, default 1 (up to 1,000 ÷ page_size). |
| page_size | integer | – | 25, 50 or 100 (the default). |
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | yes | – |
| page | integer | yes | – |
| page_size | integer | yes | – |
| rows | array | yes | – |
| supply | string | yes | – |
| time | integer | yes | – |
| total_rows | integer | yes | – |
No examples provided.
get_transaction Transaction ~97
A transaction: confirmations, block, fee, inputs and outputs (is_change marks outputs paying back to an input address).
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | Optional: prices in this currency instead of USD. |
| hash | string | yes | The 64-character transaction ID (hash). |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| block_hash | string|null | – | – |
| block_height | integer|null | – | – |
| confirmations | integer | yes | – |
| facts | object | – | – |
| fee | string | yes | – |
| hash | string | yes | – |
| heuristic | boolean|null | – | – |
| inputs | array | yes | – |
| inputs_n | integer | – | – |
| inputs_value | string | – | – |
| kind | string|null | – | – |
| locktime | integer | – | – |
| outputs | array | yes | – |
| outputs_n | integer | – | – |
| outputs_value | string | – | – |
| price | object|null | – | – |
| size | integer | – | – |
| time | integer | – | – |
| version | integer | – | – |
| vsize | integer | – | – |
| weight | integer | – | – |
No examples provided.
get_transaction_counts Address Transaction Counts ~69
How many transactions an address has sent, received, and in total.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| received | integer | yes | – |
| sent | integer | yes | – |
| total | integer | yes | – |
No examples provided.
get_transaction_status Transaction Status ~125
A transaction's status: pending, mined, replaced (another transaction spent one of its inputs, as in a fee bump or double spend; replaced_by names it), dropped, or expired (Zcash). SoChain remembers a removal for about a day; after that, or for a transaction it never saw, the status is unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | The 64-character transaction ID (hash). |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| block_height | integer|null | yes | – |
| confirmations | integer|null | yes | – |
| hash | string | yes | – |
| network | string | yes | – |
| removed_at | integer|null | yes | – |
| replaced_ancestor | string|null | yes | – |
| replaced_by | string|null | yes | – |
| replaced_by_height | integer|null | yes | – |
| replaced_by_status | string|null | yes | – |
| status | string | yes | – |
No examples provided.
get_transactions Address Transactions ~384
An address's transactions, newest first (unconfirmed first), with the amount each one moved for the address and the price at the time (USD unless currency is given). Without filters, pages by number; with any filter (block or time range, direction), pages by cursor: pass next_cursor back until it's null (a short page with a cursor isn't the end).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| currency | string | – | Optional: prices in this currency instead of USD. |
| cursor | string | – | next_cursor from the previous page; it carries the filters. |
| direction | string | – | in: the balance went up; out: it went down (a payment with change counts once, as out). Default both. |
| from_height | integer | – | Oldest block to include. |
| from_time | string | – | Start (a date means from its first second): unix seconds, a date like 2025-12-31 (UTC) or a timestamp like 2025-12-31T23:59:59Z. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| page | integer | – | Page number (10 per page). Default 1. |
| page_size | integer | – | Rows per page, default 10. |
| to_height | integer | – | Newest block to include. |
| to_time | string | – | End (a date means to its last second): unix seconds, a date like 2025-12-31 (UTC) or a timestamp like 2025-12-31T23:59:59Z. |
| unconfirmed | string | – | Mempool transactions. Default include, or exclude when there's an end (to_height or to_time). |
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| from_height | integer|null | – | – |
| next_cursor | string|null | – | – |
| page_size | integer | – | – |
| tip_height | integer | – | – |
| to_height | integer|null | – | – |
| transactions | array | yes | – |
| unconfirmed | string | – | – |
No examples provided.
get_unspent_outputs Address Unspent Outputs ~88
The coins (unspent outputs) an address can spend, oldest first.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| page | integer | – | Page number (10 per page). Default 1. |
| Name | Type | Req | Description |
|---|---|---|---|
| outputs | array | yes | – |
No examples provided.
is_valid_address Validate an Address ~66
Whether a string is a valid address on the network.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | An address on that network. |
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| Name | Type | Req | Description |
|---|---|---|---|
| is_valid | boolean | yes | – |
No examples provided.
search Search ~91
Classify a search string: an address, a transaction ID, a block hash or a block height.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | yes | Network: BTC, LTC, DOGE, ZEC, BTCTEST, LTCTEST, DOGETEST or ZECTEST. |
| query | string | yes | An address, a transaction ID or block hash (64 hexadecimal characters), or a block height (commas allowed). |
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | – | – |
| kind | string | yes | – |
| value | string | – | – |
No examples provided.
How do I install the SoChain MCP server?
SoChain is a hosted endpoint at https://sochain.com/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 · sochain.com
claude mcp add --transport http com-sochain-mcp 'https://sochain.com/mcp'
What is the SoChain MCP server?
SoChain is an MCP server listed in the public MCP registry as com.sochain/mcp. Live Bitcoin, Litecoin, Dogecoin and Zcash data: balances, transactions, blocks, fees, prices. This page covers its hosted endpoint (https://sochain.com/mcp).
Is the SoChain MCP server safe to use?
SoChain scores 74 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 SoChain MCP server expose?
SoChain exposes 20 tools: get_balance, get_address_summary, get_transaction_counts, get_transactions, get_unspent_outputs, and 15 more. Their descriptions and schemas cost roughly 2,507 tokens of context every time the server is loaded.
Does the SoChain MCP server require authentication?
No. We connected to SoChain without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SoChain MCP server still maintained?
SoChain is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.