Motiv Fleet

io.github.vilogyPublished by GitHub account vilogyv1.0.0Updated Oct 24, 2026

DeFi MCP fleet: oracle, security audit, treasury yield, QA attestation, and compute tools on Base.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

A remote DeFi MCP fleet on Base offering oracle, security audit, treasury yield, QA attestation and compute tools to an AI assistant.

What you can do
Access a fleet of DeFi-related tools on the Base network, grouped as oracle, security audit, treasury yield, QA attestation and compute services. The manifest lists no individual tools, so the exact operations and their inputs are not documented here.
When to use it
Consider it when working on Base-based DeFi tasks that need oracle data, contract security auditing, treasury yield information, attestation or compute services through an assistant.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. Authentication is OAuth and required, so the user must complete an OAuth sign-in with the provider.
Before you install
It is a DeFi service on Base, so tools may touch on-chain data, treasury or yield positions and could involve transactions or spending; confirm what each tool does before use. The manifest lists no tools, so capabilities cannot be verified in advance. OAuth grants the server access tied to your account.

Installation

In SourceWeft

  1. Open Motiv Fleet 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/io.github.vilogy%2Fmcp-fleet/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": {
    "motiv-fleet": {
      "type": "http",
      "url": "https://motiv-mcp-fleet.mcp.xpay.sh/mcp"
    }
  }
}

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.0LatestSep 16, 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.