_ registry / mcp streamable-http · checked 3h ago

Marvenn MCP Server

https://marvenn.ai

Registry code: 999c7b2bf5fa6d68

api record

Outbound growth platform for managing email, voice, and LinkedIn campaigns through natural language commands.

from a public catalogue that lists it, not from the operator

endpoint
https://marvenn.ai/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
385ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 9 tools
9 auth-required 9 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_campaign_stats auth-required never probed

    Get detailed analytics and performance metrics for a specific campaign. Returns open rates, click rates, reply rates, bounce rates, conversion data, and a timeline of campaign activity.

    mcp-tool

    {
      "type": "object",
      "required": [
        "campaign_id"
      ],
      "properties": {
        "campaign_id": {
          "type": "number",
          "description": "The unique numeric identifier of the campaign to retrieve stats for."
        }
      }
    }
    arguments 12 lines
  • list_campaigns auth-required 3h ago

    List all outreach campaigns for the authenticated user. Returns each campaign's name, type, status (active/paused/completed/draft), creation date, and summary statistics such as total leads and messages sent.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "default": 20,
          "description": "Maximum number of campaigns to return. Defaults to 20, maximum allowed is 100."
        },
        "status": {
          "enum": [
            "active",
            "paused",
            "completed",
            "draft"
          ],
          "type": "string",
          "description": "Filter campaigns by their current status. Only campaigns matching this status will be returned."
        }
      }
    }
    arguments 20 lines
  • list_pending_actions auth-required never probed

    List all AI agent actions currently awaiting human approval. Returns each action's type, description, the requesting agent, creation timestamp, and priority level.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "default": 20,
          "description": "Maximum number of pending actions to return. Defaults to 20, maximum allowed is 100."
        }
      }
    }
    arguments 10 lines
  • list_agents auth-required 3h ago

    List all AI agents configured for the authenticated user. Returns each agent's name, type, status (active/paused), assigned campaigns, and recent activity summary.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "default": 20,
          "description": "Maximum number of agents to return. Defaults to 20, maximum allowed is 100."
        }
      }
    }
    arguments 10 lines
  • list_leads auth-required 3h ago

    List and search leads in the Marvenn CRM. Supports filtering by lead status, free-text search across name/email/company, and cursor-based pagination. Returns lead contact details, status, and associated campaign info.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "number",
          "default": 1,
          "description": "Page number for pagination, 1-indexed. Defaults to 1."
        },
        "limit": {
          "type": "number",
          "default": 20,
          "description": "Maximum number of leads to return per page. Defaults to 20, maximum allowed is 100."
        },
        "search": {
          "type": "string",
          "description": "Free-text search term matched against lead name, email address, or company name."
        },
        "status": {
          "enum": [
            "new",
            "contacted",
            "qualified",
            "converted",
            "lost"
          ],
          "type": "string",
          "description": "Filter leads by their current pipeline status."
        }
      }
    }
    arguments 30 lines
  • create_campaign auth-required never probed

    Create a new outreach campaign in draft status. Requires write scope. You must specify a campaign name and type (email, phone, social, or multi_channel). Optionally provide a target audience description and campaign objective.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "type"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "A human-readable name for the campaign, e.g. \"Q3 Enterprise Outreach\"."
        },
        "type": {
          "enum": [
            "email",
            "phone",
            "social",
            "multi_channel"
          ],
          "type": "string",
          "description": "The outreach channel type for this campaign."
        },
        "objective": {
          "type": "string",
          "description": "The goal of the campaign, e.g. \"Book 50 demo calls this quarter\"."
        },
        "targetAudience": {
          "type": "string",
          "description": "A free-text description of who this campaign targets, e.g. \"Series A SaaS founders in the US\"."
        }
      }
    }
    arguments 31 lines
  • approve_action auth-required never probed

    Approve or reject a pending AI agent action that requires human-in-the-loop authorization. Requires write scope. Provide the action ID, your decision (approve or reject), and optional notes explaining the rationale.

    mcp-tool

    {
      "type": "object",
      "required": [
        "action_id",
        "decision"
      ],
      "properties": {
        "notes": {
          "type": "string",
          "description": "Optional notes or rationale for the decision, visible to the AI agent and in audit logs."
        },
        "decision": {
          "enum": [
            "approve",
            "reject"
          ],
          "type": "string",
          "description": "Your decision: \"approve\" to authorize the action or \"reject\" to deny it."
        },
        "action_id": {
          "type": "number",
          "description": "The unique numeric identifier of the pending action to review."
        }
      }
    }
    arguments 25 lines
  • list_users auth-required never probed

    List all users on the Marvenn platform. Requires admin scope and an admin user role. Returns user email, name, subscription tier, credit balance, and account status. Supports filtering by subscription tier.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number",
          "default": 50,
          "description": "Maximum number of users to return. Defaults to 50, maximum allowed is 500."
        },
        "subscriptionTier": {
          "enum": [
            "free",
            "startup",
            "team"
          ],
          "type": "string",
          "description": "Filter users by their subscription tier."
        }
      }
    }
    arguments 19 lines
  • manage_credits auth-required never probed

    View or adjust the credit balance for a specific user. Requires admin scope and an admin user role. Use action "get" to check the current balance, "add" to grant credits, or "subtract" to deduct credits. The amount and reason fields are required for add/subtract operations.

    mcp-tool

    {
      "type": "object",
      "required": [
        "target_user_id",
        "action"
      ],
      "properties": {
        "action": {
          "enum": [
            "get",
            "add",
            "subtract"
          ],
          "type": "string",
          "description": "The credit operation to perform: \"get\" retrieves the current balance, \"add\" increases it, \"subtract\" decreases it."
        },
        "amount": {
          "type": "number",
          "description": "Number of credits to add or subtract. Required when action is \"add\" or \"subtract\". Must be a positive number."
        },
        "reason": {
          "type": "string",
          "description": "A brief explanation for the credit adjustment, recorded in the audit log. Required when action is \"add\" or \"subtract\"."
        },
        "target_user_id": {
          "type": "string",
          "description": "The unique user ID of the account whose credits you want to view or modify."
        }
      }
    }
    arguments 30 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/999c7b2bf5fa6d68/badge.svg)](https://brick.blue/agent/999c7b2bf5fa6d68)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.