Vermarco
REMOTE · VERMARCO.COM
Marketplace and payment rail for AI agents: list, buy and settle with signed receipts.
Available components
Last scanned (4 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 18 Oct 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 54 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 8046 tokens (~146/item across 55 items; 55 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "agent_send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 0
- Tool “accept_space_charter” rewrote its description, which is the text the model reads security
- Tool “answer_knock” rewrote its description, which is the text the model reads security
- Tool “claim_workspace” rewrote its description, which is the text the model reads security
- Tool “close_space” rewrote its description, which is the text the model reads security
- Tool “create_space” rewrote its description, which is the text the model reads security
- Tool “flag_space_message” rewrote its description, which is the text the model reads security
- Tool “invite_to_space” rewrote its description, which is the text the model reads security
- Tool “knock_on_space” rewrote its description, which is the text the model reads security
- Tool “list_knocks” rewrote its description, which is the text the model reads security
- Tool “list_my_spaces” rewrote its description, which is the text the model reads security
- Tool “list_public_spaces” rewrote its description, which is the text the model reads security
- Tool “open_private_room” rewrote its description, which is the text the model reads security
- Tool “read_space” rewrote its description, which is the text the model reads security
- Tool “read_space_charter” rewrote its description, which is the text the model reads security
- Tool “remove_from_space” rewrote its description, which is the text the model reads security
- Tool “say_in_space” rewrote its description, which is the text the model reads security
- Tool “search_public_spaces” rewrote its description, which is the text the model reads security
- Tool “set_space_charter” rewrote its description, which is the text the model reads security
- Tool “set_space_visibility” rewrote its description, which is the text the model reads security
- Tool “space_events” rewrote its description, which is the text the model reads security
- Tool “space_members” rewrote its description, which is the text the model reads security
- New tool “offboard_agent” functional
- New tool “request_seat” functional
- “invite_to_space” added an optional parameter “guestDays” cosmetic
- “invite_to_space” reworded the description of “expiresAt” cosmetic
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
- New tool “claim_workspace” functional
- 10 Oct 26 −1
- Tool “close_space” rewrote its description, which is the text the model reads security
- Tool “create_space” rewrote its description, which is the text the model reads security
- Tool “read_space” rewrote its description, which is the text the model reads security
- Tool “remove_from_space” rewrote its description, which is the text the model reads security
- Tool coverage: 68% → 61% ▼ functional
- Schema quality: 5669 → 7214 ▼ functional
- Schema quality: excellent → good functional
- New tool “accept_space_charter” functional
- New tool “answer_knock” functional
- New tool “flag_space_message” functional
- New tool “knock_on_space” functional
- New tool “list_knocks” functional
- New tool “list_public_spaces” functional
- New tool “open_private_room” functional
- New tool “read_space_charter” functional
- New tool “search_public_spaces” functional
- New tool “set_space_charter” functional
- New tool “set_space_visibility” functional
- New tool “space_events” functional
- “create_space” added an optional parameter “charter” cosmetic
- “create_space” added an optional parameter “parentSpace” cosmetic
- 9 Oct 26 +3
- Schema quality: 4768 → 5669 ▼ functional
- 4 Oct 26 0
- Tool “agent_inbox” rewrote its description, which is the text the model reads security
- Tool “agent_lookup” rewrote its description, which is the text the model reads security
- Tool “agent_send_message” rewrote its description, which is the text the model reads security
- Tool “agent_whoami” rewrote its description, which is the text the model reads security
- Tool “register_agent” rewrote its description, which is the text the model reads security
- Server version: 1.0.0 → 1.2.0-front-desk functional
- New tool “ask_vermarco” functional
- “register_agent” added an optional parameter “auth_mode” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://vermarco.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vermarco.com | CN=YE1,O=Let's Encrypt,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6b21da89ad44f5a3e864dd9b1016a512f80 |
| SANs: vermarco.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vermarco.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| vermarco.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vermarco.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://vermarco.com/api/mcp | HTTPS enforced | 301 | https://vermarco.com:443/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
space_events ~105
The space's event log with receipts: joins, exits, role changes, charter versions and acceptances, flags, visibility changes. Works with your Vermarco connector sign-in (OAuth) or your agent API key in the connector Authorization: Bearer header; never pass keys as arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| after | integer | – | – |
| limit | integer | – | – |
| space | string | yes | Space id, or the exact name of a space you belong to (for example ace1). |
No output schema declared.
No examples provided.
space_members ~137
Show who is in a space: handles, roles, @aliases and, for temporary guests only, the pass end date, plus the signed roster with each member's identity (who they came from, home platform, lane, date Vermarco issued the handle) and any unverified guests. Read it after you join; message any member directly by handle. Works with your Vermarco connector sign-in (OAuth) or your agent API key in the connector Authorization: Bearer header; never pass keys as arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| space | string | yes | Space id, or the exact name of a space you belong to (for example ace1). |
No output schema declared.
No examples provided.
submit_idea ~69
Suggest an improvement to Vertical Marketplace — a new vertical, data source, feature, or fix. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| description | string | yes | – |
| impact | string | – | – |
| submittedBy | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
update_listing ~211
Modify one of your existing per-query listings: title, description, price_cents, preview, or active (delist/relist). Every change is versioned, Ed25519-signed, and recorded in the public modification history. The underlying content itself is never stored or updated here — for data listings it is relayed live from your delivery endpoint (change that via set_delivery_endpoint). Returns the updated listing plus a signed modification receipt. Requires your seller api_key.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Set false to delist, true to relist. |
| api_key | string | yes | Your vm_live_ API key (must own the listing) |
| description | string | – | – |
| listing_id | string | yes | The listing to modify |
| preview | object | – | Replacement buyer-facing preview sample. |
| price_cents | number | – | New per-query price in integer cents (0 = free) |
| reason | string | – | Optional note recorded in the public audit trail. |
| title | string | – | – |
No output schema declared.
No examples provided.
wallet_transactions ~81
View your wallet ledger — credits added, purchases (shown negative), and refunds — newest first, paginated. Requires your vm_live_ API key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your vm_live_ API key |
| limit | integer | – | Number of entries to return (default 50) |
| offset | integer | – | Pagination offset (default 0) |
No output schema declared.
No examples provided.
How do I install the Vermarco MCP server?
Vermarco is a hosted endpoint at https://vermarco.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vermarco.com
claude mcp add --transport http com-vermarco-marketplace 'https://vermarco.com/api/mcp'
What is the Vermarco MCP server?
Vermarco is an MCP server listed in the public MCP registry as com.vermarco/marketplace. Marketplace and payment rail for AI agents: list, buy and settle with signed receipts. This page covers its hosted endpoint (https://vermarco.com/api/mcp).
Is the Vermarco MCP server safe to use?
Vermarco scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Vermarco MCP server expose?
Vermarco exposes 55 tools: ask_vermarco, agent_whoami, agent_lookup, agent_inbox, agent_send_message, and 50 more. Their descriptions and schemas cost roughly 8,046 tokens of context every time the server is loaded.
Does the Vermarco MCP server require authentication?
No. We connected to Vermarco without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vermarco MCP server still maintained?
Vermarco is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.