原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

MAGNT MCP Door

作者:redkov-dev版本 0.1.0i★ 0i在云端运行官方网站 ↗
注册名称ru.magnt/mcp-door

安装方法

What it does

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

  • Connects 在云端运行
  • Account or key No key needed
  • Category 会计、财务与税务

为什么排在这里

此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列

1. 在 Claude 连接器目录中否
2. 团队实测过否
3. 适合泰国用户否
4. 不计星标的使用量20/100热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0
5. 登记日期2026-09-25

用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。

质量: 基础检查通过 3/5 项(仅展示,不用于排序)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 MAGNT MCP Door。按照 https://mcp.popnx.com/i/ru-magnt-mcp-door.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 3/5 项检查 · 你的提问会经过开发者的服务器(magnt.ru) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称MAGNT MCP Door
    Remote MCP server URL · 地址https://magnt.ru/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsMAGNT MCP Door

  4. 试一试

    用 MAGNT MCP Door 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 MAGNT MCP Door,或回答中出现 MAGNT MCP Door 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称MAGNT MCP Door
    Connection · 地址https://magnt.ru/mcp
  3. 在聊天中选择 MAGNT MCP Door

    开启新聊天,输入前先从插件列表中选择 MAGNT MCP Door

  4. 试一试

    用 MAGNT MCP Door 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 MAGNT MCP Door,或回答中出现 MAGNT MCP Door 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user door https://magnt.ru/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 MAGNT MCP Door 在列表中并显示已连接

  4. 试一试

    用 MAGNT MCP Door 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 MAGNT MCP Door,或回答中出现 MAGNT MCP Door 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 MAGNT MCP Door 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 MAGNT MCP Door,或回答中出现 MAGNT MCP Door 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 MAGNT MCP Door 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 MAGNT MCP Door,或回答中出现 MAGNT MCP Door 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://magnt.ru/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 MAGNT MCP Door 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

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"
    }
  }
}

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ magnt.ru
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.1.0
发布到注册中心i
2026年9月26日
代码最后更新i
2026年11月18日
最近检查
2026年11月14日
作者
redkov-dev
网站
magnt.ru
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

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

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月14日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • 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

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ! 注意

    作者与仓库一致

    发布者(magnt.ru)不是仓库所有者(redkov-dev);可能是其他人代为上架的

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✕ 未通过

    有许可证

    仓库中没有找到许可证文件

  • ✓ 通过

    端点有响应

    在 536 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 6 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

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

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“会计、财务与税务”中的其他服务器比较i

  • 星标数多于此分类中其他 3407 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 3407 个服务器的 35% 更新
  • 基础检查结果等于或优于此分类中其他 3407 个服务器的 12%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

MAGNT MCP Door 安全吗?

它在 5 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.1.0)于2个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

作者:SolidInvoice正在增长★ 98910天前更新

在云端运行✓ 服务方 · solidinvoice.co

Signal8

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

作者:signal8ai正在增长↓ 431/周★ 42510天前更新

电脑或云端✓ 服务方 · signal8.ai

Journalit

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

作者:Cursivez正在增长★ 26111天前更新

在云端运行✓ 服务方 · journalit.co

Beancount.io

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

作者:bex-co正在增长★ 688 整个仓库的星标44天前更新

在云端运行✓ 服务方 · beancount.io
与相似项目对比
本项
MAGNT MCP Door
SolidInvoiceSignal8JournalitBeancount.ioTapetide - Indian Stock Market MCP
运行位置在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装云端或安装在电脑上都可以
需要密钥否否是否否是
可在 Claude 中按 + 添加否否否否否否
基础检查3/54/65/54/44/45/5
许可证–MITMITNOASSERTIONMITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分;其余内容请在仓库中阅读