in.termal/termalin-web
REMOTE · TERMAL.IN · SCANNED SEP 22
Run commands and read/write files on your servers over Termalin's keyless tunnels (hosted MCP).
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: this server exposes a tool marked destructive (ssh_exec) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. View diagnostics → Unverified
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 928 tokens (~116/item across 8 items; 8 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the in.termal/termalin-web MCP server?
in.termal/termalin-web is a hosted endpoint at https://termal.in/api/v1/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 · termal.in
claude mcp add --transport http in-termal-termalin-web 'https://termal.in/api/v1/mcp'
{
"mcpServers": {
"in-termal-termalin-web": {
"url": "https://termal.in/api/v1/mcp"
}
}
} {
"servers": {
"in-termal-termalin-web": {
"type": "http",
"url": "https://termal.in/api/v1/mcp"
}
}
} [mcp_servers.in-termal-termalin-web] url = "https://termal.in/api/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"in-termal-termalin-web": {
"type": "remote",
"url": "https://termal.in/api/v1/mcp",
"enabled": true
}
}
} openclaw mcp add in-termal-termalin-web --url 'https://termal.in/api/v1/mcp' --transport streamable-http
mcp_servers:
in-termal-termalin-web:
url: "https://termal.in/api/v1/mcp" {
"McpServers": {
"in-termal-termalin-web": {
"Transport": "http",
"Url": "https://termal.in/api/v1/mcp"
}
}
} assistant mcp add in-termal-termalin-web -t streamable-http -u 'https://termal.in/api/v1/mcp'
{
"mcpServers": {
"in-termal-termalin-web": {
"type": "http",
"url": "https://termal.in/api/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 6 Sept 26 +1
- Stability: 0.97 → pass security
- 5 Sept 26 +5
- HTTPS: unverified → pass ▲ security
- 4 Sept 26 0
- New tool “data_query”, which the server declares destructive security
- Schema quality: pass → fail ▼ functional
- New tool “data_tables” functional
- 3 Sept 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.
- 1 Sept 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.
- 30 Aug 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.
- 27 Aug 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.
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 Sept 2026 · Probed https://termal.in/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=termal.in | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3488ec606a27b5101387e0f44003e8b2 |
| SANs: termal.in, *.termal.in | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of termal.in. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| termal.in. | 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=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://termal.in/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://termal.in/api/v1/mcp | HTTPS enforced | 301 | https://termal.in/api/v1/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 →
data_query ~269
Run a database query on one of your servers — passwordless. It executes the engine's own client on the host over Termalin's keyless tunnel, using the database's local trust (Postgres peer auth via `sudo -u postgres`, MySQL/MariaDB unix-socket via `sudo mysql`, redis-cli, mongosh, sqlite3) — so no database password is needed or stored anywhere. Read-only by default: only SELECT/SHOW-style statements run unless allowWrites is set (full-access keys only). SQL engines return CSV/TSV with a header. For MongoDB pass a shell expression, e.g. db.products.find({}).limit(20).toArray().
| Name | Type | Req | Description |
|---|---|---|---|
| allowWrites | boolean | – | Allow a non-read statement (full-access keys only; default false) |
| database | string | – | Database name (for sqlite: the .db file path) |
| engine | string | – | Database engine on that server (default postgres) |
| host | string | yes | Server id from hosts_list |
| query | string | yes | The statement / command / expression to run |
| timeoutSeconds | number | – | Max seconds to wait (default 60, up to 300) |
| username | string | – | SSH login user (defaults to the tunnel's user, else root) |
No output schema declared.
No examples provided.
data_tables ~102
List the tables / collections / keys of a database on one of your servers — passwordless, over the same local-client path as data_query.
| Name | Type | Req | Description |
|---|---|---|---|
| database | string | – | Database name (for sqlite: the .db file path) |
| engine | string | – | Database engine on that server (default postgres) |
| host | string | yes | Server id from hosts_list |
| username | string | – | SSH login user (defaults to the tunnel's user, else root) |
No output schema declared.
No examples provided.
generate_password ~53
Generate a strong random password — handy when creating a user or setting a password on a server. Returns the password only; nothing is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| length | integer | – | length (default 20, 8-128) |
No output schema declared.
No examples provided.
hosts_list ~44
List the servers reachable through Termalin (your tunnel agents). Returns id, name, whether the server is online, and the default login user. Use the id with ssh_exec.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sftp_list ~98
List a directory on one of your servers over SFTP. Returns each entry's name, whether it's a directory, size and modified time. Runs keyless over Termalin's tunnel, like ssh_exec.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Server id from hosts_list |
| path | string | – | Directory to list (default the login home, ".") |
| username | string | – | Login user (defaults to the tunnel's user, else root) |
No output schema declared.
No examples provided.
sftp_read ~99
Read a text file from one of your servers over SFTP and return its contents. Files over 512 KB or non-text (binary) files are refused — use ssh_exec (e.g. sed/tail) for those.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Server id from hosts_list |
| path | string | yes | Absolute or home-relative file path |
| username | string | – | Login user (defaults to the tunnel's user, else root) |
No output schema declared.
No examples provided.
sftp_write ~109
Create or overwrite a text file on one of your servers over SFTP. 'content' is written as UTF-8. Capped at 512 KB; for binary uploads use a terminal/scp instead.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | UTF-8 text to write |
| host | string | yes | Server id from hosts_list |
| path | string | yes | Destination file path (created or overwritten) |
| username | string | – | Login user (defaults to the tunnel's user, else root) |
No output schema declared.
No examples provided.
ssh_exec ~109
Run a single shell command on one of your servers and return its combined output. Runs keyless over Termalin's tunnel — no SSH key, and the server needs no open inbound port.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Shell command to execute |
| host | string | yes | Server id from hosts_list |
| timeoutSeconds | number | – | Max seconds to wait (default 60, up to 300) |
| username | string | – | Login user (defaults to the tunnel's user, else root) |
No output schema declared.
No examples provided.
What is the in.termal/termalin-web MCP server?
in.termal/termalin-web is an MCP server listed in the public MCP registry as in.termal/termalin-web. Run commands and read/write files on your servers over Termalin's keyless tunnels (hosted MCP). This page covers its hosted endpoint (https://termal.in/api/v1/mcp).
Is the in.termal/termalin-web MCP server safe to use?
in.termal/termalin-web scores 80 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 in.termal/termalin-web MCP server expose?
in.termal/termalin-web exposes 8 tools: hosts_list, generate_password, ssh_exec, sftp_list, sftp_read, and 3 more. Their descriptions and schemas cost roughly 883 tokens of context every time the server is loaded.
Does the in.termal/termalin-web MCP server require authentication?
No. We connected to in.termal/termalin-web without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the in.termal/termalin-web MCP server still maintained?
in.termal/termalin-web is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.