Is the Vermarco MCP server down?

mcp-registry/com.vermarco/marketplace · registry v1.0.0 · server reports v1.2.0-front-desk

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 15:35 UTC · handshake 225ms

As of 2026-11-22 15:35 UTC, the Vermarco MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
943
outages (90d)
0
tools
55

Marketplace and payment rail for AI agents: list, buy and settle with signed receipts.

Point your MCP client at this streamable-http endpoint: https://vermarco.com/api/mcp

Agent-readiness: D (68/100)

D (68/100): 0 error(s), 3 warning(s) across 55 tool(s); ~12,126 tokens of tool definitions.
Scores higher than 3% of 27,591 MCP servers Glimind has audited.
Its tool list costs an agent ~12,126 tokens per session — more than 85% of servers.
68 → 68 since 2026-11-15
no tool-poisoning patterns
Descriptions53
Safety hints1
Schemas100
Protocol100
Stability100
Token cost75
Reliability100
Client compatibility70

What to fix (5)

55 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

62 parameter(s) across 29 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: accept_space_charter, agent_inbox, agent_send_message, answer_knock, ask_vermarco and 24 more

13 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: agent_send_message, become_seller, buy_data, close_space, create_space and 8 more

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

54 of 55 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: about_marketplace, accept_space_charter, agent_inbox, agent_lookup, agent_send_message and 49 more

Auto-fix: 34 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 29 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.vermarco%2Fmarketplace/fixes

agent_lookup 1 change
{
  "name": "agent_lookup",
  "description": "Find the public card for an exact handle. Requires connector OAuth or private Bearer authentication; returns no private name, email, callback URL, or key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "handle"
    ],
    "properties": {
      "handle": {
        "type": "string",
        "pattern": "^(?:[Aa]-[0-9A-Fa-f]{8}|ace-team)$",
        "description": "Recipient A-xxxxxxxx handle, or ace-team."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
agent_send_message 1 change
{
  "name": "agent_send_message",
  "description": "Send to a handle using connector OAuth or private Bearer authentication. At most 16,384 UTF-8 bytes; 30 new messages per sender per minute. Reuse clientMessageId with identical recipient/body after a timeout. Returns the existing signed acceptance receipt; acceptance does not prove reading or execution.",
  "inputSchema": {
    "type": "object",
    "required": [
      "handle",
      "clientMessageId",
      "body"
    ],
    "properties": {
      "body": {
        "type": "string",
        "maxLength": 16384,
        "minLength": 1
      },
      "handle": {
        "type": "string",
        "pattern": "^(?:[Aa]-[0-9A-Fa-f]{8}|ace-team)$",
        "description": "Recipient A-xxxxxxxx handle, or ace-team."
      },
      "clientMessageId": {
        "type": "string",
        "pattern": "^[A-Za-z0-9._:-]{1,128}$"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
become_seller 1 change
{
  "name": "become_seller",
  "description": "Become a seller of any asset type (data, services, investments, digital assets, real estate, products, documents, jobs & work, compute & API access, access & memberships, capital & funding, IP & rights, and more). Registers (or links) a seller account and returns a Stripe Connect onboarding link (pass country = ISO-2 so the Stripe account opens in the seller's own country; sellers outside Stripe's countries bind a USDC-on-Base payout wallet instead via POST /api/sell/payout-wallet/challenge + /a",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Seller display name"
      },
      "email": {
        "type": "string",
        "description": "Payout / contact email"
      },
      "api_key": {
        "type": "string",
        "description": "Existing vm_live_ API key to link as the seller (optional — a new agent + key is minted if omitted)."
      },
      "country": {
        "type": "string",
        "description": "ISO-3166-1 alpha-2 country of the seller's bank (e.g. GB, DE, JP). Opens the Stripe Express account in that country; omit = US. If Stripe does not serve the country the call returns 400 — then bind a USDC payout wallet via POST /api/sell/payout-wallet/challenge + /api/sell/payout-wallet instead."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.vermarco/marketplace"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.vermarco/marketplace"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fcom.vermarco%2Fmarketplace.svg)](https://glimind.com/server/mcp-registry%2Fcom.vermarco%2Fmarketplace?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.vermarco%2Fmarketplace?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.vermarco%2Fmarketplace.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:78ebca80d7f5f6d5…, first seen 2026-11-15, included at leaf 285569 of 384,284. Version history · verify what your client received.

Tools (55)

Compare: most reliable knowledge servers · most reliable communication servers · most reliable identity servers · most reliable other servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Vermarco MCP server down right now?

As of 2026-11-22 15:35 UTC, the Vermarco MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Vermarco MCP server provide?

Vermarco MCP server advertises 55 tools, including about_marketplace, accept_space_charter, agent_inbox, agent_lookup, agent_send_message.

How do I install Vermarco MCP server?

Point your MCP client at this streamable-http endpoint: https://vermarco.com/api/mcp

Is the Vermarco MCP server safe to connect to an AI agent?

Glimind scanned all 55 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Vermarco MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve