Marvnor

io.github.wendelxiaPublished by GitHub account wendelxiav1.0.0Updated Oct 24, 2026

Hosted agent memory with record-based verification, conflict detection, correction and deletion.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Gives an assistant hosted agent memory with record-based verification, conflict detection, correction and deletion.

What you can do
Provides a hosted memory store for an agent, keeping records that the assistant can rely on across sessions. It supports record-based verification, conflict detection, correction and deletion of stored memories. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Worth adding when an assistant needs persistent memory that survives across conversations and the user wants conflicts between stored records detected and resolved. Less useful for one-off sessions or when memory must stay entirely on the local machine.
Requirements
A remote streamable HTTP endpoint at Authentication is required: a bearer token supplied in the Authorization header, using a Marvnor API key. No local runtime or packages are needed. Network access to the endpoint is required.
Before you install
The server is hosted and requires a bearer API key sent in the Authorization header, so the key is a secret to protect. Memory records are stored on a third-party service, so avoid putting sensitive or regulated data into it. It supports correction and deletion, which change or remove stored records.

Installation

In SourceWeft

  1. Open Marvnor in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.wendelxia%2Fmarvnor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "marvnor": {
      "type": "http",
      "url": "https://api.marvnor.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 14, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.