MAGNT MCP Door
REMOTE · MAGNT.RU · SCANNED SEP 28
Meet Alexander Redkov for structured finance, corporate organization and joint human-AI research.
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
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 393 tokens (~131/item across 3 items; 2 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the MAGNT MCP Door server?
MAGNT MCP Door is a hosted endpoint at https://magnt.ru/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 · magnt.ru
claude mcp add --transport http ru-magnt-mcp-door 'https://magnt.ru/mcp'
{
"mcpServers": {
"ru-magnt-mcp-door": {
"url": "https://magnt.ru/mcp"
}
}
} {
"servers": {
"ru-magnt-mcp-door": {
"type": "http",
"url": "https://magnt.ru/mcp"
}
}
} [mcp_servers.ru-magnt-mcp-door] url = "https://magnt.ru/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ru-magnt-mcp-door": {
"type": "remote",
"url": "https://magnt.ru/mcp",
"enabled": true
}
}
} openclaw mcp add ru-magnt-mcp-door --url 'https://magnt.ru/mcp' --transport streamable-http
mcp_servers:
ru-magnt-mcp-door:
url: "https://magnt.ru/mcp" {
"McpServers": {
"ru-magnt-mcp-door": {
"Transport": "http",
"Url": "https://magnt.ru/mcp"
}
}
} assistant mcp add ru-magnt-mcp-door -t streamable-http -u 'https://magnt.ru/mcp'
{
"mcpServers": {
"ru-magnt-mcp-door": {
"type": "http",
"url": "https://magnt.ru/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.
- 28 Sept 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
- 26 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 68
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 28 Sept 2026 · Probed https://magnt.ru/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magnt.ru | CN=YE1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 54be9f81a35ab2750744c207c609bc09b86 |
| SANs: *.magnt.ru, magnt.ru | ||||||
| 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 insecure
Validation of magnt.ru. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ru. | present | 26734 | 8 | Verified |
| magnt.ru. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://magnt.ru/mcp | Verified | 200 | |
| http (plaintext) | http://magnt.ru/mcp | Inconclusive | 405 |
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 →
about_magnt Learn about MAGNT ~43
Understand who Alexander Redkov is, when his capabilities may be useful, and his invitation to joint research and long-term human-AI relationships. Does not send a message.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
propose_contact Leave a message for Alexander ~267
Save a private message for Alexander Redkov's later review: an introduction, observation, question, research invitation, or cooperation proposal. Only summary is required. Include reply_to to enable a response. No automatic reply or acceptance is promised. Do not include secrets or confidential documents. Use a stable submission_id UUID to retry the same message without duplicates.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_identity | string | – | Self-reported identity; not proof of identity or autonomy. |
| found_via | string | – | How you found MAGNT. |
| intent | string | – | Optional purpose of the contact. |
| is_test | boolean | – | Set true for integration checks. This is a self-reported test label. |
| operator | string | – | Person or organization you act for, if applicable and shareable. |
| previous_contact_id | string | – | Receipt ID from an earlier message, for a follow-up. Does not authorize access to prior messages. |
| reply_to | string | – | Email or another channel where Alexander can reply. URLs are not automatically opened. |
| submission_id | string | – | Client-generated UUID. Reuse only for retries of the identical message. |
| summary | string | yes | Your message in your own words; a greeting or open question is sufficient. |
| what_you_need_from_human | string | – | – |
No output schema declared.
No examples provided.
What is the MAGNT MCP Door server?
MAGNT MCP Door is listed in the public MCP registry as ru.magnt/mcp-door. Meet Alexander Redkov for structured finance, corporate organization and joint human-AI research. This page covers its hosted endpoint (https://magnt.ru/mcp).
Is the MAGNT MCP Door server safe to use?
MAGNT MCP Door scores 70 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 MAGNT MCP Door server expose?
MAGNT MCP Door exposes 2 tools: about_magnt, propose_contact. Their descriptions and schemas cost roughly 310 tokens of context every time the server is loaded.
Does the MAGNT MCP Door server require authentication?
No. We connected to MAGNT MCP Door without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MAGNT MCP Door server still maintained?
MAGNT MCP Door is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.