Verde

ai.getverdePublished by getverde.aiOfficial publisherv1.0.0Updated Nov 7, 2026

Shared, permission-aware memory for teams and their AI: recall, save, and keep knowledge current.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server giving assistants shared, permission-aware team memory to recall, save, and keep knowledge current.

What you can do
  • Recall stored team knowledge through the assistant
  • Save new information into shared memory
  • Keep existing knowledge up to date
  • Apply permission-aware access to what is recalled and saved
When to use it
Useful when a team wants its assistants to work from a common, maintained body of knowledge instead of isolated context, and when recalled information must respect per-user permissions.
Requirements
A remote endpoint at the provider's site, connected over streamable HTTP. Authentication is required via OAuth; no environment variables or headers are declared.
Before you install
Content saved to shared memory is visible to others in the team according to its permission model, so avoid storing secrets or sensitive material. The server can write and update stored knowledge, and memory data is held by the third-party provider.

Installation

In SourceWeft

  1. Open Verde in the dashboard and add it to a workspace.
  2. Connect the required 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/ai.getverde%2Fverde/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "verde": {
      "type": "http",
      "url": "https://www.getverde.ai/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 7, 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.