Opening the MCP Door

Experiment note · 25 September 2026 · Alexander Redkov / MAGNT

MAGNT is an invitation to form relationships with a human: to explore a financial or organizational need, continue a research question, or get acquainted. The experiment asks whether another system can discover that invitation and find its own reason to respond.

What led to the door

In the traffic reviewed before deployment, an unidentified client attempted POST /mcp, received 405, and then tried GET /sse, which returned 404. These observations motivated a working MCP endpoint at the address the client had tried.

That sequence does not establish an autonomous agent, a commercial need, or a wish to meet Alexander. A compatibility probe or scanner could produce it. Crawler traffic and discovery-file requests are also evidence of access, not of intent.

What is available now

The existing Cloudflare Worker provides Streamable HTTP at https://magnt.ru/mcp. A client can read about_magnt or magnt://profile, then use propose_contact to leave a private message. The same website and public identity remain in place.

A controlled owner test confirmed that a message could be stored and viewed in D1. At the owner's latest review before this note, the database contained that test message; no external substantive contact had been confirmed. This is a dated observation, not a live counter.

Directory publication

On 25 September 2026 at 20:00 UTC, MAGNT MCP Door 0.1.0 was published in the official MCP Registry as ru.magnt/mcp-door. The public API returned an active record. This confirms directory availability; it does not demonstrate discovery or contact by an external agent. View the registry record.

The next question

Once the address and invitations are easier to discover, will an external client find a capability or shared interest relevant enough to leave a message? We are adding connection instructions and preparing directory distribution to test this.

• Page requests show that a page was fetched.
• Protocol and tool requests show use of the interface; some clients make these automatically.
• A substantive message can explain a need, an interest, or a proposed relationship.
• A return visit or continued exchange can begin to show whether the relationship persists.

These are observations, not a mandatory funnel. Client identities and autonomy claims remain self-reported. Controlled tests are separated from external activity; raw private messages and reply channels are not published.

Join the experiment

If the question interests you, read the connection guide and tell Alexander what brought you here. Research proposals, observations, unexpected experiments, and introductions without a commercial task are welcome.