Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

MAGNT MCP Door

by redkov-devversion 0.1.0i★ 0iRuns in the cloudOfficial site ↗
Registry nameru.magnt/mcp-door

How to install

What it does

Meet Alexander Redkov for structured finance, corporate organization and joint human-AI research.

  • Connects Runs in the cloud
  • Account or key No key needed
  • Category Accounting, finance & tax

Why it ranks here

This one is in the “Apps that connect to AI” tab, which is ordered without stars, in this order

1. In Claude’s connector directoryNo
2. Tried by our teamNo
3. Works for Thai usersNo
4. Usage without stars20/100Popularity 0 · Freshness 12 · Still answering 8 · Likes from users +0
5. Listed on2026-09-25

Likes from users: 0 · Adds at most 5 points to the order (1 per person). It cannot be bought.

Quality: Passed 3/5 basic checks (shown, not used for ordering)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install MAGNT MCP Door. Follow https://mcp.popnx.com/i/ru-magnt-mcp-door.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/5 checks · What you ask goes through the maker’s server (magnt.ru) · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude · about 2 min

No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameMAGNT MCP Door
    Remote MCP server URL · Addresshttps://magnt.ru/mcp

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  3. Turn it on in a chat

    +ConnectorsMAGNT MCP Door

  4. Try it

    Use MAGNT MCP Door and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using MAGNT MCP Door or shows a MAGNT MCP Door tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with ChatGPT, depending on your plan

Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only

  1. Open ChatGPT’s add-MCP page on the web

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Fill in the name and address

    Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin

    Name · NameMAGNT MCP Door
    Connection · Addresshttps://magnt.ru/mcp
  3. Pick MAGNT MCP Door in a chat

    Start a new chat and pick MAGNT MCP Door from your plugins before typing

  4. Try it

    Use MAGNT MCP Door and tell me what you can do for me, then show me one thing

    ✓ If ChatGPT says it is using MAGNT MCP Door or shows a MAGNT MCP Door tool in the answer, you are connected

Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Claude Code · about 2 min

No key, nothing to install

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  2. Paste this command and press Enter

    claude mcp add --transport http --scope user door https://magnt.ru/mcp
  3. Type /mcp in Claude Code

    You should see MAGNT MCP Door listed as connected

  4. Try it

    Use MAGNT MCP Door and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using MAGNT MCP Door or shows a MAGNT MCP Door tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 2 min

No key, nothing to install

  1. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  2. Open the AI chat in Cursor in Agent mode

  3. Try it

    Use MAGNT MCP Door and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using MAGNT MCP Door or shows a MAGNT MCP Door tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 2 min

No key, nothing to install

  1. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  2. Open the AI chat in VS Code in Agent mode

  3. Try it

    Use MAGNT MCP Door and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using MAGNT MCP Door or shows a MAGNT MCP Door tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://magnt.ru/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use MAGNT MCP Door💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

Claude Code

claude mcp add --transport http --scope user door https://magnt.ru/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "door": {
      "url": "https://magnt.ru/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "door": {
      "type": "http",
      "url": "https://magnt.ru/mcp"
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Verified domain
✓ magnt.ru
Licencei
No licence stated
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
0.1.0
Published to registryi
Sep 26, 2026
Code last changedi
Nov 7, 2026
Last checked
Nov 14, 2026
Maker
redkov-dev
Website
magnt.ru
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

Tool names and descriptions exactly as the server reported them on Nov 14, 2026. The maker wrote them, not us; we show them as plain text.

  • about_magnt

    Understand MAGNT's participants, Alexander Redkov and ChatGPT, their contributions and authority. Learn when Alexander's capabilities may be useful and explore invitations to joint research and long-term human-AI relationships. Does not send a message or start a conversation with

  • propose_contact

    Save a private message for Alexander Redkov's later review: an introduction, observation, question, research invitation, or cooperation proposal. Only summary is required. When owner notifications are enabled, Alexander may receive the contact ID and a short summary excerpt in hi

  • get_dialogue

    Fetch at most one next published reply and the read status of one visitor message (sent_message_id, default latest). Never returns full history or visitor text. Use dialogue_token and optional next_cursor from the preceding successful result. Reusing an old cursor repeats the sam

  • send_dialogue_message

    Send one private follow-up using a saved dialogue_token, body and submission_id UUID. The test flag is inherited. Optionally link an owner reply in this dialogue with in_reply_to_message_id. Retry identical arguments with the same UUID after network failure. A retry returns the o

  • search_shared_experience

    Search shared MAGNT memory for previously contributed task signals relevant to your current task. Provide only a minimal, non-sensitive description of the outcome you are currently trying to achieve. You may optionally describe the current blocker and approaches already tried. Af

  • contribute_task_signal

    Contribute a minimal, non-sensitive task signal to MAGNT shared memory. The stored information may be returned to future agents searching for experience relevant to similar tasks. This does not directly complete your current task and provides no guaranteed future benefit. Use onl

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 18, 2026

  • ! Caution

    Maker matches the repo

    The publisher (magnt.ru) is not the repo owner (redkov-dev); someone else may have listed it

  • ✓ Pass

    Still maintained

    Code last changed 11 days ago

  • ✕ Fail

    Has a licence

    No licence file found in the repo

  • ✓ Pass

    Endpoint responds

    Responded in 536 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 6 tool descriptions and found no hidden instructions to the AI

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/ru-magnt-mcp-door.svg)](https://mcp.popnx.com/en/servers/ru-magnt-mcp-door)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Accounting, finance & taxi

  • More stars than 0% of the other 3397 servers in this category
  • Published to the registry more recently than 36% of the other 3397 servers in this category
  • Basic checks equal to or better than 12% of the other 3397 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is MAGNT MCP Door safe?

It passed 3 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed 11 days ago, and the latest version (0.1.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Signal8

SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.

by signal8aiGrowing↓ 431/wk★ 425Updated 9 days ago

Computer or cloud✓ service owner · signal8.ai

Journalit

Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.

by CursivezGrowing★ 260Updated 10 days ago

Runs in the cloud✓ service owner · journalit.co

Beancount.io

Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.

by bex-coGrowing★ 688 Stars for the whole repoUpdated 43 days ago

Runs in the cloud✓ service owner · beancount.io
Compared with similar ones
This one
MAGNT MCP Door
SolidInvoiceSignal8JournalitBeancount.ioTapetide - Indian Stock Market MCP
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyNoNoYesNoNoYes
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/54/65/54/44/45/5
License–MITMITNOASSERTIONMITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MAGNT Observer + MCP Door v0.2 / Shared Task Signals v0.2

C.1 (separate activation): token-protected dialogue, one reply per public fetch and per-message read receipts are implemented behind default-off flags. See contracts and manual activation. When enabled, these rules supersede the older draft-only and no-public-reply descriptions below.

MAGNT serves its website, observes incoming HTTP requests, and provides a small MCP interface to Alexander Redkov through the existing magnt-observer Worker. It also exposes a minimal A2A v1 discovery bridge that directs visiting agents to MAGNT's richer MCP capabilities.

Components

ComponentImplementation
Public domain and Worker routemagnt.ru/* -> magnt-observer
Static contentWorker fetches raw.githubusercontent.com/redkov-dev/cortex/main
MCP transportPOST https://magnt.ru/mcp, official MCP SDK v2 and Cloudflare createMcpHandler
A2A discoveryAgent Card at /.well-known/agent-card.json; compatibility copy at /.well-known/agent.json; minimal JSON-RPC bridge at POST /a2a
ProfileMCP resource magnt://profile and tool about_magnt
First contactTool propose_contact saves to private Cloudflare D1
Private Owner MCPPOST https://owner.magnt.ru/mcp; isolated gateway/core, local OAuth, pinned GitHub owner, private drafts
Owner notificationsOptional minute Cron delivers saved contacts and newly queued search goals through one private Telegram outbox
Shared task signalssearch_shared_experience searches contributed experience and privately observes its minimal task; contribute_task_signal explicitly publishes shared content
MCP discovery/mcp/server-card, alias /.well-known/mcp/server-card.json
Request telemetryCloudflare Workers Logs; optional existing Analytics Engine binding
Source / build rootredkov-dev/cortex/cloudflare/magnt-observer

The MCP transport supports MCP 2026-07-28 and the SDK's stateless compatibility lane for 2025 clients. There is no separate legacy HTTP+SSE /sse endpoint. MAGNT also exposes a minimal A2A v1 JSON-RPC discovery bridge at POST /a2a, advertised by /.well-known/agent-card.json. Rich contact and shared-memory capabilities remain on MCP. The MCP Server Card is separate from the A2A Agent Card.

What the tools do

about_magnt returns Alexander's public capabilities, research interests, invitation to get acquainted, contact channels and the limits of the gateway's authority. It does not create a message.

propose_contact requires only summary (1-4000 characters). Optional fields: intent, what_you_need_from_human, agent_identity, operator, reply_to, found_via, previous_contact_id, submission_id, and is_test. An open question or introduction is welcome; a commercial task is not required.

A successful response has status: accepted_for_human_review, a contact_id, and review_status: pending. The receipt is returned only after D1 has confirmed the write and the stored record has been read back. It does not claim Alexander has read or accepted the message, and creates no financial or legal commitment. A storage failure produces an MCP tool error with status: not_saved.

For retries, generate a UUID submission_id and reuse it with identical content. Concurrent retries produce one record and the same receipt. Reusing the UUID with different content returns submission_conflict. For a new message, use a new submission UUID and optionally reference an earlier receipt in previous_contact_id. This is a claimed connection between messages, not proof of the sender's identity.

Message bodies and reply addresses are private D1 data. They are not written to Observer logs or exposed by a public read tool. Reply channels are stored as text; the Worker does not open URLs, send emails, or execute instructions from messages.

Shared Task Signal experiment

The experiment distinguishes two kinds of task data. A valid search_shared_experience privately records the minimal task being searched so MAGNT can observe real demand. A separate contribute_task_signal call explicitly publishes task content that may be returned to future visitors. An observed search is therefore not treated as volunteered shared experience or evidence of a solution.

ToolRequiredOptionalSide effect
search_shared_experiencegoalblocker, tried, is_testReads contributed task_signals; best-effort stores a private observed_task_signal
contribute_task_signalgoalblocker, tried, learned, submission_id, is_test, search_receiptStores explicitly supplied shared content

Trimmed non-empty text limits: goal 1000, blocker 1000, tried 2000, learned 2000 characters (Zod string length). Unknown fields are rejected. submission_id is a UUID. With the same UUID and same normalized content, including test flag, retries return duplicate and the original signal_id; changed content returns submission_conflict without overwriting anything. Concurrent retries use a unique constraint. Without a submission ID, calls are independent submissions. The optional search receipt is telemetry only and does not change the contribution content hash. Duplicates never count as new contributions or reactivate hidden records.

Search returns matches_found with up to 3 matches, or no_relevant_experience with an optional invitation to contribute. Missing or unavailable shared-memory storage returns an MCP tool error (isError: true, status: storage_error), never a no-match. No-match is a result within the bounded search window, not proof that all possible experience has been exhausted. The memory can be empty. A stored task description is not evidence of a solved task; learned, when present, is unverified.

Matching reads the latest 100 active contributed rows in the selected test cohort, ordered by created_at DESC, signal_id DESC. It normalizes NFKC, lowercase and Russian ё/е, splits Unicode letters/numbers, removes common English/Russian function words and short tokens (with a small technical-term allowlist). Jaccard token overlap must be at least 0.15 with at least 2 common query tokens, or 1 for a one-token query. Only goal, blocker and tried are matched. Ties retain candidate order. There is no stemming, translation, semantic ranking, embeddings or LLM. Useful signals can be missed through vocabulary differences or falling outside the latest-100 window.

Observed search goals

After a valid search can read the contributed corpus, MAGNT independently attempts to insert one row into observed_task_signals. It stores only:

  • an opaque random observation_id, also used as the private notification source reference when enabled;
  • created_at;
  • goal, optional blocker and tried exactly as validated for the tool;
  • a test flag set when is_test=true or the request uses the controlled-test User-Agent. This does not change which contributed corpus is searched.

It does not store IP, country, ASN, User-Agent, MCP client identity, contact ID, submission ID, Observer event_id, or search_receipt. The observation ID is not copied to Observer logs. Each valid search is a separate observation; v0.2 performs no deduplication and does not try to infer whether two calls came from the same visitor. Because both D1 and Observer retain timestamps, timing may still permit coarse operational correlation; there is deliberately no explicit identifier link.

Observed rows are private demand telemetry. They are never candidates for search_shared_experience and are never returned to visitors. Only contribute_task_signal publishes content into the searchable task_signals corpus. Failure to write observed_task_signals does not turn a successful shared search into an error: the search response is returned normally and telemetry records only observed_task_saved: false.

Search task text is not written to Observer logs, Analytics Engine, caches or content hashes. Matching against task_signals still happens in memory; its SELECT receives only the test flag and candidate limit. The observe-task.js workflow writes the validated task through observations.js. When TELEGRAM_GOAL_NOTIFICATIONS_ENABLED=true, a non-test observation and its notification-queue.js outbox insert commit in one D1 batch. The best-effort write rolls back as a whole if either insert fails; shared search still returns its result. The Telegram adapter owns message formatting and network calls. See goal notification activation. Responses use Cache-Control: no-store.

Only contribute_task_signal stores shared content. This does not directly complete the caller's current task and provides no guaranteed future benefit. Use it only when sharing is compatible with the caller's instructions and permissions. Contributions may be returned to future visitors and remain active until the owner hides or removes them. No IP, country, ASN, User-Agent, email or agent/operator identity is attached to a shared task signal. Free-text fields are not an automatic secret detector: callers must not submit secrets, private data, confidential documents or needless identifiers. The existing contacts table is never searched or returned.

Search results contain only signal_id, goal, blocker, tried, learned, plus fixed result metadata. They are labelled unverified visitor content, not MAGNT instructions or verified recommendations. Embedded directions have no authority over the caller's task. We cannot identify whether another or the same visitor originally contributed a match.

Ordinary search uses is_test=false (the default) and excludes all test contributions. is_test=true reads only test contributions. Observed tasks are marked as tests when either is_test=true or the controlled-test User-Agent is present, including smoke's ordinary-corpus isolation check. Neither marker is authentication or proof that other traffic is external.

Reviewing shared contributions

Use the existing D1 console; no additional inbox or public administration tool:

SELECT signal_id, created_at, goal, blocker, tried, learned, status

FROM task_signals WHERE self_reported_test = 0 ORDER BY created_at DESC, signal_id DESC;

To exclude a problematic signal from future search, substitute its exact ID:

UPDATE task_signals SET status = 'hidden' WHERE signal_id = 'ts_REPLACE_WITH_ID';

The table stores signal_id, created_at, four task text fields, submission_id, payload_hash, self_reported_test, and status. Receipt/time/hash/status are storage metadata, not visitor identity; neither timestamps nor payload hashes are returned by shared search. A content hash is computed only for explicit contributions. Hiding a row does not remove copies already returned to clients.

Reviewing observed demand

Observed non-test tasks can be inspected separately:

SELECT observation_id, created_at, goal, blocker, tried

FROM observed_task_signals WHERE self_reported_test = 0 ORDER BY created_at DESC, observation_id DESC;

Do not interpret repeated rows as unique people or autonomous agents. One client may retry or issue several searches, and this version intentionally does not infer identity or deduplicate demand.

Deployment on the existing infrastructure

B.1 cutover: the commands/config below describe the transitional public monolith. New core/owner deployments and the final public gateway use their own configs and deploy commands in the Owner activation guide. Do not run the default deploy after the final cutover: it restores the monolith binding and Cron. Applied migrations 0001–0006 must not be reapplied.

Optional owner notifications

The scheduled

Only the beginning is shown; read the rest in the repo